Import SQLite 3.7.6.3.

third_party/sqlite/src/test/alter2.test

 # 2005 February 18
 #
 # 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.
 #
 #*************************************************************************
 # This file implements regression tests for SQLite library.  The
 # focus of this script is testing that SQLite can handle a subtle 
 # file format change that may be used in the future to implement
 # "ALTER TABLE ... ADD COLUMN".
 #
 # $Id: alter2.test,v 1.14 2009/04/07 14:14:22 danielk1977 Exp $
 #
 
 set testdir [file dirname $argv0]
 source $testdir/tester.tcl
 
 # We have to have pragmas in order to do this test
 ifcapable {!pragma} return
 
-# These tests do not work if there is a codec. 
+# Do not use a codec for tests in this file, as the database file is
+# manipulated directly using tcl scripts. See proc [set_file_format].
 #
-#if {[catch {sqlite3 -has_codec} r] || $r} return
+do_not_use_codec
 
 # The file format change affects the way row-records stored in tables (but 
 # not indices) are interpreted. Before version 3.1.3, a row-record for a 
 # table with N columns was guaranteed to contain exactly N fields. As
 # of version 3.1.3, the record may contain up to N fields. In this case
 # the M fields that are present are the values for the left-most M 
 # columns. The (N-M) rightmost columns contain NULL.
 #
 # If any records in the database contain less fields than their table
 # has columns, then the file-format meta value should be set to (at least) 2. 
@@ skipping 27 matching lines @@
   set t [string map {' ''} $tbl]
   dbat eval [subst {
     PRAGMA writable_schema = 1;
     UPDATE sqlite_master SET sql = '$s' WHERE name = '$t' AND type = 'table';
     PRAGMA writable_schema = 0;
   }]
   dbat close
   set_file_format 2
 }
 
+# Create bogus application-defined functions for functions used 
+# internally by ALTER TABLE, to ensure that ALTER TABLE falls back
+# to the built-in functions.
+#
+proc failing_app_func {args} {error "bad function"}
+do_test alter2-1.0 {
+  db func substr failing_app_func
+  db func like failing_app_func
+  db func sqlite_rename_table failing_app_func
+  db func sqlite_rename_trigger failing_app_func
+  db func sqlite_rename_parent failing_app_func
+  catchsql {SELECT substr('abcdefg',1,3)}
+} {1 {bad function}}
+
+
 #-----------------------------------------------------------------------
 # Some basic tests to make sure short rows are handled.
 #
 do_test alter2-1.1 {
   execsql {
     CREATE TABLE abc(a, b);
     INSERT INTO abc VALUES(1, 2);
     INSERT INTO abc VALUES(3, 4);
     INSERT INTO abc VALUES(5, 6);
   }
@@ skipping 141 matching lines @@
 
 #---------------------------------------------------------------------
 # Check that an error occurs if the database is upgraded to a file
 # format that SQLite does not support (in this case 5). Note: The 
 # file format is checked each time the schema is read, so changing the
 # file format requires incrementing the schema cookie.
 #
 do_test alter2-4.1 {
   db close
   set_file_format 5
-  sqlite3 db test.db
+  catch { sqlite3 db test.db }
+  set {} {}
 } {}
 do_test alter2-4.2 {
   # We have to run two queries here because the Tcl interface uses
   # sqlite3_prepare_v2(). In this case, the first query encounters an 
   # SQLITE_SCHEMA error. Then, when trying to recompile the statement, the
   # "unsupported file format" error is encountered. So the error code
   # returned is SQLITE_SCHEMA, not SQLITE_ERROR as required by the following
   # test case.
   #
   # When the query is attempted a second time, the same error message is
@@ skipping 194 matching lines @@
     }
   } {a b d}
   do_test alter2-10.4 {
     execsql {
       SELECT count(b) FROM t2 WHERE b = X'ABCD';
     }
   } {3}
 }
 
 finish_test