Problems with hsqldb

[Thomas Dudziak <to...@first.gmd.de>]

Hi,

just wanted to let you know about two problems I had with OJB + hsqldb.
The first one is that hsqldb issues an error if you have a column tagged
as IDENTITY that is also denoted as PRIMARY KEY. You will get such a
column definition if you use Torque to generate the db and the column is
autoincrement (-> IDENTITY) and primary key. This has been fixed yesterday
in the hsqldb CVS.
The second problem arises when you have a String field that is mapped onto
a ((LONG)VAR)BINARY column. hsqldb will complain about an unrecognized
encoding or hex string (depending on the hsqldb version) as it does not
automatically map the String to the column but rather expects that the
string contains the encoding of some object. You will have to use some
conversion on the field (e.g. Object2ByteArrFieldConversion).

Tom


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-user-help@db.apache.org