Revision c0fd5754fdbd8124bf516c81aa548ba871462d23 authored by Anthony Brummett on 21 August 2013, 19:39:53 UTC, committed by Anthony Brummett on 21 August 2013, 19:39:53 UTC
Base RDBMS datasources have AutoCommit off, but derived classes can turn it on.
If it's on, we need to explicitly start a transaction before altering any data
in case there's a problem in the commit, so we can rollback the partially saved
changes.

As the comment shows, DBI docs say that starting a transaction when AutoCommit
is on will temporarily turn it off until the transaction is over (commit or
rollback)
1 parent fe2afdc
History
File Mode Size
alt
bin
dist-maint
gmt-web
lib
pod
t
ubuntu-lucid
.gitignore -rw-r--r-- 289 bytes
Build.PL -rw-r--r-- 3.2 KB
Changes -rw-r--r-- 15.8 KB
INSTALL -rw-r--r-- 57 bytes
LICENSE -rw-r--r-- 40.7 KB
MANIFEST -rw-r--r-- 21.7 KB
MANIFEST.SKIP -rw-r--r-- 132 bytes
META.json -rw-r--r-- 37.6 KB
META.yml -rw-r--r-- 25.9 KB
MYMETA.json -rw-r--r-- 38.4 KB
MYMETA.yml -rw-r--r-- 27.2 KB
README -rw-r--r-- 1.4 KB
debian l--------- 12 bytes
doc l--------- 13 bytes

README

back to top