Avoiding nulls along an EOQualifier's [toMany] keypaths
Avoiding nulls along an EOQualifier's [toMany] keypaths
- Subject: Avoiding nulls along an EOQualifier's [toMany] keypaths
- From: Lachlan Deck <email@hidden>
- Date: Mon, 13 Nov 2006 18:01:04 +1100
Hi there,
I have some entities related as follows...
A -->> B -->> C --> D
...and a qualifier...
new EOKeyValueQualifier( "b.c.d",
EOQualifier.QualifierOperatorContains, myD );
...used for a display group to limit the view to those 'a' objects
that contain any 'b's that have a relationship to any 'c' that is
related to a particular 'd'.
The trouble is that some c's may have a null relationship for d. So,
obviously, where relevant NSKeyValueCoding.NullValue's get
substituted which cannot resolve the key "d"; and an exception is
thrown.
Does anyone have any efficient work-a-rounds?
There's potentially a lot of objects involved - so it'll need to be
somewhat efficient.
Thanks in advance...
with regards,
--
Lachlan Deck
_______________________________________________
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