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

Back out changes allowing writes to tables that have open cursors. (CVS 2134)

Browse Source 
FossilOrigin-Name: af635cab8a1d761c469e35208dda08a29f0964a1
This commit is contained in:
danielk1977
2004-11-22 10:02:21 +00:00
parent 299b187d76
commit 12b13002ce
9 changed files with 96 additions and 591 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
test/delete2.test
View File

@ -29,7 +29,7 @@
# The solution to the problem was to detect that the table is locked
# before the index entry is deleted.
#
# $Id: delete2.test,v 1.3 2004/11/16 15:50:21 danielk1977 Exp $
# $Id: delete2.test,v 1.4 2004/11/22 10:02:23 danielk1977 Exp $
#
set testdir [file dirname $argv0]
@ -66,26 +66,27 @@ do_test delete2-1.4 {
} SQLITE_ROW
integrity_check delete2-1.5
# Try to delete a row from the table. Before version 3.10 the DELETE
# would fail because of the SELECT active on the table. In 3.10 the
# DELETE is legal.
# Try to delete a row from the table. The delete should fail.
#
do_test delete2-1.6 {
catchsql {
DELETE FROM q WHERE rowid=1
}
} {0 {}}
} {1 {database table is locked}}
integrity_check delete2-1.7
do_test delete2-1.8 {
execsql {
SELECT * FROM q;
}
} {goodbye id.2 again id.3}
} {hello id.1 goodbye id.2 again id.3}
# Finalize the query, thus clearing the lock on the table. Then
# retry the delete. The delete should work this time.
#
do_test delete2-1.9 {
sqlite3_finalize $STMT
catchsql {
DELETE FROM q WHERE rowid=2
DELETE FROM q WHERE rowid=1
}
} {0 {}}
integrity_check delete2-1.10
@ -93,6 +94,6 @@ do_test delete2-1.11 {
execsql {
SELECT * FROM q;
}
} {again id.3}
} {goodbye id.2 again id.3}
finish_test