From: "Skip Walker" <[EMAIL PROTECTED]> > > This question is a best practices question. > > How are users of Turbine dealing with actions where all or none transactions > would be desired? > > For instance, I have an action that needs to add something to one of my > database tables, and then perform several operations on the turbine > user/security database tables. If one of these steps fail, then I would > like the whole action to fail, and roll back. This doesn't seem like a > unique problem, so I was wondering what kind of solutions people had.
The current security implementation does not use transactions. I still haven't got around to posting my hack/patch to overcome the problem highlighted in the extend-user-howto, but further work is necessary to enable transactions. > > Skip > Scott -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
