Import SQLite 3.7.6.3.

third_party/sqlite/src/test/capi2.test

 # 2003 January 29
 #
 # 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 53 matching lines @@
 } {t1 1}
 do_test capi2-1.5 {
   get_column_names $VM
 } {name rowid text INTEGER}
 do_test capi2-1.6 {
   sqlite3_step $VM 
 } {SQLITE_DONE}
 do_test capi2-1.7 {
   list [sqlite3_column_count $VM] [get_row_values $VM] [get_column_names $VM]
 } {2 {} {name rowid text INTEGER}}
-do_test capi2-1.8-misuse {
-  sqlite3_step $VM
-} {SQLITE_MISUSE}
+
+# This used to be SQLITE_MISUSE.  But now we automatically reset prepared
+# statements.
+ifcapable autoreset {
+  do_test capi2-1.8 {
+    sqlite3_step $VM
+  } {SQLITE_ROW}
+} else {
+  do_test capi2-1.8 {
+    sqlite3_step $VM
+  } {SQLITE_MISUSE}
+}
 
 # Update: In v2, once SQLITE_MISUSE is returned the statement handle cannot
 # be interrogated for more information. However in v3, since the column
 # count, names and types are determined at compile time, these are still
 # accessible after an SQLITE_MISUSE error.
 do_test capi2-1.9 {
+  sqlite3_reset $VM
   list [sqlite3_column_count $VM] [get_row_values $VM] [get_column_names $VM]
 } {2 {} {name rowid text INTEGER}}
 do_test capi2-1.10 {
   sqlite3_data_count $VM
 } {0}
 
 do_test capi2-1.11 {
   sqlite3_finalize $VM
 } {SQLITE_OK}
 
@@ skipping 689 matching lines @@
   do_test capi2-13.11 {
     check_origins {select * from (select * from tab1 limit 10 offset 10)}
   } [list {main tab1 col1} {main tab1 col2}]
 }
 
 
 } ;# ifcapable columnmetadata
 
 db2 close
 finish_test