t: 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,
if you use Identity columns from database you can't use the default
SequenceManager (SequenceManagerHighLowImpl). Have a look in
http://db.apache.org/ojb/sequenceman
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
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-user.xml I set every pk column with
> primarykey="t
No! You misunderstood me.
Declare the PK's, FK's etc in the database. Do not abandon good
database practices for OJB -- particularly as never know what programs
will access the DB directly in the future.
The DB managed auto-increment is the thing that is causing OJB to
hiccup on you, I susp
hm. our db2 database tables are configured with an autoincrement for the
primary keys by default. (for exampl: activityId INTEGER NOT NULL GENERATED
BY DEFAULT AS IDENTITY (STARTS WITH 1, INCREMENT BY 1, NO CACHE, PRIMARY
KEY). this is my first time using ojb. Meanwhile I get aware of what ojb
can
