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?
The latest nightly (as of a few days ago) supports one-sided many-to-
many relationships in the wizard.
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?
Veogen does not require a subclass for the join entity. If you choose
to flatten, entity modeler will use EOGenericRecord as the join entity
class, which veogen will skip on generation.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
