Home
last modified time | relevance | path

Searched refs:schema (Results 1 – 25 of 176) sorted by relevance

12345678

/sqlite-3.40.0/test/
H A Dschema.test33 # Test cases schema-9.* and schema-10.* test some specific bugs
44 do_test schema-1.1 {
51 do_test schema-1.2 {
54 do_test schema-1.3 {
61 do_test schema-1.4 {
116 do_test schema-4.1 {
126 do_test schema-4.2 {
129 do_test schema-4.3 {
136 do_test schema-4.4 {
170 do_test schema-6.1 {
[all …]
H A Dvtab2.test26 CREATE VIRTUAL TABLE schema USING schema;
27 SELECT * FROM schema;
30 main schema 0 database {} 0 {} 0 \
31 main schema 1 tablename {} 0 {} 0 \
32 main schema 2 cid {} 0 {} 0 \
33 main schema 3 name {} 0 {} 0 \
34 main schema 4 type {} 0 {} 0 \
35 main schema 5 not_null {} 0 {} 0 \
51 } {schema}
103 FROM schema a LEFT JOIN schema b ON a.dflt_value=b.dflt_value
[all …]
H A Ddbstatus.test89 # different database schema.
98 # and the schema memory again.
115 foreach {tn schema} {
181 execsql $schema
193 execsql $schema
208 # counted as "schema memory".
213 # for any reason is not counted as "schema memory".
244 # different database schema.
247 # schema.
271 foreach {tn schema statements} {
[all …]
H A DcorruptM.test55 } {1 {malformed database schema (t1)}}
65 } {1 {malformed database schema (t1)}}
74 } {1 {malformed database schema (t1)}}
83 } {1 {malformed database schema (t9)}}
105 } {1 {malformed database schema (t1)}}
117 } {1 {malformed database schema (i1)}}
128 } {1 {malformed database schema (i1)}}
139 } {1 {malformed database schema (i1)}}
151 } {1 {malformed database schema (v2)}}
162 } {1 {malformed database schema (v3)}}
[all …]
H A Derrmsg.test29 proc error_messages_worker {prepare sql schema} {
33 execsql $schema
42 proc error_messages_v2 {sql {schema {}}} {
43 error_messages_worker sqlite3_prepare_v2 $sql $schema
46 proc error_messages {sql {schema {}}} {
47 error_messages_worker sqlite3_prepare $sql $schema
93 # Test SQLITE_SCHEMA errors. And, for _v2(), test that if the schema
105 SQLITE_SCHEMA {database schema has changed}
H A DsharedA.test104 # set, it resets the schema. Both of the above steps must be done
106 # try to use the new schema with the old data.
145 # Create a prepared statement on db2 that will attempt a schema change
147 # the schema of test.db and that creates a rollback journal on test2.db
159 # schema change when db1 accesses the journal file of test2.db.
162 # be rolled back but before the schema has been reset. If the
165 # schema, which is wrong.
186 # schema change.
191 } {SQLITE_SCHEMA {database schema has changed}}
H A De_resolve.test20 # An example database schema for testing name resolution:
22 set schema {
50 db eval $::schema
68 # EVIDENCE-OF: R-00634-08585 If a schema name is specified as part of an
70 # schema-name of an attached database.
82 # EVIDENCE-OF: R-17446-42210 Like other SQL identifiers, schema names
91 # EVIDENCE-OF: R-14755-58619 If a schema name is specified, then only
92 # that one schema is searched for the named object.
H A Dshared8.test14 # does not cause the schema to be reloaded and (b) does not cause any
37 # 1.1: Using "PRAGMA writable_schema", destroy the database schema on
38 # disk. The schema is still in memory, so it is possible to keep
41 # 1.3-4: Open connection db2. Check that it can see the db schema. Then
43 # db1 did not reset the in-memory schema.
47 # 1.8: Close all database connections (deleting the in-memory schema).
H A Dcsv01.test88 schema='CREATE TABLE x(x0,x1,x2,x3,x4)',
108 schema='CREATE TABLE t2(a INT, b TEXT, c REAL, d BLOB)'
138 schema=
163 schema=
167 } {1 {bad schema: 'CREATE TABLE t3(a,b,c,d,PRIMARY KEY(a,b)) WITHOUT ROWID' - not an error}}
179 schema=
194 schema=
198 } {1 {bad schema: 'CREATE TABLE t3(a,b,c,d) WITHOUT ROWID' - PRIMARY KEY missing on table t3}}
H A Dtemptrigger.test31 # schema. If process 2 reloads the shared-cache schema from disk, then
44 # the shared-cache schema to be reloaded.
82 # Cause the shared-cache schema to be reloaded.
105 # It does not do anything special to cause the schema to be reloaded.
144 # the schema of an attached database (because some other connection had
145 # changed the schema cookie) it was not re-creating temp triggers attached
153 # temptrigger-3.3: Update the schema of 'test2.db' using an external
155 # schema. Check that the temp trigger is still fired
H A Ddbpage.test63 SELECT pgno, schema, substr(data,1,6)
65 WHERE sqlite_dbpage.schema=x3.y AND sqlite_dbpage.pgno=x3.z
89 SELECT data FROM sqlite_dbpage WHERE schema='aux1' AND pgno=2;
92 UPDATE sqlite_dbpage SET data=zeroblob(4096) WHERE pgno=2 AND schema='aux1';
99 WHERE pgno=2 AND schema='aux1';
H A Dtkt2854.test74 } {1 {database schema is locked: main}}
77 } {1 {database schema is locked: main}}
79 # This fails because the schema of main cannot be verified.
81 } {1 {database schema is locked: main}}
85 # at the b-tree level, not the schema level.
H A Dschema3.test25 # This block tests that if one client modifies the database schema, a
26 # second client updates its internal cache of the database schema before
30 # schema.
32 # Types of schema modifications:
42 # Have connections [db1] and [db2] load the current database schema.
H A Dpragma.test34 # pragma-6.*: Test schema-query pragmas.
42 # reset when the schema is reloaded.
86 # EVIDENCE-OF: R-13861-56665 PRAGMA schema.cache_size; PRAGMA
87 # schema.cache_size = pages; PRAGMA schema.cache_size = -kibibytes;
654 # Test schema-query pragmas
780 # sure the schema of the main table can still be queried using
843 # Make sure a pragma knows to read the schema if it needs to
919 # to verify that the value being read is in fact the schema version).
980 # forces the second connection to reload the schema.
1007 # accidentally manipulating the schema-version instead).
[all …]
H A Dshared.test74 # shared-4.*: Check that the schema is locked and unlocked correctly.
75 # shared-5.*: Test that creating/dropping schema items works when databases
135 # transaction modifies the schema, it should not be possible for
146 # is because of the schema-modified lock established by connection 1
154 } {1 {database schema is locked: main}}
275 # Tests shared-4.* test that the schema locking rules are applied
281 # schema.
283 # write-lock on the schema.
411 } {1 {(6) database schema is locked: test}}
417 } {1 {(6) database schema is locked: test}}
[all …]
H A Dtkt-f7b4edec.test43 # In the second database connection cause the schema to be reparsed
44 # without changing the schema cookie.
58 # schema reparse. Verify that the update-hook gives the correct
H A Dautovacuum2.test35 proc autovac_page_callback {schema filesize freesize pagesize} {
37 lappend autovac_callback_data $schema $filesize $freesize $pagesize
74 proc autovac_page_callback_off {schema filesize freesize pagesize} {
H A Dnotify3.test56 } {1 {database schema is locked: aux}}
66 } {(262) database schema is locked: aux}
90 # ATTACH fails due to locks on the schema table held by other shared-cache
97 # Executing such SQL causes SQLite to load the database schema into memory
H A Dshell1.test570 # .schema ?TABLE? Show the CREATE statements
574 catchcmd "test.db" ".schema"
577 catchcmd "test.db" ".schema FOO"
581 catchcmd "test.db" ".schema FOO BAD"
590 catchcmd "test.db" ".schema"
1149 catchcmd "test.db" ".schema _"
1153 catchcmd "test.db" ".schema \\\\_"
1156 catchcmd "test.db" ".schema __"
1160 catchcmd "test.db" ".schema \\\\_\\\\_"
1163 catchcmd "test.db" ".schema ___"
[all …]
/sqlite-3.40.0/ext/fts5/test/
H A Dfts5connect.test24 # The tests in this file test the outcome of a schema-reset happening
29 # table causing SQLite to load the db schema into memory.
31 # 2. Connection [db2] opens the db and modifies the db schema.
34 # schema has been modified is detected inside the fts5 xConnect()
38 # that the schema has changed and successfully prepare the
39 # statement against the new schema.
43 # 1.*: Trigger the xConnect()/schema-reset using statements executed
/sqlite-3.40.0/ext/rbu/
H A Drbu1.test149 foreach {tn schema} {
225 execsql $schema
322 execsql $schema
344 foreach {tn schema} {
385 execsql $schema
421 foreach {tn schema} {
434 execsql $schema
472 foreach {tn schema} {
505 execsql $schema
550 foreach {tn schema error} {
[all …]
H A DrbuC.test46 foreach {tn schema} {
62 execsql $schema
94 foreach {tn schema} {
107 execsql $schema
/sqlite-3.40.0/ext/session/
H A Dsession1.test375 # Create an identical schema in both databases.
376 set schema {
379 execsql $schema db
380 execsql $schema db2
406 set schema {
411 execsql $schema db
412 execsql $schema db2
435 set schema {
440 execsql $schema db
441 execsql $schema db2
H A Dsession3.test13 # database schema modifications and mismatches.
27 # correctly when confronted with a schema mismatch when applying a
88 # correctly when the schema of an attached table is modified during the
98 # session3-2.4.*: Table is dropped and recreated with an identical schema.
/sqlite-3.40.0/doc/
H A Dtrusted-schema.md5 An attacker might modify the schema of an SQLite database by adding
32 in elements of the schema such as CHECK constraint, DEFAULT values,
60 the database schema and possibly trick a high-privilege application
76 corrupts the schema of a persistent database file. Hence TEMP views and
131 SQL functions that are never allowed to be used in the schema or in

12345678