Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Add further tests to e_createtable.test. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
0a4528d629018eae0b0f3e173ebda666 |
User & Date: | dan 2010-09-30 18:43:14.000 |
Context
2010-09-30
| ||
20:33 | Merge experimental into trunk: Refactor the text-to-numeric conversion routines to work without zero-terminators and in UTF16 as well as UTF8. Avoid invalidating strings with doing affinity conversions. (check-in: 07ee080ec4 user: drh tags: trunk) | |
18:43 | Add further tests to e_createtable.test. (check-in: 0a4528d629 user: dan tags: trunk) | |
2010-09-29
| ||
18:26 | Add test cases to e_createtable.test. (check-in: f34dc54d46 user: dan tags: trunk) | |
Changes
Changes to test/e_createtable.test.
︙ | ︙ | |||
12 13 14 15 16 17 18 19 20 21 22 23 24 25 | # This file implements tests to verify that the "testable statements" in # the lang_createtable.html document are correct. # set testdir [file dirname $argv0] source $testdir/tester.tcl # Test organization: # # e_createtable-0.*: Test that the syntax diagrams are correct. # # e_createtable-1.*: Test statements related to table and database names, # the TEMP and TEMPORARY keywords, and the IF NOT EXISTS clause. # | > > | 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 | # This file implements tests to verify that the "testable statements" in # the lang_createtable.html document are correct. # set testdir [file dirname $argv0] source $testdir/tester.tcl set ::testprefix e_createtable # Test organization: # # e_createtable-0.*: Test that the syntax diagrams are correct. # # e_createtable-1.*: Test statements related to table and database names, # the TEMP and TEMPORARY keywords, and the IF NOT EXISTS clause. # |
︙ | ︙ | |||
1049 1050 1051 1052 1053 1054 1055 1056 | do_createtable_tests 3.9 { 2 "SELECT a FROM t8 ORDER BY a, rowid" {abc ABC {abc } {ABC }} 3 "SELECT b FROM t8 ORDER BY b, rowid" {{ABC } ABC abc {abc }} 4 "SELECT c FROM t8 ORDER BY c, rowid" {ABC {ABC } abc {abc }} 5 "SELECT d FROM t8 ORDER BY d, rowid" {ABC {ABC } abc {abc }} } finish_test | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 | do_createtable_tests 3.9 { 2 "SELECT a FROM t8 ORDER BY a, rowid" {abc ABC {abc } {ABC }} 3 "SELECT b FROM t8 ORDER BY b, rowid" {{ABC } ABC abc {abc }} 4 "SELECT c FROM t8 ORDER BY c, rowid" {ABC {ABC } abc {abc }} 5 "SELECT d FROM t8 ORDER BY d, rowid" {ABC {ABC } abc {abc }} } # EVIDENCE-OF: R-25473-20557 The number of columns in a table is limited # by the SQLITE_MAX_COLUMN compile-time parameter. # proc columns {n} { set res [list] for {set i 0} {$i < $n} {incr i} { lappend res "c$i" } join $res ", " } do_execsql_test e_createtable-3.10.1 [subst { CREATE TABLE t9([columns $::SQLITE_MAX_COLUMN]); }] {} do_catchsql_test e_createtable-3.10.2 [subst { CREATE TABLE t10([columns [expr $::SQLITE_MAX_COLUMN+1]]); }] {1 {too many columns on t10}} # EVIDENCE-OF: R-27775-64721 Both of these limits can be lowered at # runtime using the sqlite3_limit() C/C++ interface. # # A 30,000 byte blob consumes 30,003 bytes of record space. A record # that contains 3 such blobs consumes (30,000*3)+1 bytes of space. Tests # 3.11.4 and 3.11.5, which verify that SQLITE_MAX_LENGTH may be lowered # at runtime, are based on this calculation. # sqlite3_limit db SQLITE_LIMIT_COLUMN 500 do_execsql_test e_createtable-3.11.1 [subst { CREATE TABLE t10([columns 500]); }] {} do_catchsql_test e_createtable-3.11.2 [subst { CREATE TABLE t11([columns 501]); }] {1 {too many columns on t11}} # Check that it is not possible to raise the column limit above its # default compile time value. # sqlite3_limit db SQLITE_LIMIT_COLUMN [expr $::SQLITE_MAX_COLUMN+2] do_catchsql_test e_createtable-3.11.3 [subst { CREATE TABLE t11([columns [expr $::SQLITE_MAX_COLUMN+1]]); }] {1 {too many columns on t11}} sqlite3_limit db SQLITE_LIMIT_LENGTH 90010 do_execsql_test e_createtable-3.11.4 { CREATE TABLE t12(a, b, c); INSERT INTO t12 VALUES(randomblob(30000),randomblob(30000),randomblob(30000)); } {} do_catchsql_test e_createtable-3.11.5 { INSERT INTO t12 VALUES(randomblob(30001),randomblob(30000),randomblob(30000)); } {1 {string or blob too big}} #------------------------------------------------------------------------- # Tests for statements regarding constraints (PRIMARY KEY, UNIQUE, NOT # NULL and CHECK constraints). # # EVIDENCE-OF: R-52382-54248 Each table in SQLite may have at most one # PRIMARY KEY. # # EVIDENCE-OF: R-18080-47271 If there is more than one PRIMARY KEY # clause in a single CREATE TABLE statement, it is an error. # # To test the two above, show that zero primary keys is Ok, one primary # key is Ok, and two or more primary keys is an error. # drop_all_tables do_createtable_tests 4.1.1 { 1 "CREATE TABLE t1(a, b, c)" {} 2 "CREATE TABLE t2(a PRIMARY KEY, b, c)" {} 3 "CREATE TABLE t3(a, b, c, PRIMARY KEY(a))" {} 4 "CREATE TABLE t4(a, b, c, PRIMARY KEY(c,b,a))" {} } do_createtable_tests 4.1.2 -error { table "t5" has more than one primary key } { 1 "CREATE TABLE t5(a PRIMARY KEY, b PRIMARY KEY, c)" {} 2 "CREATE TABLE t5(a, b PRIMARY KEY, c, PRIMARY KEY(a))" {} 3 "CREATE TABLE t5(a INTEGER PRIMARY KEY, b PRIMARY KEY, c)" {} 4 "CREATE TABLE t5(a INTEGER PRIMARY KEY, b, c, PRIMARY KEY(b, c))" {} 5 "CREATE TABLE t5(a PRIMARY KEY, b, c, PRIMARY KEY(a))" {} 6 "CREATE TABLE t5(a INTEGER PRIMARY KEY, b, c, PRIMARY KEY(a))" {} } proc table_pk {tbl} { set pk [list] db eval "pragma table_info($tbl)" a { if {$a(pk)} { lappend pk $a(name) } } set pk } # EVIDENCE-OF: R-41411-18837 If the keywords PRIMARY KEY are added to a # column definition, then the primary key for the table consists of that # single column. # # The above is tested by 4.2.1.* # # EVIDENCE-OF: R-31775-48204 Or, if a PRIMARY KEY clause is specified as # a table-constraint, then the primary key of the table consists of the # list of columns specified as part of the PRIMARY KEY clause. # # The above is tested by 4.2.2.* # do_createtable_tests 4.2 -repair { catchsql { DROP TABLE t5 } } -tclquery { table_pk t5 } { 1.1 "CREATE TABLE t5(a, b INTEGER PRIMARY KEY, c)" {b} 1.2 "CREATE TABLE t5(a PRIMARY KEY, b, c)" {a} 2.1 "CREATE TABLE t5(a, b, c, PRIMARY KEY(a))" {a} 2.2 "CREATE TABLE t5(a, b, c, PRIMARY KEY(c,b,a))" {a b c} 2.3 "CREATE TABLE t5(a, b INTEGER PRIMARY KEY, c)" {b} } # EVIDENCE-OF: R-33986-09410 Each row in a table with a primary key must # feature a unique combination of values in its primary key columns. # # EVIDENCE-OF: R-39102-06737 If an INSERT or UPDATE statement attempts # to modify the table content so that two or more rows feature identical # primary key values, it is a constraint violation. # drop_all_tables do_execsql_test 4.3.0 { CREATE TABLE t1(x PRIMARY KEY, y); INSERT INTO t1 VALUES(0, 'zero'); INSERT INTO t1 VALUES(45.5, 'one'); INSERT INTO t1 VALUES('brambles', 'two'); INSERT INTO t1 VALUES(X'ABCDEF', 'three'); CREATE TABLE t2(x, y, PRIMARY KEY(x, y)); INSERT INTO t2 VALUES(0, 'zero'); INSERT INTO t2 VALUES(45.5, 'one'); INSERT INTO t2 VALUES('brambles', 'two'); INSERT INTO t2 VALUES(X'ABCDEF', 'three'); } {} do_createtable_tests 4.3.1 -error { %s not unique } { 1 "INSERT INTO t1 VALUES(0, 0)" {"column x is"} 2 "INSERT INTO t1 VALUES(45.5, 'abc')" {"column x is"} 3 "INSERT INTO t1 VALUES(0.0, 'abc')" {"column x is"} 4 "INSERT INTO t1 VALUES('brambles', 'abc')" {"column x is"} 5 "INSERT INTO t1 VALUES(X'ABCDEF', 'abc')" {"column x is"} 6 "INSERT INTO t2 VALUES(0, 'zero')" {"columns x, y are"} 7 "INSERT INTO t2 VALUES(45.5, 'one')" {"columns x, y are"} 8 "INSERT INTO t2 VALUES(0.0, 'zero')" {"columns x, y are"} 9 "INSERT INTO t2 VALUES('brambles', 'two')" {"columns x, y are"} 10 "INSERT INTO t2 VALUES(X'ABCDEF', 'three')" {"columns x, y are"} } do_createtable_tests 4.3.2 { 1 "INSERT INTO t1 VALUES(-1, 0)" {} 2 "INSERT INTO t1 VALUES(45.2, 'abc')" {} 3 "INSERT INTO t1 VALUES(0.01, 'abc')" {} 4 "INSERT INTO t1 VALUES('bramble', 'abc')" {} 5 "INSERT INTO t1 VALUES(X'ABCDEE', 'abc')" {} 6 "INSERT INTO t2 VALUES(0, 0)" {} 7 "INSERT INTO t2 VALUES(45.5, 'abc')" {} 8 "INSERT INTO t2 VALUES(0.0, 'abc')" {} 9 "INSERT INTO t2 VALUES('brambles', 'abc')" {} 10 "INSERT INTO t2 VALUES(X'ABCDEF', 'abc')" {} } do_createtable_tests 4.3.3 -error { %s not unique } { 1 "UPDATE t1 SET x=0 WHERE y='two'" {"column x is"} 2 "UPDATE t1 SET x='brambles' WHERE y='three'" {"column x is"} 3 "UPDATE t1 SET x=45.5 WHERE y='zero'" {"column x is"} 4 "UPDATE t1 SET x=X'ABCDEF' WHERE y='one'" {"column x is"} 5 "UPDATE t1 SET x=0.0 WHERE y='three'" {"column x is"} 6 "UPDATE t2 SET x=0, y='zero' WHERE y='two'" {"columns x, y are"} 7 "UPDATE t2 SET x='brambles', y='two' WHERE y='three'" {"columns x, y are"} 8 "UPDATE t2 SET x=45.5, y='one' WHERE y='zero'" {"columns x, y are"} 9 "UPDATE t2 SET x=X'ABCDEF', y='three' WHERE y='one'" {"columns x, y are"} 10 "UPDATE t2 SET x=0.0, y='zero' WHERE y='three'" {"columns x, y are"} } # EVIDENCE-OF: R-52572-02078 For the purposes of determining the # uniqueness of primary key values, NULL values are considered distinct # from all other values, including other NULLs. # do_createtable_tests 4.4 { 1 "INSERT INTO t1 VALUES(NULL, 0)" {} 2 "INSERT INTO t1 VALUES(NULL, 0)" {} 3 "INSERT INTO t1 VALUES(NULL, 0)" {} 4 "INSERT INTO t2 VALUES(NULL, 'zero')" {} 5 "INSERT INTO t2 VALUES(NULL, 'one')" {} 6 "INSERT INTO t2 VALUES(NULL, 'two')" {} 7 "INSERT INTO t2 VALUES(NULL, 'three')" {} 8 "INSERT INTO t2 VALUES(0, NULL)" {} 9 "INSERT INTO t2 VALUES(45.5, NULL)" {} 10 "INSERT INTO t2 VALUES(0.0, NULL)" {} 11 "INSERT INTO t2 VALUES('brambles', NULL)" {} 12 "INSERT INTO t2 VALUES(X'ABCDEF', NULL)" {} 13 "INSERT INTO t2 VALUES(NULL, NULL)" {} 14 "INSERT INTO t2 VALUES(NULL, NULL)" {} } # EVIDENCE-OF: R-61866-38053 Unless the column is an INTEGER PRIMARY KEY # SQLite allows NULL values in a PRIMARY KEY column. # # If the column is an integer primary key, attempting to insert a NULL # into the column triggers the auto-increment behaviour. Attempting # to use UPDATE to set an ipk column to a NULL value is an error. # do_createtable_tests 4.5.1 { 1 "SELECT count(*) FROM t1 WHERE x IS NULL" 3 2 "SELECT count(*) FROM t2 WHERE x IS NULL" 6 3 "SELECT count(*) FROM t2 WHERE y IS NULL" 7 4 "SELECT count(*) FROM t2 WHERE x IS NULL AND y IS NULL" 2 } do_execsql_test 4.5.2 { CREATE TABLE t3(s, u INTEGER PRIMARY KEY, v); INSERT INTO t3 VALUES(1, NULL, 2); INSERT INTO t3 VALUES('x', NULL, 'y'); SELECT u FROM t3; } {1 2} do_catchsql_test 4.5.3 { INSERT INTO t3 VALUES(2, 5, 3); UPDATE t3 SET u = NULL WHERE s = 2; } {1 {datatype mismatch}} finish_test |
Changes to test/tester.tcl.
︙ | ︙ | |||
331 332 333 334 335 336 337 | puts "\nExpected: \[$expected\]\n Got: \[$result\]" fail_test $name } else { puts " Ok" } flush stdout } | | > > > > > > > > > > > | 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 | puts "\nExpected: \[$expected\]\n Got: \[$result\]" fail_test $name } else { puts " Ok" } flush stdout } proc fix_testname {varname} { upvar $varname testname if {[info exists ::testprefix] && [string is digit [string range $testname 0 0]] } { set testname "${::testprefix}-$testname" } } proc do_execsql_test {testname sql result} { fix_testname testname uplevel do_test $testname [list "execsql {$sql}"] [list $result] } proc do_catchsql_test {testname sql result} { fix_testname testname uplevel do_test $testname [list "catchsql {$sql}"] [list $result] } #------------------------------------------------------------------------- # Usage: do_select_tests PREFIX ?SWITCHES? TESTLIST # # Where switches are: |
︙ | ︙ |