Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(410)

Unified Diff: third_party/sqlite/sqlite-src-3080704/test/tkt3093.test

Issue 2363173002: [sqlite] Remove obsolete reference version 3.8.7.4. (Closed)
Patch Set: Created 4 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/sqlite/sqlite-src-3080704/test/tkt3093.test
diff --git a/third_party/sqlite/sqlite-src-3080704/test/tkt3093.test b/third_party/sqlite/sqlite-src-3080704/test/tkt3093.test
deleted file mode 100644
index 3be46d15cfec7fc4aa968fa52c6620186e431545..0000000000000000000000000000000000000000
--- a/third_party/sqlite/sqlite-src-3080704/test/tkt3093.test
+++ /dev/null
@@ -1,86 +0,0 @@
-# 2008 May 2
-#
-# The author disclaims copyright to this source code. In place of
-# a legal notice, here is a blessing:
-#
-# May you do good and not evil.
-# May you find forgiveness for yourself and forgive others.
-# May you share freely, never taking more than you give.
-#
-#***********************************************************************
-#
-# Ticket #3093
-#
-# Verify that a busy callback waiting on a reserved lock resolves
-# once the lock clears.
-#
-# $Id: tkt3093.test,v 1.2 2008/05/02 14:23:55 drh Exp $
-#
-
-set testdir [file dirname $argv0]
-source $testdir/tester.tcl
-
-# Set up a test database
-#
-do_test tkt3093.1 {
- db eval {
- CREATE TABLE t1(x);
- INSERT INTO t1 VALUES(1);
- SELECT * FROM t1
- }
-} {1}
-
-# Establish a separate, independent connection to that database.
-#
-do_test tkt3093.2 {
- catch {sqlite3_enable_shared_cache 0}
- sqlite3 db2 test.db
- db2 eval {
- SELECT * FROM t1
- }
-} {1}
-
-# Make sure that clearing a lock allows a pending request for
-# a reserved lock to continue.
-#
-do_test tkt3093.3 {
- # This will be the busy callback for connection db2. On the first
- # busy callback, commit the transaction in db. This should clear
- # the lock so that there should not be a second callback. If the
- # busy handler is called a second time, then fail so that we get
- # timeout.
- proc busy_callback {cnt} {
- if {$cnt==0} {
- db eval COMMIT
- return 0
- } else {
- return 1
- }
- }
- db2 busy ::busy_callback
-
- # Start a write transaction on db.
- db eval {
- BEGIN;
- INSERT INTO t1 VALUES(2);
- }
-
- # Attempt to modify the database on db2
- catchsql {
- UPDATE t1 SET x=x+1;
- } db2
-} {0 {}}
-
-# Verify that everything worked as expected. The db transaction should
-# have gone first and added entry 2. Then the db2 transaction would have
-# run and added one to each entry.
-#
-do_test tkt3093.4 {
- db eval {SELECT * FROM t1}
-} {2 3}
-do_test tkt3093.5 {
- db2 eval {SELECT * FROM t1}
-} {2 3}
-db2 close
-
-finish_test
« no previous file with comments | « third_party/sqlite/sqlite-src-3080704/test/tkt3080.test ('k') | third_party/sqlite/sqlite-src-3080704/test/tkt3121.test » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698