Import SQLite 3.7.6.3.

third_party/sqlite/src/test/io.test

 # 2007 August 21
 #
 # 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.
 #
 #***********************************************************************
@@ skipping 182 matching lines @@
   execsql { COMMIT }
   list [nWrite db] [nSync]
 } {3 4}
 
 # Test that the journal file is created and sync()d if the transaction
 # modifies a single database page and also appends a page to the file.
 # Internally, this case is handled differently to the one above. The
 # journal file is not actually created until the 'COMMIT' statement
 # is executed.
 #
+# Changed 2010-03-27:  The size of the database is now stored in 
+# bytes 28..31 and so when a page is added to the database, page 1
+# is immediately modified and the journal file immediately comes into
+# existance.  To fix this test, the BEGIN is changed into a a
+# BEGIN IMMEDIATE and the INSERT is omitted.
+#
 do_test io-2.6.1 {
   execsql {
-    BEGIN;
-    INSERT INTO abc VALUES(9, randstr(1000,1000));
+    BEGIN IMMEDIATE;
+    -- INSERT INTO abc VALUES(9, randstr(1000,1000));
   }
   file exists test.db-journal
 } {0}
 do_test io-2.6.2 {
   # Create a file at "test.db-journal". This will prevent SQLite from
   # opening the journal for exclusive access. As a result, the COMMIT
   # should fail with SQLITE_CANTOPEN and the transaction rolled back.
   #
   file mkdir test.db-journal
-  catchsql { COMMIT }
+  catchsql {
+    INSERT INTO abc VALUES(9, randstr(1000,1000));
+    COMMIT
+  }
 } {1 {unable to open database file}}
 do_test io-2.6.3 {
   file delete -force test.db-journal
   catchsql { COMMIT }
-} {1 {cannot commit - no transaction is active}}
+} {0 {}}
 do_test io-2.6.4 {
   execsql { SELECT * FROM abc }
 } {1 2 3 4 5 6 7 8}
 
 # Test that if the database modification is part of multi-file commit,
 # the journal file is always created. In this case, the journal file
 # is created during execution of the COMMIT statement, so we have to
 # use the same technique to check that it is created as in the above 
 # block.
 file delete -force test2.db test2.db-journal
@@ skipping 315 matching lines @@
   do_test io-5.$tn {
     execsql {
       CREATE TABLE abc(a, b, c);
     }
     expr {[file size test.db]/2}
   } $pgsize
 }
 
 sqlite3_simulate_device -char {} -sectorsize 0
 finish_test