Re: SELECT statement on relationship binding
Re: SELECT statement on relationship binding
- Subject: Re: SELECT statement on relationship binding
- From: Mark Wardle <email@hidden>
- Date: Sun, 23 Jan 2011 22:42:28 +0000
Remove the inverse relationship.
Mark -- Dr. Mark Wardle Specialist registrar, Neurology (Sent from my mobile)
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 (email@hidden)
This email sent to email@hidden
|
_______________________________________________
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