I have to wonder: _why_ is DESTROY not being called for this query and others like it? Since these are not persistent db connections, at some point the object will go out of scope and DESTROY should be called.
Is it that you have sql calls that need commit()'ing before the object goes out of scope? Or is it that the script may croak before DESTROY gets called? If it's the first case, then explicitly calling commit() (or a sub to do it for you) is the way to go. If it's the latter, perhaps you need to hijack the SIGDIE long enough to make sure any commits that need doing get done.
In reply to Re: Committing database transactions with DESTROY
by AidanLee
in thread Committing database transactions with DESTROY
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |