Hi!
This one should be simple.
I have object A that has a to-many relationship to B. So, A
contains Bs.
I fetch A that contains one B. Then, I add another B to the
relationship. Some other app deletes the B that was there before, and
saves changes. When I save changes on my app, I
On Aug 12, 2007, at 3:52 PM, Miguel Arroz wrote:
Hi!
This one should be simple.
I have object A that has a to-many relationship to B. So, A
contains Bs.
I fetch A that contains one B. Then, I add another B to the
relationship. Some other app deletes the B that was there before,
Hi!
On 2007/08/13, at 17:24, Chuck Hill wrote:
How do you handle this kind of problem?
By not disabling merging of changes. :-)
(I don't know if it's relevant, but the merging of changes is
disabled for the context).
I guess that it is relevant, though I don't recall doing this.
On Aug 13, 2007, at 1:10 PM, Miguel Arroz wrote:
Hi!
On 2007/08/13, at 17:24, Chuck Hill wrote:
How do you handle this kind of problem?
By not disabling merging of changes. :-)
(I don't know if it's relevant, but the merging of changes is
disabled for the context).
I guess that
Hi!
On 2007/08/13, at 21:35, Chuck Hill wrote:
I'm going to test this. But why is it relevant, if the deletion
of the first object happens in a different app? What exactly is
being merged here?
If it is in another app or another OSC then you won't get the error
that you mentioned. :-)
On Aug 13, 2007, at 1:42 PM, Miguel Arroz wrote:
Hi!
On 2007/08/13, at 21:35, Chuck Hill wrote:
I'm going to test this. But why is it relevant, if the deletion
of the first object happens in a different app? What exactly is
being merged here?
If it is in another app or another OSC the
Hi!
On 2007/08/13, at 21:44, Chuck Hill wrote:
Then something in your app is refreshing the to-many relationship.
Well, the problem is much more strange than I thought (we are
entering the "you surely know how to have fun with WO" zone!).
I have the a.bs() to-many relationship.
I h
On Aug 13, 2007, at 2:56 PM, Miguel Arroz wrote:
Hi!
On 2007/08/13, at 21:44, Chuck Hill wrote:
Then something in your app is refreshing the to-many relationship.
Well, the problem is much more strange than I thought (we are
entering the "you surely know how to have fun with WO" zone!)
Hi!
Have you tried
a.removeObjectFromBothSidesOfRelationship( obj, "bs" );
Same result.
Have you made other changes in the EC? If not, ec.revert() should
handle all this much more cleanly.
I did! :( The problem is this: the user changes one object. Then,
I'm going to try to save th
Hi Miguel,
You do have all the fun. Must be nice in Alentejo this time of year...
On Aug 13, 2007, at 3:42 PM, Miguel Arroz wrote:
Hi!
Have you tried
a.removeObjectFromBothSidesOfRelationship( obj, "bs" );
Same result.
I thought so, but it was worth a try.
Have you made other chan
Hi!
On 2007/08/14, at 17:03, Chuck Hill wrote:
Hi Miguel,
You do have all the fun. Must be nice in Alentejo this time of
year...
Friday. Friday I go there. Right before the border with Spain,
Serpa is where I'll go. Good food. Sun. Pool. The bad news is... I
come back Sunday.
I ca
On Aug 14, 2007, at 9:25 AM, Miguel Arroz wrote:
Hi!
On 2007/08/14, at 17:03, Chuck Hill wrote:
Hi Miguel,
You do have all the fun. Must be nice in Alentejo this time of
year...
Friday. Friday I go there. Right before the border with Spain,
Serpa is where I'll go. Good food. Sun. P
Hi!
On 2007/08/14, at 17:40, Chuck Hill wrote:
See, it is trying to create an UPDATE statement for this object.
Something has trashed the EC state.
Maybe try adding
ec.undoManager().removeAllActions(); before the call to saveChanges
(), or try getting rid of the undo manager before making
13 matches
Mail list logo
