Hi John, hi Jean-Pierre, thanks for your replies!
I stumbbled on this one too. Did someone file a bug report ? JPM
I just did, radar 4725832. I also came across a message from Christian Pekeler on another problem with the iterator implementation: <http://lists.apple.com/archives/webobjects-dev/2006/ Jan/msg00365.html>
I discovered this a month or two ago. It appears as if iterator() does not fire the fault on relationships. That is why with your log statement everything is ok: the accessing of the productionRuns() field IS firing the fault. The iterator then works. This is a bug in the iterator implementation. The only thing you can do is either manually fire each fault or use objectEnumerator(). I use objectEnumerator(). John
I'm still wondering about this one:
Order <->> OrderItem <<->> ProductionRun <-> DeliveryDefect In Order, I've defined a flattened relationship deliveryDefects. It works fine for deliveryDefects that exist when the order is fetched from the DB. However, it fails to include a deliveryDefect that is created and then saved to the DB. Is this a known limitation of flattened relationships?
Is this behaviour to be expected? Is this documented anywhere? I couldn't find an awful lot of documentation on flattened relationships anyway.
cheers Fabian _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
