Help, strange behavior after saveChanges with WO 5.2.3
Help, strange behavior after saveChanges with WO 5.2.3
- Subject: Help, strange behavior after saveChanges with WO 5.2.3
- From: Dario Bagatto <email@hidden>
- Date: Thu, 1 Jul 2004 11:03:02 +0200
Hello together
I changed one of my servers from WO 5.2.1 to 5.2.3 running on Panther.
I'm running a JavaClient application and as I experienced strange side
effects with 5.2.3, I
examined my application more thoroughly.
When I create and insert an object into the EOEditingContext I can see
the EO in the
insertedObject NSArray with an EOTemporaryGlobalID (as expected).
Now I invoke saveChanges, the data is saved into the database.
After saving, the EO is removed from insertedObjects and is available
in the registeredObject
NSArray. GlobalIDChangedNotification is sent BUT the EO still has an
EOTemporaryGlobalID and
not an EOGlobalID as it should be!!
This leads to the big problem that uniquing does not work anymore
correctly. When I fetch the
same EO again, after the save, into the context I now have TWO Objects
representing and pointing
to the same data in the database. One with an EOTemporaryGlobalID and
one with an EOGlobalID.
I'm puzzled the same application works flawlessly with WO 5.2.1
Any ideas what's wrong here, am I missing something?
Thanks for any help
Dario
_______________________________________________
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.