Remove the inverse relationship. Mark
-- Dr. Mark Wardle Specialist registrar, Neurology (Sent from my mobile) On 23 Jan 2011, at 22:05, Tarun Reddy <t...@cornell.edu> wrote: So I've got a situation where I'm seeing a SELECT that will eventually kill my performance and want to see if I can fix it before my site goes live. My EOModel has an object called a Landing and an object called a SiteDefinition. The SiteDefinition defines what the site looks like and the Landing represents a user landing on the site. When a user comes to the site, I create a Landing and associate it with the SiteDefinition so that I can capture what site a user sees and what users were on a site. SiteDefinition to many Landings When I add the relationship using this: aLanding.setSiteDefinitionRelationship(getSiteDefinition()); WebObjects decides it needs to select all Landings where the siteDefinitionID equals the one I'm assigning. This is fine in dev where I may only have 17 records but eventually I may have 10s of thousands of records. Is this my EOModel, and if so how can I prevent it? Thank you, Tarun _______________________________________________ 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/mark%40wardle.org This email sent to m...@wardle.org
_______________________________________________ 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 arch...@mail-archive.com
