One more important thing. Make sure your primary keys are unique across Documents _and_ Downloads. Ie. If there is document #10 there should never be download #10
This is because they are in the same extent. If you retrieve a collection of SupportItemI's then they need to have unique IDs, or a Bad Thing(TM) will occur. Depending on your DBMS, you can do this in a number of ways. http://db.apache.org/ojb/sequencemanager.html explains it. Set the same sequence-name for the primary key fields for all classes in an extent (download and document). Rob :) > -----Original Message----- > From: Patrick Scheuerer [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 6 January 2004 12:35 p.m. > To: OJB Users List > Subject: Re: How to combine two non-decomposed m:n mappings > in one collection? > > > ... and now for something completely different: > > do i even have define foreign key constraints in my > database??? I'm having the > impression that OJB is handling all the joins. Is it enough > to have some loose > tables in my DB ??? > > Patrick > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
