I have a strange problem with mysql 4.1 (innodb engine) and DBD::mysql 2.9006:
A dbh->begin_work immediately after a dbh->commit fails with
the error "Already in a transaction".
A level 2 trace shows that there are indeed no other DBI calls between
these two:
-> commit for DBD::mysql::db (DBI::db=HASH(0x872feb4)~0x8753170) thr#814bf18
<- commit= 1 at MySQL.pm line 141
-> begin_work in DBD::_::db for DBD::mysql::db
(DBI::db=HASH(0x872feb4)~0x8753170) thr#814bf18
1 -> FETCH for DBD::mysql::db (DBI::db=HASH(0x8753170)~INNER 'AutoCommit')
thr#814bf18
1 <- FETCH= '' at DBI.pm line 1623
1 -> set_err in DBD::_::common for DBD::mysql::db
(DBI::db=HASH(0x8753170)~INNER 1 'Already in a transaction') thr#814bf18
!! ERROR: 1 'Already in a transaction' (err#1)
1 <- set_err= undef at DBI.pm line 1623
!! ERROR: 1 'Already in a transaction' (err#1)
<- begin_work= undef at MySQL.pm line 336
How can this happen?
hp
--
_ | Peter J. Holzer | In our modern say,learn,know in a day
|_|_) | Sysadmin WSR | world, perhaps being an expert is an
| | | [EMAIL PROTECTED] | outdated concept.
__/ | http://www.hjp.at/ | -- Catharine Drozdowski on dbi-users.
pgpOYz3Ryu2JV.pgp
Description: PGP signature
