AryaWu/sqlite

1# 2004 September 22#3# The author disclaims copyright to this source code.  In place of4# a legal notice, here is a blessing:5#6#    May you do good and not evil.7#    May you find forgiveness for yourself and forgive others.8#    May you share freely, never taking more than you give.9#10#***********************************************************************11# This file implements regression tests for SQLite library.  The12# focus of this script testing the callback-free C/C++ API and in13# particular the behavior of sqlite3_step() when trying to commit14# with lock contention.15#16# $Id: capi3b.test,v 1.4 2007/08/10 19:46:14 drh Exp $17#18 19set testdir [file dirname $argv0]20source $testdir/tester.tcl21 22 23# These tests depend on the pager holding changes in cache24# until it is time to commit.  But that won't happen if the25# soft-heap-limit is set too low.  So disable the soft heap limit26# for the duration of this test.27#28sqlite3_soft_heap_limit 029 30 31set DB [sqlite3_connection_pointer db]32sqlite3 db2 test.db33set DB2 [sqlite3_connection_pointer db2]34 35# Create some data in the database36#37do_test capi3b-1.1 {38  execsql {39    CREATE TABLE t1(x);40    INSERT INTO t1 VALUES(1);41    INSERT INTO t1 VALUES(2);42    SELECT * FROM t143  }44} {1 2}45 46# Make sure the second database connection can see the data47#48do_test capi3b-1.2 {49  execsql {50    SELECT * FROM t151  } db252} {1 2}53 54# First database connection acquires a shared lock55#56do_test capi3b-1.3 {57  execsql {58    BEGIN;59    SELECT * FROM t1;60  }61} {1 2}62 63# Second database connection tries to write.  The sqlite3_step()64# function returns SQLITE_BUSY because it cannot commit.65#66do_test capi3b-1.4 {67  set VM [sqlite3_prepare $DB2 {INSERT INTO t1 VALUES(3)} -1 TAIL]68  sqlite3_step $VM69} SQLITE_BUSY70 71# The sqlite3_step call can be repeated multiple times.72#73do_test capi3b-1.5.1 {74  sqlite3_step $VM75} SQLITE_BUSY76do_test capi3b-1.5.2 {77  sqlite3_step $VM78} SQLITE_BUSY79 80# The first connection closes its transaction.  This allows the second81# connections sqlite3_step to succeed.82#83do_test capi3b-1.6 {84  execsql COMMIT85  sqlite3_step $VM86} SQLITE_DONE87do_test capi3b-1.7 {88  sqlite3_finalize $VM89} SQLITE_OK90do_test capi3b-1.8 {91  execsql {SELECT * FROM t1} db292} {1 2 3}93do_test capi3b-1.9 {94  execsql {SELECT * FROM t1}95} {1 2 3}96 97# Start doing a SELECT with one connection.  This gets a SHARED lock.98# Then do an INSERT with the other connection.  The INSERT should99# not be able to complete until the SELECT finishes.100#101do_test capi3b-2.1 {102  set VM1 [sqlite3_prepare $DB {SELECT * FROM t1} -1 TAIL]103  sqlite3_step $VM1104} SQLITE_ROW105do_test capi3b-2.2 {106  sqlite3_column_text $VM1 0107} 1108do_test capi3b-2.3 {109  set VM2 [sqlite3_prepare $DB2 {INSERT INTO t1 VALUES(4)} -1 TAIL]110  sqlite3_step $VM2111} SQLITE_BUSY112do_test capi3b-2.4 {113  sqlite3_step $VM1114} SQLITE_ROW115do_test capi3b-2.5 {116  sqlite3_column_text $VM1 0117} 2118do_test capi3b-2.6 {119  sqlite3_step $VM2120} SQLITE_BUSY121do_test capi3b-2.7 {122  sqlite3_step $VM1123} SQLITE_ROW124do_test capi3b-2.8 {125  sqlite3_column_text $VM1 0126} 3127do_test capi3b-2.9 {128  sqlite3_step $VM2129} SQLITE_BUSY130do_test capi3b-2.10 {131  sqlite3_step $VM1132} SQLITE_DONE133do_test capi3b-2.11 {134  sqlite3_step $VM2135} SQLITE_DONE136do_test capi3b-2.12 {137  sqlite3_finalize $VM1138  sqlite3_finalize $VM2139  execsql {SELECT * FROM t1}140} {1 2 3 4}141 142catch {db2 close}143 144sqlite3_soft_heap_limit $cmdlinearg(soft-heap-limit)145finish_test146