Object not being saved after refaulting and applying changed
Object not being saved after refaulting and applying changed
- Subject: Object not being saved after refaulting and applying changed
- From: Miguel Arroz <email@hidden>
- Date: Thu, 19 Jul 2007 23:54:48 +0100
Hi!
I'm having a weird problem here. The situation is the following: I
have a context, where I have a freshly inserted EO, some non-updated
EOs, and some updated EOs. When I try to save and detect a Optimistic
locking exception, I need to deal with it by refaulting all the
objects (updated or not) from the DB, and reapplying the changes to
some of them.
So, I manually call refaultObject(object) to all objects I know
that were updated, and call refaultAllObjects for all the others
(because refaultAllObjects does NOT refault updated objects).
After than, I reapply the changes, and try to save. I'm absolutely
sure that I applied the changes, because I log one of the properties
of an updated object right before the saveChanges call.
Now, the amazing result is that some objects are saved, and some
are not! No SQL is generated for them, and so they are simply not saved.
I looked arround, and say this: <http://lists.apple.com/archives/
webobjects-dev/2004/May/msg00377.html>. I tried to apply that hack,
but it didn't work. Is the bug 3389369 solved?
So... is this a bug from WO or am I doing something stupid? If
it's a bug, how can I do an workarround? If it's me doing stupid
things, what are those? :)
Yours
Miguel Arroz
Miguel Arroz
http://www.terminalapp.net
http://www.ipragma.com
_______________________________________________
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