Yes, EOF will be slow when saving an object with a huge modeled toMany relationship since it fetches the entire relationship for validateForSave. The solution is to remove the toMany side of the relationship from the eomodel and (if needed) add your own business logic for fetching/modifying/deleting items in that toMany relationship.
If relationships are not too large, but the db table is really huge and you are using a db without proper foreign key support (sadly mysql falls into this category with the lack of deferred FK constraints in latest GA versions), then you need to make sure you have an INDEX for the foreign key of the toMany relationships, otherwise the regular EOF fetch on those relationships will be slow due to the sheer size of the foreign db table itself. Hope that helps a little, Regards, Kieran On Jul 8, 2010, at 11:14 AM, Greg Lappen wrote: > does that mean that EO has problems when a one-to-many relationship gets too > large? _______________________________________________ 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]
