Re: undefined behaviour for sub-transactions?

Tyler MacDonald <[email protected]> wrote:
> Jochen Wiedmann <[email protected]> wrote:
> > >         Ok. If that's the only behaviour that can be depended on, then I
> > > guess the best choice would be to make a wrapper around the database handle
> > > that keeps track of the transaction status.
> > Did you understand me? There is no such thing as a "transaction
> > status" in DBI. There always is a current, and uncommitted
> > transaction. Nothing more, nothing less.
> 
> 	Yep, I understood perfectly.

	I just took a look on CPAN, and it looks like somebody else has run
into the same problem I have:

	http://search.cpan.org/~porton/DBI-Transaction-0.101/

	But it's licensed under the GPL, so if I wrote my package using it,
I would be encumbered by the GPL by proxy. :-/

		- Tyler

-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/[email protected]