[daisy] regarding the DB2 issues -- @Aaron

Aaron.Digulla at Globus.ch Aaron.Digulla at Globus.ch
Mon Jan 22 04:28:00 CST 2007


daisy-bounces at lists.cocoondev.org schrieb am 19.01.2007 11:27:36:

> Also, we are worried about on-going support and testing against 
> "officially supported" databases.

Please have a look at the patches right now.

You'll see that only a part of them is DB2 specific (namely, the SQL 
generation scripts).

I reported a few issues with the datamodel (using DATE instead of 
DATETIME/TIMESTAMP for "last modification time") plus the broken usage of 
NULL values in PreparedStatement.set*(). These issues only work with MySQL 
because MySQL fixed a couple of bugs in the SQL and JDBC standard :-) You 
cannot reply on this to work anywhere else. You'll see these if you start 
to base your test cases in Derby, for example.

The issue about the length of the table names is probably DB2 specific but 
I hope that you can accept shorter names in your model :-)

When these are fixed, porting to new "big" DBs like Oracle and DB2 (were 
JDBC support is nowhere as good as in MySQL :-( ) will be much more simple 
(namely writing or copying the Torque scripts).

Regards,

-- 
Aaron Digulla


More information about the daisy mailing list