From 214cb720b61dbe20ed4b1111616544e878d19e60 Mon Sep 17 00:00:00 2001
From: Nathaniel Nutter <iam@nnutter.com>
Date: Thu, 16 Apr 2015 11:11:13 -0500
Subject: [PATCH] clarify BEGIN IMMEDIATE is used when AutoCommit is off

Clarify that `BEGIN IMMEDIATE` is used when `AutoCommit` is off rather
than when in `AutoCommit` mode.
---
 lib/DBD/SQLite.pm | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/lib/DBD/SQLite.pm b/lib/DBD/SQLite.pm
index 2fe6b72..e07cb9c 100644
--- a/lib/DBD/SQLite.pm
+++ b/lib/DBD/SQLite.pm
@@ -1374,7 +1374,8 @@ could create a separate transaction and write to the database after
 the C<BEGIN> on the current thread has executed, and eventually
 cause a "deadlock". To avoid this, DBD::SQLite internally issues
 a C<BEGIN IMMEDIATE> when you begin a transaction by
-C<begin_work> or under the C<AutoCommit> mode (since 1.38_01).
+C<begin_work> or execute a statement with C<AutoCommit> disabled
+(since 1.38_01).
 
 If you really need to turn off this feature for some reasons,
 set C<sqlite_use_immediate_transaction> database handle attribute