Sorry, No help yet. Any help on this would be appreciated.
Bob. -----Original Message----- From: Agarwal, Piyush [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 3:00 PM To: '[EMAIL PROTECTED]' Subject: RE: [castor-dev] JDO class design constrained by RDBMS relational paradigm Hi Robert, did you get an example of this ? If you have one can you send it to me . Thanks, Piyush -----Original Message----- From: Robert Ollila [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 8:22 AM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] JDO class design constrained by RDBMS relational paradigm Brad, Bruce, and Marie, First, thanks to all for your input. Brad (or anyone), is there any way you could show me what the mapping file (and java classes) looks like in your first example (many-to-many with only one of the java classes containing a collection of the other)? Even a quick pseudo-code example would be welcome. If you have time it would be greatly appreciated. thanks, Bob. -----Original Message----- From: Bruce Snyder [mailto:[EMAIL PROTECTED]] Sent: Friday, November 30, 2001 12:17 AM To: [EMAIL PROTECTED] Subject: Re: [castor-dev] JDO class design constrained by RDBMS relational paradigm This one time, at band camp, Brad Clow said: BC >u don't have to have both sides of a relationship represented in your java BC >objects. for example we have a many-to-many defined in the database. BC >however only one of the two java classes involved contains a collection of BC >the other. BC > BC >we also have one-to-many relationships where we have done the opposite to BC >your question. the child contains a reference to the parent, but the parent BC >doesn't contain the collection of children. BC > Bob, Brad is exactly correct. It really only depends on how you'd like to be able to navigate the relationships in your objects. -- perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");' ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev LEGAL NOTICE - Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately. ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
