Disconnecting, One Way or Another
The transaction
effect of explicitly disconnecting from a
database while AutoCommit
is disabled is, sadly,
undefined. Some database systems, such as Oracle and Ingres, will
automatically commit any outstanding changes. However, other database
systems, such as Informix, will roll back any outstanding changes.
Because of this, applications not using AutoCommit
should always explicitly call
commit()
or rollback()
before
calling
disconnect()
.
So what happens if you don’t explicitly call
disconnect()
, or don’t have the chance to
because the program exits after a die
? Well,
because DBI handles are object references, we can be sure that Perl
itself will call the DESTROY
method for us on each
handle if the program exits, the handle goes out of scope, or the
only copy of a handle is overwritten by another value.
The actual implementation of the
DESTROY
method is in the hands of the driver
author. If the database handle is still connected then it
should automatically call
rollback()
(unless AutoCommit
is enabled) before calling disconnect()
. Calling
rollback()
in DESTROY
is
critical. If the driver doesn’t, then a program aborting due to
a die
part way though a transaction may actually
“accidentally” commit the incomplete transaction!
Fortunately, all the drivers that we’re aware of that support
transactions do the right thing.
As an extra sanity check, if you disconnect from a database while you still have active statement handles, you will get a warning. ...
Get Programming the Perl DBI now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.