in reply to local & DBD::mysql

One caveat, as gleaned from the Class::DBI source code - this approach seems to leak memory "on older perls", whatever versions that might be. Other than that, I think your approach is fine, as it does automagic cleanup/restoration of the previous state.

I think that you got the AutoCommit thing wrong though - AutoCommit should be a false value if you want to issue your transaction statements (begin transaction/commit transaction) yourself. But DBI will warn you about ineffective commit statements anyway.

Replies are listed 'Best First'.
Re^2: local & DBD::mysql
by shemp (Deacon) on Jun 14, 2005 at 21:26 UTC
    For this particular app, im using perl v5.8.0 for sun4-solaris, so the memory leak probably wont be an issue - i hope.
      There were memory leaks in v5.8.0 as I learnt from this post; BTW this specific problem was solved in v5.8.6 (don't know which release solved it actually). They're probably unrelated memory leak problems, but I wouldn't bet on v5.8.0 not leaking.

      Flavio (perl -e 'print(scalar(reverse("\nti.xittelop\@oivalf")))')

      Don't fool yourself.