RE: Ordering of operations in editingContext
RE: Ordering of operations in editingContext
- Subject: RE: Ordering of operations in editingContext
- From: Kaj Hejer <email@hidden>
- Date: Thu, 28 Aug 2003 23:09:46 +0200
At 09:30 -0400 28-08-2003, dov rosenberg wrote:
we tried ordering the operations manually but it was too unreliable. On
oracle and postgresql there are options to make the costraints deferrable
until after the transaction has completed before applying the constraints.
Things will still rollback if there is a problem, it just allows all of the
operations to go thru first without having to muck around in the bowels of
EOF. Seems to work pretty well.
Hi!
Thank you for answering!
If we have a table like
PERSON (username [pk], full_name); // empty table
and perform the following in our application (with ec.insertObject
and ec.deleteObject):
insert ('endremr', 'Endre Rognerud');
delete ('endremr', 'Endre Rognerud');
insert ('endremr', 'Endre Rognerud');
saveChanges();
When the sql is gererated by EOF this might turn into
delete ('endremr', 'Endre Rognerud'); // nothing to delete (error)
insert ('endremr', 'Endre Rognerud'); // maybe ok
insert ('endremr', 'Endre Rognerud'); // duplicate (error)
For this example we can't see how making the contraint deferrable will help us.
-Kaj :)
_______________________________________________
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.