RE: Ordering of operations in editingContext
RE: Ordering of operations in editingContext
- Subject: RE: Ordering of operations in editingContext
- From: "dov rosenberg" <email@hidden>
- Date: Thu, 28 Aug 2003 09:30:26 -0400
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.
Dov Rosenberg
-----Original Message-----
From: email@hidden
[mailto:email@hidden]On Behalf Of Kaj Hejer
Sent: Thursday, August 28, 2003 8:47 AM
To: email@hidden
Subject: Ordering of operations in editingContext
Hi!
Some times it's critical to do database operations in a given order; i.e.
that deletes is performed before inserts. Usually this works fine, but
sometimes the operations is mixed up, and that can mess up a saveChanges.
To solve this, you can use the delegate
"adaptorChannelWillPerformOperations" and fix the order yourself. This can
solve some things, but it can be difficult since this delegate doesn't know
about states in components and sessions.
Why doesn't editingContexts keep the order of when operations is done? Is it
possible to force it to?
Thanks in advance!!
-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.
_______________________________________________
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.