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 the beginning and the end of all requests,
> just to be safe :)
Ok, thanks everybody, I've got. You do rollback just to be sure that you
don't leave things open... That's an interesting technique.
On Thu, 14 Dec 2000, Bruce W. Hoylman wrote:
> Interesting behavior ... I did not know Apache::DBI did this!
Changes:
0.84 August 21, 1999
- the PerlCleanupHandler in Apache::DBI.pm, which is supposed
to initiate a rollback in case AutoCommit is off, will only be
created, if the initial data_source sets AutoCommit to 0.
0.82 June 03, 1999
- proposal from Honza Pazdziora <[EMAIL PROTECTED]>:
add PerlCleanupHandler in Apache::DBI, which issues a rollback
unless AutoCommit is on.
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://logilune.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
