[sql] Import reference version of SQLite 3.8.7.4.

third_party/sqlite/sqlite-src-3080704/test/attach2.test

Index: third_party/sqlite/sqlite-src-3080704/test/attach2.test
diff --git a/third_party/sqlite/sqlite-src-3070603/test/attach2.test b/third_party/sqlite/sqlite-src-3080704/test/attach2.test
similarity index 97%
copy from third_party/sqlite/sqlite-src-3070603/test/attach2.test
copy to third_party/sqlite/sqlite-src-3080704/test/attach2.test
index 3cc5af961bbc9c17b4fa103a7c4ee9d93d0b5412..f8705685419e6ede6afa710d211619c8106846c8 100644
--- a/third_party/sqlite/sqlite-src-3070603/test/attach2.test
+++ b/third_party/sqlite/sqlite-src-3080704/test/attach2.test
@@ -33,8 +33,8 @@ do_test attach2-1.1 {
     CREATE TABLE t1(a,b);
     CREATE INDEX x1 ON t1(a);
   }
-  file delete -force test2.db
-  file delete -force test2.db-journal
+  forcedelete test2.db
+  forcedelete test2.db-journal
   sqlite3 db2 test2.db
   db2 eval {
     CREATE TABLE t1(a,b);
@@ -327,7 +327,7 @@ do_test attach2-4.15 {
 
 db close
 db2 close
-file delete -force test2.db
+forcedelete test2.db
 sqlite3_soft_heap_limit $soft_limit
 
 # These tests - attach2-5.* - check that the master journal file is deleted
@@ -335,7 +335,7 @@ sqlite3_soft_heap_limit $soft_limit
 #
 # Update: It's not actually created if a rollback occurs, so that test
 # doesn't really prove too much.
-foreach f [glob test.db*] {file delete -force $f}
+foreach f [glob test.db*] {forcedelete $f}
 do_test attach2-5.1 {
   sqlite3 db test.db
   execsql {
@@ -377,6 +377,9 @@ do_test attach2-6.2 {
   }
 } {1 {cannot ATTACH database within transaction}}
 
+# EVIDENCE-OF: R-59740-55581 This statement will fail if SQLite is in
+# the middle of a transaction.
+#
 do_test attach2-6.3 {
   catchsql {
     DETACH aux;