[sql] Import SQLite 3.17.0.

third_party/sqlite/src/test/e_walhook.test

 # 2014 December 04
 #
 # 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 143 matching lines @@
 # been replaced.
 proc my_new_wal_hook {args} { return 0 }
 db wal_hook my_new_wal_hook
 do_test 5.2 {
   execsql { INSERT INTO t1 VALUES(11) }
   set ::old_wal_hook
 } {1}
 
 
 
-# EVIDENCE-OF: R-42842-27162 Note that the sqlite3_wal_autocheckpoint()
+# EVIDENCE-OF: R-57445-43425 Note that the sqlite3_wal_autocheckpoint()
 # interface and the wal_autocheckpoint pragma both invoke
-# sqlite3_wal_hook() and will those overwrite any prior
-# sqlite3_wal_hook() settings.
+# sqlite3_wal_hook() and will overwrite any prior sqlite3_wal_hook()
+# settings.
 #
 set ::old_wal_hook 0
 proc my_old_wal_hook {args} { incr ::old_wal_hook ; return 0 }
 db wal_hook my_old_wal_hook
 do_test 6.1.1 {
   execsql { INSERT INTO t1 VALUES(12) }
   set ::old_wal_hook
 } {1}
 do_test 6.1.2 {
   execsql { PRAGMA wal_autocheckpoint = 1000 }
@@ skipping 13 matching lines @@
 #
 # EVIDENCE-OF: R-23378-42536 The second is a copy of the database
 # handle.
 #
 #    There is an assert() in the C wal-hook used by tclsqlite.c to
 #    prove this. And that hook has been invoked multiple times when
 #    running this script. So consider this requirement tested as well.
 #
 
 finish_test