I'm looking through the DBI documentation and I can't find anything about sub transactions (eg; if you do a "begin_work" ... "commit/rollback" when begin_work has already been called).
This seems to work under DBD::Pg. Under DBD::mysql, I'm not sure if the begin_work is just being ignored, or if creating sub-transactions is the cause of my woes. (see http://rt.cpan.org/NoAuth/Bug.html?id=15803). I think some pod on the "Transactions" heading of the DBI manpage would be useful, telling us what to expect (even if it is the unexpected) when we use sub-transactions under DBI. If this is an engine-specific thing, could DBI be made to be capable of figuring out whether a particular engine supports sub-transactions? Then any sub-begin-works could just be ignored, and, say, attempting to "commit" when a "rollback" has already been called could cause a fatal error. Or is there already some way to take care of this? There's very little about transactions in the DBI documentation. Thanks, Tyler
