On Sep 1, 2006, at 3:39 PM, Lachlan Deck wrote:
Hi there,
On 02/09/2006, at 3:18 AM, Chuck Hill wrote:
On Sep 1, 2006, at 1:12 AM, Lachlan Deck wrote:
On 01/09/2006, at 5:26 PM, Lachlan Deck wrote:
I'm looking at providing a global qualifier to some EOEntities
(EOEntity.setRestrictingQualifier) that involve setting
qualifiers that restrict the set of objects returned by any
fetch to those related to a particular record.
The concern is that if any of the attributes change for that
record that the above qualifier would then be out of date. So my
question is whether or not the above provides a safe foreign key
qualifier (akin to EOEntity.qualifierForPrimaryKey(NSDictionary)).
Ah. I think EOEntity.schemaBasedQualifier(EOQualifier) is what
I'm after.
As a final bit of confirmation, setRestrictingQualifier() is what
EOF uses to manage single table inheritance. If you go changing it
around, I predict that you will confuse EOF and produce peculiar
bugs.
That's good to know. I'm not using single table inheritance - but
either way, perhaps ANDing the current restricting qualifier with
the additional criteria would be the safe way forward?
That should happen automatically. The restricting qualifier is
usually set once, in the EOModel, and not changed after that.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
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 archive@mail-archive.com
