is.
>
> From: Ricardo Parada <rpar...@mac.com>
> Date: Tuesday, September 20, 2016 at 3:19 PM
> To: Chuck Hill <ch...@gevityinc.com>
> Cc: "webobjects-dev@lists.apple.com" <webobjects-dev@lists.apple.com>
> Subject: Re: Cannot obtain globalId for an
Parada <rpar...@mac.com>
Date: Tuesday, September 20, 2016 at 3:19 PM
To: Chuck Hill <ch...@gevityinc.com>
Cc: "webobjects-dev@lists.apple.com" <webobjects-dev@lists.apple.com>
Subject: Re: Cannot obtain globalId for an object which...
Hi Chuck,
I followed the ste
Hi Chuck,
I followed the steps of the code and I noticed that the object containing the
to-many relationship in question is being local instanced in a peer editing
context. The to-many is still an array fault which has not been triggered.
Then when the object in the original context has its
A full stack track would help. It sounds like your code is making a
relationship between objects in different editing contexts. Did someone forget
to add a “localInstance”?
From: on behalf of
Ricardo Parada
Hi Bill,
Is it possible that there are objects that aren't in _any_
EditingContext? Created but not inserted? That can cause some really
crazy stuff.
Dave
On Feb 18, 2009, at 5:19 PM, Bill Gallop wrote:
Hello all,
We're seeing this really weird behaviour in our applications from
time
Hi!
I have seen this behavior when I screwed up some locking stuff.
Make sure:
1) All the contexts you are working with are locked, and locked by
the proper thread.
2) Never, ever, share contexts between sessions. It might appear
it's working fine. Well, it's not. It will fail.
On Feb 18, 2009, at 2:56 PM, Miguel Arroz wrote:
Hi!
I have seen this behavior when I screwed up some locking stuff.
Make sure:
1) All the contexts you are working with are locked, and locked by
the proper thread.
2) Never, ever, share contexts between sessions. It might appear