It is fairly simple to write a thin typology layer in java (yes I have
done it) that
shows the db types in a unified way to a java program.
My current typology includes the types
BOOLEAN, INTEGER, FLOATING, DECIMAL, STRING, BINARY, TEMPORAL and EXOTIC
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
underlying db.
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.
- rami
On 2.7.2011 1:13, Shai Bentin wrote:
Hey,
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.
Shai
בתאריך 30/06/11 11:14 PM, ציטוט cowwoc:
On 30/06/2011 3:11 PM, bart wrote:
However the management of different types of databases is interesting.
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.
Gili
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
