On 08.08.2008, at 15:11, Chuck Hill wrote:
Hmmm. Back to the old application, FETCHING works now. Resolving a
relationship to an object that was NOT cached earlier, crashes.
When I do a fetch, the relationship is resolved just fine when the
object the relation is pointing to was fetched before. But it stops
working as soon as the timestamp lag is reached.
Weird.
What glorious fun for a Friday!
This is sounding more like a variant of the problem Mike worked on
in Wonder: if you fetch the object, the GID is set correctly. If a
relationship is followed, it is set incorrectly. This is a total
guess.
But it sounds like the thing I'm seeing. And I didn't have time
exploring that much. Just switched to that workspace a couple of times
when I thought I had an idea. But I was at the office today so I
didn't have much time for tinkering with it.
At least I'm down to the following scenario:
1. Fetching the stuff with a normal fetch works now.
2. Following a relationship does not work, if I haven't fetched that
object at the end of the relation before.
After a while I get null values back when I try to access something
that follows that relationship - on an object where I got a valid
value back before. Very, very weird!
cug
--
http://www.event-s.net
_______________________________________________
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]
