one sided many-to-many?
one sided many-to-many?
- Subject: one sided many-to-many?
- From: Kieran Kelleher <email@hidden>
- Date: Wed, 5 Mar 2008 12:07:56 -0500
Implementing a "one sided" one-to-many is straightforward (to prevent
pulling in a million rows just to add a few entities to the both sides
of relationship), but is there some special consideration when
implementing a one-sided "many-to-many" since the join table has rows
added and deleted for relationship adds and deletes rather than just
setting and nullifying foreign keys in a regular one-to-many?
On a related note, does the fact that the VeoGen requires us to have a
custom java subclass for join entities have any performance impact on
huge many-to-many relationships ... or is that irrelevant?
Kieran
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden