I was in the process of updating the Apache::DBI section of the guide with
the notes from the latest version of this package, and there is a new
section about Transactions. Since I use mysql, it doesn't have
transactions so I cannot it's not absolutely clear to me. For example why
the script
Stas Bekman writes:
I was in the process of updating the Apache::DBI section of the guide with
the notes from the latest version of this package, and there is a new
section about Transactions. Since I use mysql, it doesn't have
transactions so I cannot it's not absolutely clear to me.
In case your script makes some db changes "by accident"--if you don't do
an explicit rollback or commit at the end, the uncommitted changes will
hang around, and the next request may end up committing those changes
unwittingly. I rollback at both the beginning and the end of all requests,
just to
"Stas" == Stas Bekman [EMAIL PROTECTED] writes:
Stas In general it is good practice to perform an explicit commit
Stas or rollback at the end of every script. In order to avoid
Stas inconsistencies in the database in case CAutoCommit is
Stas IOff and the script finishes without
On Thu, 14 Dec 2000, Chris Nokleberg wrote:
In case your script makes some db changes "by accident"--if you don't do
an explicit rollback or commit at the end, the uncommitted changes will
hang around, and the next request may end up committing those changes
unwittingly. I rollback at both
