: AW: AW: AW: Two 1:N mappings to one table
Ah hah! You are allowing DB2 to add the ID via a trigger, aren't you?
OJB doesn't play super nicely with the database doing that for it behind the
scenes, unfortunately. If you are allowed, try using one of the OJB auto
increment modules. I suggest
to set
autoincrement off in db2, because other apps might use these tables as
well...
-Ursprüngliche Nachricht-
Von: Brian McCallister [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 15. Januar 2004 16:44
An: OJB Users List
Betreff: Re: AW: AW: AW: Two 1:N mappings to one table
Ah hah! You
these tables as
well...
-Ursprüngliche Nachricht-
Von: Brian McCallister [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 15. Januar 2004 16:44
An: OJB Users List
Betreff: Re: AW: AW: AW: Two 1:N mappings to one table
Ah hah! You are allowing DB2 to add the ID via a trigger, aren't you?
OJB
thank you both. you helped me a lot in understanding ojb. I'll give it a
try.
Dirk
-Ursprüngliche Nachricht-
Von: Armin Waibel [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 15. Januar 2004 18:06
An: OJB Users List
Betreff: Re: AW: AW: AW: AW: Two 1:N mappings to one table
Hi Dirk
: AW: AW: AW: AW: Two 1:N mappings to one table
Hi Dirk,
if you use Identity columns from database you can't use the default
SequenceManager (SequenceManagerHighLowImpl). Have a look in
http://db.apache.org/ojb/sequencemanager.html#nativeSequenceManager
can all do for me. In the repository
