Hi Kieran, Am 05.03.2008 um 18:07 schrieb Kieran Kelleher:
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?
can't speak on the first topic but using Entity Modeler to create a manty-to-many relationship the join entity gets automatically EOGenericRecord as class name. So as long as there are no custom attributes you don't need to have a custom subclass for these and I couldn't notice that VeoGen had a problem with that.
jw
Kieran _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/werner%40isd.uni-stuttgart.de This email sent to [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
