Re: EO Changes Not Saving to DB?
Re: EO Changes Not Saving to DB?
- Subject: Re: EO Changes Not Saving to DB?
- From: Kieran Kelleher <email@hidden>
- Date: Mon, 24 May 2004 17:14:05 -0400
Thanks for the suggestion Art.
I tried it and actually I sent the NSArray of updatedObjects() out to
the log just before saveChanges() was called only to find that the EO
which was refaulted and had failed values reapplied was NOT in the
updatedObjects list. I got another long email from Pierre which I need
to digest and try his suggestions.
I'll keep trying to figure it out! .... and if I don't within a
reasonable time, then the app functionality will just have to tell the
user that changes happened while they were editing and ask them to
re-edit the new snapshot and save again instead of the app silently
merging the changed values.
-Kieran
On May 24, 2004, at 2:12 PM, Art Isbell wrote:
On May 24, 2004, at 5:56 AM, Kieran Kelleher wrote:
Then when I saved, the EC did not recognise the EO as having changes
that needed to be saved, so it did not write it back out to the DB
after reapplying changes from dictionary.
EOF does a lot of stuff at the end of each "event". When EOF was
originally written, an event was a desktop application event (e.g.,
mouse click, key press). So events were frequent. Web app events are
typically must less frequent (e.g., request/response).
So when EOF is reluctant to process a change, I usually send a
processRecentChanges() message to the appropriate editing context to
see whether that will shake things loose. It might be worth trying.
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.