Re: Yes, even one more concurrency question - relationship "freshness"
Re: Yes, even one more concurrency question - relationship "freshness"
- Subject: Re: Yes, even one more concurrency question - relationship "freshness"
- From: Chuck Hill <email@hidden>
- Date: Mon, 13 Aug 2007 09:24:04 -0700
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,
and saves changes. When I save changes on my app, I get an
exception saying that the first B (the one that got deleted by the
other app) is not registered in any editing context.
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.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden