1
0
mirror of https://github.com/sqlite/sqlite.git synced 2025-08-01 06:27:03 +03:00

Do now allow a COMMIT to occur while even a single write operating is

in progress. (CVS 6790)

FossilOrigin-Name: 605520ec04061e389226fbec59f7aedf674b3c4e
This commit is contained in:
drh
2009-06-19 22:23:41 +00:00
parent bf66446972
commit 9eb8cbe5c0
4 changed files with 19 additions and 14 deletions

View File

@ -9,7 +9,7 @@
#
#***********************************************************************
#
# $Id: incrblob.test,v 1.23 2008/11/05 16:37:35 drh Exp $
# $Id: incrblob.test,v 1.24 2009/06/19 22:23:42 drh Exp $
#
set testdir [file dirname $argv0]
@ -451,8 +451,8 @@ do_test incrblob-6.9 {
} {}
# At this point rollback should be illegal (because
# there is an open blob channel). But commit is allowed because
# the blob is read-only.
# there is an open blob channel). But commit is also illegal because
# the open blob is read-write.
#
do_test incrblob-6.10 {
catchsql {
@ -463,7 +463,7 @@ do_test incrblob-6.11 {
catchsql {
COMMIT;
} db2
} {0 {}}
} {1 {cannot commit transaction - SQL statements in progress}}
do_test incrblob-6.12 {
execsql {
@ -474,6 +474,11 @@ do_test incrblob-6.13 {
close $::blob
} {}
do_test incrblob-6.14 {
catchsql {
COMMIT;
} db2
} {0 {}}
do_test incrblob-6.15 {
execsql {
SELECT * FROM blobs WHERE rowid = 4;
}