Am 30.11.2008 um 20:57 schrieb Jeff Schmitz:
The reason I ask is, it seems from testing that if I bring up the same record on my site in two different sessions and change an attribute on one page and save it, and then do a save on the other page without changing anything, the attribute that was changed on the first update gets overwritten by the original (now stale) value that was brought up by the second session, even though no attributes were changed. To me, this sounds like the "stomp" option from the description below.
The behaviour is correct (or at least expected): assume a=0. If you change a=1 in EC1 and save in EC2. EC2 will refault and re-apply the "changes" which are now that a=1. So it will overwrite with it's own value of a=0. I'm not sure if there is an actual way to know that a didn't really change in EC2...
I was hoping it would check what changed from when the page was first brought up and merge only those changes with the values from the refaulted data that was brought in from the DB when the exception occurred. Asking too much? Or is there something else I need to do to get this behavior?
I suppose it is asking too much. The actual "change" isn't really recorded anywhere, it's just transient data in the adaptor. And how would you know that a didn't change from 0 to to 2, then to 0 and then to 1 in the time your EC2 was inactive? If you used the ERC features for the audit trails, you might have a chance, though.
Cheers, Anjo _______________________________________________
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]
