Why remove it?
Just uncheck the diamond. You can then still use it in qualifiers but it won’t
get fetched.
atze
Am 23.01.2011 um 23:42 schrieb Mark Wardle:
Remove the inverse relationship.
Mark
--
Dr. Mark Wardle
Specialist registrar, Neurology
(Sent from my mobile)
Hi Tarun;
Large to-many can be trouble for the reason that you have identified. I
tend to omit those from the model, leaving the to-one relationship in
place. EOF allows this because the relationships are not automatically
reflexive.
In this I mean that the to-one and to-many
On Jan 23, 2011, at 2:04 PM, Tarun Reddy 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
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
