> > > While it would be neat to have such a capability (ie, adding transaction > > monitor capability to DBI), in this present form, the docs will need to be very > > explicit about > > what its capabilities really are (Bold and UPPERCASE THE POD DESCRIPTION). > > > OTOH, might a partial xaction monitor behavior be possible by the DBI > > layer flagging that its "acting as xaction monitor", and then tracking every > > database handle that gets used within the $coderef, and applying the > > rollback/commit to *all* such handles ? It ain't 2PC, but its a start. > > That's a whole different can of works I don't even want to think > about right now as I'm up to my eyes in worms already. But my gut > feel is I don't want to go there at all without doing 2PC properly > via XA APIs. > > > Overthinking again, > > Yes :) > > Tim.
'kay...but, XA issues aside, might a try...catch... type of construct be more "elegant" ? Maybe once I clear my own teetering pile of works, I'll take a stab at a DBIx that implements that behavior. Shouldn't be any later than 2007 or so... Dean Arnold Presicient Corp. www.presicient.com
