batchFetchRelationship---is it a hint, or a command?
batchFetchRelationship---is it a hint, or a command?
- Subject: batchFetchRelationship---is it a hint, or a command?
- From: Jonathan Rochkind <email@hidden>
- Date: Tue, 17 Feb 2004 18:45:14 -0600
Has anyone looked into exactly what
EODatabaseContext.batchFetchRelationship does?
It's looking to me like it's kind of a 'hint', not a directive that
EODatabaseContext must follow. I have a list of 30 objects of the
same entity. I call batchFetchRelationship with a particular to-one
relationship of that entity.
What I expect is, as soon as I trigger one of the faults for that
to-one relationship, one fetch will be done to fetch ALL of them (or
all of them that need fetching), and none of them will be faults any
longer. What I seem to find is that when I trigger one of the faults,
_some_ of the other faults get cleared (in fact just ONE additional
one---which is one more than I'd expect without the
batchFetchRelationship directive)..... but some of the other faults
remain faults. It doesn't seem to batch fetch them all, but just an
apparent random subset of them.
When I later access one of those to-one faults that mysteriously
remained faults.... in my little experiment, THAT caused all of the
faults to get cleared. So all the faults cleared in TWO fetches, but
I'd expect batchFetchRelationship to clear them all in ONE fetch.
Anyone have any light to shed on this?
--Jonathan
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.