simcop2387/DBD-SQLite-SQLcipher
1
0
Fork 0
mirror of https://github.com/DBD-SQLite/DBD-SQLite synced 2025-06-07 22:28:47 -04:00
Code Issues Releases Wiki Activity

might be better to use the same word class to avoid confusion

Browse source
This commit is contained in:
Kenichi Ishigaki 2015-04-18 16:32:39 +09:00
parent ba815ce91f
commit 4b92383fe4
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
lib/DBD/SQLite.pm
View file

@ -1373,7 +1373,7 @@ operation, and thus it is possible that another thread or process
could create a separate transaction and write to the database after could create a separate transaction and write to the database after
the C<BEGIN> on the current thread has executed, and eventually the C<BEGIN> on the current thread has executed, and eventually
cause a "deadlock". To avoid this, DBD::SQLite internally issues cause a "deadlock". To avoid this, DBD::SQLite internally issues
a C<BEGIN IMMEDIATE> if you begin a transaction by a C<BEGIN IMMEDIATE> if you begin a transaction by calling
C<begin_work> or by turning off C<AutoCommit> (since 1.38_01). C<begin_work> or by turning off C<AutoCommit> (since 1.38_01).
If you really need to turn off this feature for some reasons, If you really need to turn off this feature for some reasons,