Hi,
I've submitted a bug and an enhancement request related to JDO & SAPDB.
Current sapdb factory forces users to write all uppercase table and
column names in the mapping file.
I'm not sure that this is a good choice?!? I've also provided a solution
for this problem, actually two solutions.
I vote for the first one, which is - simply use the inherited Oracle
factory which perfectly suites sapdb/maxdb for the purpose of quoting
table and column names, even with the sapdb built-in functions 'currval'
and 'nextval'. Also, this bug means that the mapping.xml from castor jdo
test suite doesn't work with sapdb. Besides that, sql script used to
create the testing database has incorrect sql syntax and I'm just
wondering if anyone has actually tried to run those test against the
sapdb engine?! :-)
The enhancement request is for support of the IDENTITY key generator for
sapdb engine too.
Since sapdb supports the SERIAL data type perfect for IDENTITY key
generator, I'm not sure why this type of key generator is not supported.
I've made and tested a patch for IdentityKeyGenerator class which
enables this support.
Regards,
Emir
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
