On Sun, May 19, 2002 at 11:50:48AM +0100, Nicholas Clark wrote: > However, we also used perl talking to Oracle. And we had this nasty revelation: > > BEWARE OF TRANSACTIONS >
This is a really good description of the perils of two-phase commits, i.e. the situation where rollbacks must be synchronised. Thus, why you shouldn't use languages whose database interfaces don't support two-phase commits in code that requires two phase commits. Without wishing to start an egregious flamewar, Java has done this for quite some time and might go some decent way to explaining why folks don't take perl seriously for "enterprise" type of work. As an aside, I'd tend to err on the side of *not* rolling back once the user has hit submit. The Stop button, IMO, is not a UI widget for cancelling e-commerce transactions. The user will get an email after the transaction starts saying "cheers, your stuff's in the mail" and then if they can call the support number and cancel the order. Paul -- Paul Makepeace ....................................... http://paulm.com/ "What is parsley? Samba!" -- http://paulm.com/toys/surrealism/
