1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340
|
# 2006 November 08
#
# 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.
#
# This file tests the various conditions under which an SQLITE_SCHEMA
# error should be returned. This is a copy of schema.test that
# has been altered to use sqlite3_prepare_v2 instead of sqlite3_prepare
#
# $Id: schema2.test,v 1.4 2009/02/04 17:40:58 drh Exp $
#---------------------------------------------------------------------
# When any of the following types of SQL statements or actions are
# executed, all pre-compiled statements are invalidated. An attempt
# to execute an invalidated statement always returns SQLITE_SCHEMA.
#
# CREATE/DROP TABLE...................................schema2-1.*
# CREATE/DROP VIEW....................................schema2-2.*
# CREATE/DROP TRIGGER.................................schema2-3.*
# CREATE/DROP INDEX...................................schema2-4.*
# DETACH..............................................schema2-5.*
# Deleting a user-function............................schema2-6.*
# Deleting a collation sequence.......................schema2-7.*
# Setting or changing the authorization function......schema2-8.*
#
# Test cases schema2-9.* and schema2-10.* test some specific bugs
# that came up during development.
#
# Test cases schema2-11.* test that it is impossible to delete or
# change a collation sequence or user-function while SQL statements
# are executing. Adding new collations or functions is allowed.
#
set testdir [file dirname $argv0]
source $testdir/tester.tcl
do_test schema2-1.1 {
set ::STMT [sqlite3_prepare_v2 $::DB {SELECT * FROM sqlite_master} -1 TAIL]
execsql {
CREATE TABLE abc(a, b, c);
}
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-1.2 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
do_test schema2-1.3 {
set ::STMT [sqlite3_prepare_v2 $::DB {SELECT * FROM sqlite_master} -1 TAIL]
execsql {
DROP TABLE abc;
}
sqlite3_step $::STMT
} {SQLITE_DONE}
do_test schema2-1.4 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
ifcapable view {
do_test schema2-2.1 {
set ::STMT [sqlite3_prepare_v2 $::DB {SELECT * FROM sqlite_master} -1 TAIL]
execsql {
CREATE VIEW v1 AS SELECT * FROM sqlite_master;
}
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-2.2 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
do_test schema2-2.3 {
set ::STMT [sqlite3_prepare_v2 $::DB {SELECT * FROM sqlite_master} -1 TAIL]
execsql {
DROP VIEW v1;
}
sqlite3_step $::STMT
} {SQLITE_DONE}
do_test schema2-2.4 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
}
ifcapable trigger {
do_test schema2-3.1 {
execsql {
CREATE TABLE abc(a, b, c);
}
set ::STMT [sqlite3_prepare_v2 $::DB {SELECT * FROM sqlite_master} -1 TAIL]
execsql {
CREATE TRIGGER abc_trig AFTER INSERT ON abc BEGIN
SELECT 1, 2, 3;
END;
}
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-3.2 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
do_test schema2-3.3 {
set ::STMT [sqlite3_prepare_v2 $::DB {SELECT * FROM sqlite_master} -1 TAIL]
execsql {
DROP TRIGGER abc_trig;
}
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-3.4 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
}
do_test schema2-4.1 {
catchsql {
CREATE TABLE abc(a, b, c);
}
set ::STMT [sqlite3_prepare_v2 $::DB {SELECT * FROM sqlite_master} -1 TAIL]
execsql {
CREATE INDEX abc_index ON abc(a);
}
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-4.2 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
do_test schema2-4.3 {
set ::STMT [sqlite3_prepare_v2 $::DB {SELECT * FROM sqlite_master} -1 TAIL]
execsql {
DROP INDEX abc_index;
}
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-4.4 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
#---------------------------------------------------------------------
# Tests 5.1 to 5.4 check that prepared statements are invalidated when
# a database is DETACHed (but not when one is ATTACHed).
#
ifcapable attach {
do_test schema2-5.1 {
set sql {SELECT * FROM abc;}
set ::STMT [sqlite3_prepare_v2 $::DB $sql -1 TAIL]
execsql {
ATTACH 'test2.db' AS aux;
}
sqlite3_step $::STMT
} {SQLITE_DONE}
do_test schema2-5.2 {
sqlite3_reset $::STMT
} {SQLITE_OK}
do_test schema2-5.3 {
execsql {
DETACH aux;
}
sqlite3_step $::STMT
} {SQLITE_DONE}
do_test schema2-5.4 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
}
#---------------------------------------------------------------------
# Tests 6.* check that prepared statements are invalidated when
# a user-function is deleted (but not when one is added).
do_test schema2-6.1 {
set sql {SELECT * FROM abc;}
set ::STMT [sqlite3_prepare_v2 $::DB $sql -1 TAIL]
db function hello_function {}
sqlite3_step $::STMT
} {SQLITE_DONE}
do_test schema2-6.2 {
sqlite3_reset $::STMT
} {SQLITE_OK}
do_test schema2-6.3 {
sqlite_delete_function $::DB hello_function
sqlite3_step $::STMT
} {SQLITE_DONE}
do_test schema2-6.4 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
#---------------------------------------------------------------------
# Tests 7.* check that prepared statements are invalidated when
# a collation sequence is deleted (but not when one is added).
#
ifcapable utf16 {
do_test schema2-7.1 {
set sql {SELECT * FROM abc;}
set ::STMT [sqlite3_prepare_v2 $::DB $sql -1 TAIL]
add_test_collate $::DB 1 1 1
sqlite3_step $::STMT
} {SQLITE_DONE}
do_test schema2-7.2 {
sqlite3_reset $::STMT
} {SQLITE_OK}
do_test schema2-7.3 {
add_test_collate $::DB 0 0 0
sqlite3_step $::STMT
} {SQLITE_DONE}
do_test schema2-7.4 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
}
#---------------------------------------------------------------------
# Tests 8.1 and 8.2 check that prepared statements are invalidated when
# the authorization function is set.
#
ifcapable auth {
do_test schema2-8.1 {
set ::STMT [sqlite3_prepare_v2 $::DB {SELECT * FROM sqlite_master} -1 TAIL]
db auth {}
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-8.3 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
}
#---------------------------------------------------------------------
# schema2-9.1: Test that if a table is dropped by one database connection,
# other database connections are aware of the schema change.
# schema2-9.2: Test that if a view is dropped by one database connection,
# other database connections are aware of the schema change.
#
do_test schema2-9.1 {
sqlite3 db2 test.db
execsql {
DROP TABLE abc;
} db2
db2 close
catchsql {
SELECT * FROM abc;
}
} {1 {no such table: abc}}
execsql {
CREATE TABLE abc(a, b, c);
}
ifcapable view {
do_test schema2-9.2 {
execsql {
CREATE VIEW abcview AS SELECT * FROM abc;
}
sqlite3 db2 test.db
execsql {
DROP VIEW abcview;
} db2
db2 close
catchsql {
SELECT * FROM abcview;
}
} {1 {no such table: abcview}}
}
#---------------------------------------------------------------------
# Test that if a CREATE TABLE statement fails because there are other
# btree cursors open on the same database file it does not corrupt
# the sqlite_master table.
#
# 2007-05-02: These tests have been overcome by events. Open btree
# cursors no longer block CREATE TABLE. But there is no reason not
# to keep the tests in the test suite.
#
do_test schema2-10.1 {
execsql {
INSERT INTO abc VALUES(1, 2, 3);
}
set sql {SELECT * FROM abc}
set ::STMT [sqlite3_prepare_v2 $::DB $sql -1 TAIL]
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-10.2 {
catchsql {
CREATE TABLE t2(a, b, c);
}
} {0 {}}
do_test schema2-10.3 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
do_test schema2-10.4 {
sqlite3 db2 test.db
execsql {
SELECT * FROM abc
} db2
} {1 2 3}
do_test schema2-10.5 {
db2 close
} {}
#---------------------------------------------------------------------
# Attempting to delete or replace a user-function or collation sequence
# while there are active statements returns an SQLITE_BUSY error.
#
# schema2-11.1 - 11.4: User function.
# schema2-11.5 - 11.8: Collation sequence.
#
do_test schema2-11.1 {
db function tstfunc {}
set sql {SELECT * FROM abc}
set ::STMT [sqlite3_prepare_v2 $::DB $sql -1 TAIL]
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-11.2 {
sqlite_delete_function $::DB tstfunc
} {SQLITE_BUSY}
do_test schema2-11.3 {
set rc [catch {
db function tstfunc {}
} msg]
list $rc $msg
} {1 {unable to delete/modify user-function due to active statements}}
do_test schema2-11.4 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
do_test schema2-11.5 {
db collate tstcollate {}
set sql {SELECT * FROM abc}
set ::STMT [sqlite3_prepare_v2 $::DB $sql -1 TAIL]
sqlite3_step $::STMT
} {SQLITE_ROW}
do_test schema2-11.6 {
sqlite_delete_collation $::DB tstcollate
} {SQLITE_BUSY}
do_test schema2-11.7 {
set rc [catch {
db collate tstcollate {}
} msg]
list $rc $msg
} {1 {unable to delete/modify collation sequence due to active statements}}
do_test schema2-11.8 {
sqlite3_finalize $::STMT
} {SQLITE_OK}
finish_test
|