Maybe it would make sense from those who are interested to fork it...
I'm not sure if it does make sense, but it would be an option.
My 2 cents: don't bother. You're chasing a false dream (no one has
solved this problem yet). And if you think about it, how often do you
really need to change databases? This is only useful for products that
need to support multiple databases concurrently.
You can see my stuff here: http://code.google.com/p/jaqu-orm/
post you questions on the wiki pages, post issues on the site's issues.
בתאריך 30/06/11 11:14 PM, ציטוט cowwoc:
Into exotic I have thrown everything confusing that I dislike (eg. Array)
But that will not help when accessing the db from non-java programs.
Also it will not fix the inconsistencies in the type system of the
One thing to note is that a layer on top of another is at it's best as
good as the layer below it.
That's why I choose to use jdbc and sql with H2 because if that is not
very satisfying how
can a layer above it be so?
To me Jaqu's, JooQ's and hibernate's etc. query languages are even more
confusing and difficult
than sql (which is illogical and bureaucratic to begin with).
For me the proliferation of layers above layers is the real problem of
why things are so difficult
to grasp nowadays in the java world.
Just my 5 cents.
> I want to have the point of view from Thomas because it's his project
> and he's someone I respect for all the work he did.
I would really like to comment, and help further improve JaQu, but I'm afraid I will not have time to do so in the near future. So far, I did not even have enough time to integrate all the changes from James. It doesn't look good in the near future.
So I guess it makes sense for those who are interested to create a new project. I don't want to hold up anybody. If such a new project would like a different license (for example Apache), then I would be happy to allow that. The project would need a new name I guess, as I would like to keep the name 'JaQu' currently. I will then point to this new project from the JaQu page, and possibly even retire my project later on (but more likely, I will keep JaQu as it is now for some time).