On Wed, Oct 20, 2004 at 11:57:42AM -0400, Andrew Sullivan wrote: > Now, how do you handle the cases where either the transaction fails > so you can't set it to 3? Simple: your client captures errors and > then sets the value back to 1 later.
Has anyone read "the Sagas paper" by Garcia-Molina? They present a way to handle "extended transaction models", trying to cope sort-of automatically with this kind of situations. More generally, AFAIU the idea is to have multi-transaction recoverability and rollback-ability. It seems interesting. http://portal.acm.org/citation.cfm?doid=38713.38742 I have only skimmed through it, but it sounds somewhat interesting. I'd love to know what do people think of this. -- Alvaro Herrera (<alvherre[a]dcc.uchile.cl>) "Los dioses no protegen a los insensatos. Éstos reciben protección de otros insensatos mejor dotados" (Luis Wu, Mundo Anillo) ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
