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
