Re: restricting qualifiers and join entities
Re: restricting qualifiers and join entities
- Subject: Re: restricting qualifiers and join entities
- From: Ray Kiddy <email@hidden>
- Date: Wed, 4 Jun 2008 11:07:03 -0700
On Jun 3, 2008, at 7:26 PM, Lachlan Deck wrote:
Hi there,
Say I have entities Foo and Bar (both of which have an attribute
isDeleted) and a join FooBar and I create restricting qualifiers
for Foo and Bar of (isDeleted IS NULL OR isDeleted = 0).
Foo.fooBars() still fetches all fooBars even if pointing to a Bar
that cannot be instantiated due to the restricting qualifier.
So my question is: should EOF filter such joins automatically
(i.e., should I file a bug) or is it just up to me to auto-apply
these restricting qualifiers?
with regards,
--
Lachlan Deck
I have tried this kind of thing before, and may have actually taken
this to ridiculous extremes. I find that if I change values in the eo
in certain ways, I need to make the editing context (and sometimes
all editing contexts) forget the object so that the "misdirection" I
have has an effect after the fault is tripped.
I often find I have to forget the object more than I think I should
have to. Usually, though, I want to finish with something and that
wins over figuring why I am having to jump through these hoops again.
- ray
_______________________________________________
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