I generally only add something to the DBI when the DBI can 'fake it'
for drivers that can't do it themselves. In this case the DBI will
count execute()/do() calls and reset the counter on commit()/rollback().
Then the counter can be used to control the warning for drivers that
can't tell if they're in a transaction or not.



Why don't you let the drivers implement this themselves? Even if they can't tell if they're in a transaction, they can do the counting. There's no way to have a transaction span multiple drivers (or is there?), so it should be at the driver level.


Henri.

Reply via email to