| /sqlite-3.40.0/test/ |
| H A D | tkt1449.test | 95 ) as CRITICALDATA 101 d.ISSUEID as ISSUEID, 190 CREATE VIEW ITEMS as 192 …as TABLENAME, CLASSID, SEQNO, LASTMODONNODEID, PREVMODONNODEID, ISSUEID, OBJECTID, REVISIONNUM, CO… 194 …as TABLENAME, CLASSID, SEQNO, LASTMODONNODEID, PREVMODONNODEID, ISSUEID, OBJECTID, REVISIONNUM, CO… 196 …as TABLENAME, NULL as CLASSID, NULL as SEQNO, NULL as LASTMODONNODEID, NULL as PREVMODONNODEID, IS… 198 …as TABLENAME, CLASSID, SEQNO, LASTMODONNODEID, PREVMODONNODEID, ISSUEID, OBJECTID, REVISIONNUM, CO… 200 …as TABLENAME, CLASSID, SEQNO, LASTMODONNODEID, PREVMODONNODEID, ISSUEID, OBJECTID, REVISIONNUM, CO… 202 …as TABLENAME, CLASSID, SEQNO, LASTMODONNODEID, PREVMODONNODEID, ISSUEID, OBJECTID, REVISIONNUM, CO… 203 CREATE VIEW TASKINFO as [all …]
|
| H A D | select6.test | 90 FROM (SELECT count(*) as p , y as q FROM t1 GROUP BY y) AS a, 91 (SELECT max(x) as r, y as s FROM t1 GROUP BY y) as b 98 FROM (SELECT count(*) as p , y as q FROM t1 GROUP BY y) AS a, 99 (SELECT max(x) as r, y as s, min(x)+y FROM t1 GROUP BY y) as b 146 FROM (SELECT count(*) as p , b as q FROM t2 GROUP BY b) AS a, 147 (SELECT max(a) as r, b as s FROM t2 GROUP BY b) as b 154 FROM (SELECT count(*) as p , b as q FROM t2 GROUP BY q) AS a, 155 (SELECT max(a) as r, b as s FROM t2 GROUP BY s) as b 169 FROM (SELECT count(*) as p , b as q FROM t2 GROUP BY q) AS a, 170 (SELECT max(a) as r, b as s FROM t2 GROUP BY s) as b [all …]
|
| H A D | tkt2192.test | 41 create view direct_debits as 45 select strftime('%Y-%m', date) as date, (-1 * sum(value)) as value 50 create view energy as 51 select strftime('%Y-%m', date) as date, (-1 * sum(value)) as value 56 create view phone_internet as 57 select strftime('%Y-%m', date) as date, (-1 * sum(value)) as value 64 create view credit_cards as 65 select strftime('%Y-%m', date) as date, (-1 * sum(value)) as value 78 create view jan as 82 create view nov as [all …]
|
| H A D | tkt1443.test | 35 # to change filenames, so I'll just leave it as is. No harm done. 124 Items.Item as trove, UP.pattern as pattern 127 Permissions.labelId as labelId, 128 PerItems.item as pattern 131 left outer join Items as PerItems 137 ) as UP join LabelMap on ( UP.labelId = 0 or 156 Items.Item as trove, UP.pattern as pattern 159 Permissions.labelId as labelId, 160 PerItems.item as pattern 163 left outer join Items as PerItems [all …]
|
| H A D | avfs.test | 195 SELECT integrity_check as ic FROM pragma_integrity_check(); 200 SELECT count(*) as ic FROM ri; 202 SELECT integrity_check as ic FROM pragma_integrity_check(); 204 SELECT integrity_check as ic FROM pragma_integrity_check(); 205 SELECT count(*) as ic FROM ri; 220 SELECT integrity_check as ic FROM pragma_integrity_check(); 238 SELECT integrity_check as ic FROM pragma_integrity_check(); 252 SELECT integrity_check as ic FROM pragma_integrity_check(); 265 SELECT integrity_check as ic FROM pragma_integrity_check(); 329 set shod "sh_app1.adb" ; # Same as test 4.2, reusing ADB. [all …]
|
| H A D | date3.test | 58 # interpreted as either a julian day number or a unix timestamp, 62 # 5373484.499999, then it is interpreted as a julian day number 69 # as a unix timestamp. 114 # interpreted not as a Julian day number as it normally would be, but as 127 # time-value number to be interpreted as a julian-day number. 140 # 1970 will be interpreted as julian day numbers.
|
| H A D | fts2token.test | 42 # function fts2_tokenizer(). The procedure is as follows: 44 # 1: Verify that there is no such fts2 tokenizer as 'blah'. 47 # retrieved value as tokenizer 'blah'. 50 # same as that retrieved for 'simple'. 98 # simple input string via the built-in test function. This is as much 99 # to test the test function as the tokenizer implementations. 122 # Asian languages (Lao, Khmer etc.) require the same special treatment as
|
| H A D | dbstatus.test | 80 # as part of the [sqlite3] command. This prevents the script from 88 # Each test in the following block works as follows. Each test uses a 107 # same as the difference in total memory in steps 2 and 3. 109 # b) Step 4 reports the same amount of schema and total memory used as 112 # c) Step 5 reports the same amount of schema and total memory used as 208 # counted as "schema memory". 213 # for any reason is not counted as "schema memory". 243 # Each test in the following block works as follows. Each test uses a 263 # same as the difference in total memory in steps 2 and 3. 265 # b) Step 4 reports the same amount of schema and total memory used as [all …]
|
| H A D | fts3atoken.test | 44 # function fts3_tokenizer(). The procedure is as follows: 46 # 1: Verify that there is no such fts3 tokenizer as 'blah'. 49 # retrieved value as tokenizer 'blah'. 52 # same as that retrieved for 'simple'. 106 # returns the actual pointer value as a BLOB. 167 # simple input string via the built-in test function. This is as much 168 # to test the test function as the tokenizer implementations. 192 # Asian languages (Lao, Khmer etc.) require the same special treatment as
|
| H A D | misc4.test | 45 # was rolled back, statement $stmt was marked as expired. Executing it 153 from a, (select key,sum(period) from b group by key) as x 158 # This test case tests the same property as misc4-4.1, but it is 166 select * from ab, (select b from ab) as x where x.b = ab.a; 182 create view myview as select t4.a a from t4 inner join t5 on t4.a=t5.a; 183 create table problem as select * from myview; 191 create table t6 as select * from t4, t5;
|
| H A D | tkt-a7debbe0.test | 67 # Result should be 0, as column "xyz" from the sub-query has implicit 73 # Result should be 1, as literal 'xyz' has no collation sequence, so 91 SELECT v2.c1 BETWEEN v2.c0 AND v2.c1 as count FROM v2 95 # The result is 1, as the collation used is the implicit collation sequence 98 SELECT v2.c1 BETWEEN v2.c0 AND v2.c1 as count FROM v2;
|
| H A D | select1.test | 482 set v [catch {execsql2 {SELECT A.f1, t1 FROM test1 as A, test2 487 set v [catch {execsql2 {SELECT A.f1, f1 FROM test1 as A, test1 as B 492 set v [catch {execsql2 {SELECT A.f1, B.f1 FROM test1 as A, test1 as B 497 set v [catch {execsql2 {SELECT A.f1, f1 FROM test1 as A, test1 as A 502 set v [catch {execsql {SELECT A.f1, B.f1 FROM test1 as A, test1 as B 507 set v [catch {execsql2 {SELECT A.f1, B.f1 FROM test1 as A, test1 as B 689 set v [catch {execsql {SELECT f1 FROM test1 as 'hi', test2 as}} msg] 745 # disk as a vdbe integer, not a string. Hence the value of f1/(f1-11) 825 SELECT f1-22 AS x, f2-22 as y FROM test1 830 SELECT f1-22 AS x, f2-22 as y FROM test1 WHERE x>0 AND y<50 [all …]
|
| H A D | tkt3922.test | 27 # really test the same thing as the original, 29 # provided simply as a place holder for 70 # really test the same thing as the original, 71 # but provided simply as a place holder for
|
| H A D | wal8.test | 17 # the connection as a WAL database. Following this, the first connection 21 # This is an unusual case, as normally SQLite is able to glean the page 22 # size from the database file as soon as it is opened (even before the
|
| H A D | crash.test | 48 # crash-1.3: Ensure the database is in the same state as after crash-1.1. 51 # crash-1.5: Ensure the database is in the same state as after crash-1.1. 54 # crash-1.7: Ensure the database is in the same state as after crash-1.1. 59 # operates as expected. 130 # crash-2.4: Ensure the database is in the same state as after crash-2.1. 166 # The crash-3.* test cases are essentially the same test as test case 223 CREATE TABLE aux.abc2 AS SELECT 2*a as a, 2*b as b, 2*c as c FROM abc; 339 # functions as follows:
|
| H A D | backup.test | 42 # interpreted as "copy the whole file". 117 # 5) Check that the contents of the destination db is the same as that 122 # database, the only page size tested is 1024 bytes (the same as the 139 # * Target database page-size is the same as the source, OR 183 puts -nonewline " (as $db_dest.$file_dest)" 252 # byte is at offset 0x00010000 (64KB offset), as set by tester.tcl, 253 # not at the 1GB offset as it usually is. 255 # The test procedure is as follows (same procedure as used for 273 # * Target database page-size is the same as the source, OR 472 # are organized as follows: [all …]
|
| /sqlite-3.40.0/ext/fts2/ |
| H A D | README.tokenizers | 6 by specifying a "tokenizer" clause as part of the CREATE VIRTUAL TABLE 13 The built-in tokenizers (valid values to pass as <tokenizer name>) are 36 be encoded as an SQL blob value and passed to FTS2 through the SQL 39 as follows: 46 structure encoded as an SQL blob. If the second argument is present, 47 it is registered as tokenizer <tokenizer-name> and a copy of it 49 implementation currently registered as <tokenizer-name> is returned, 50 encoded as a blob. Or, if no such tokenizer exists, an SQL exception 67 an ICU locale identifier. For example "tr_TR" for Turkish as used 68 in Turkey, or "en_AU" for English as used in Australia. For example: [all …]
|
| /sqlite-3.40.0/ext/fts3/ |
| H A D | README.tokenizers | 6 by specifying a "tokenize" clause as part of the CREATE VIRTUAL TABLE 13 The built-in tokenizers (valid values to pass as <tokenizer name>) are 36 be encoded as an SQL blob value and passed to FTS3 through the SQL 39 as follows: 46 structure encoded as an SQL blob. If the second argument is present, 47 it is registered as tokenizer <tokenizer-name> and a copy of it 49 implementation currently registered as <tokenizer-name> is returned, 50 encoded as a blob. Or, if no such tokenizer exists, an SQL exception 69 an ICU locale identifier. For example "tr_TR" for Turkish as used 70 in Turkey, or "en_AU" for English as used in Australia. For example: [all …]
|
| H A D | README.syntax | 20 as part of the query text (see sections 2 and 3 below). 54 As well as grouping tokens together by phrase, the binary NEAR operator 58 case is treated as an ordinary token. For example, the following query: 73 in as sequence. For example this query: 81 also be used as arguments to the NEAR operator. 106 matches all rows that contain the term "SQLite", as well as those that 161 handled as a regular token. 165 as its left-hand operator matches, but that the query specified as the 173 upper case. Otherwise it will be treated as a regular token. 201 in parenthesis as operands to the NOT, AND and OR operators. However both [all …]
|
| /sqlite-3.40.0/ext/rtree/ |
| H A D | rtreedoc3.test | 30 # as a list. Each cell is itself a list of the following form: 55 # Interpret the first two bytes of the blob passed as the only parameter 56 # as a 16-bit big-endian integer and return the value. If this blob is 80 # are as expected. 87 # The priority queue is stored as a Tcl list. The order of elements in 88 # the list is unimportant - it is just used as a set here. Each element 162 array set G $L ;# "Got" - as in stuff passed to xQuery 169 # xQueryCallback being called on a child - as is happening here. 171 array set P $parent ;# "Parent" - as in parent of expected cell 185 # Check level is as expected [all …]
|
| /sqlite-3.40.0/doc/ |
| H A D | trusted-schema.md | 32 in elements of the schema such as CHECK constraint, DEFAULT values, 38 Application-defined functions and virtual tables go in as Normal unless 62 with side-effects are marked as Direct-Only. 65 go in as "Normal" by default. For optimal security, we want those risky 68 functions and vtabs go in as Normal, but the application can switch them 95 <li> _SQLITE\_INNOCUOUS_ → tags the new functions as Innocuous 96 <li> _SQLITE\_DIRECTONLY_ → tags the new functions as Direct-Only 101 <li> _SQLITE\_VTAB\_INNOCUOUS_ → tags the vtab as Innocuous 102 <li> _SQLITE\_VTAB\_DIRECTONLY_ → tags the vtab as Direct-Only 140 Doing the same is not possible for virtual tables, as a virtual table
|
| /sqlite-3.40.0/ext/wasm/jaccwabyt/ |
| H A D | jaccwabyt.md | 74 Motivating use case: this API was initially developed as an 251 - `sizeof`: as reported by C's `sizeof()`. 266 Nested structs are as-yet unsupported by this tool. 338 pointer members) as follows: 599 [StructBinder][]_ as this StructType. 618 then it is treated as follows: 631 it as an array or converting it from a function to array as 718 for least as long as this struct instance. This is used, for example, 760 Works exactly as documented for [StructType][]. 763 Works exactly as documented for [StructType][]. [all …]
|
| /sqlite-3.40.0/ext/icu/ |
| H A D | README.txt | 48 as the second argument is the same as invoking the 1 argument version 64 to be in the same equivalence class as the dotted 'I' character 84 as collation sequence identifiers in SQL statements: 95 provided by the ICU library. The syntax of the operator is as described 116 and use it as a dynamically loadable SQLite extension. To do this 124 loaded into sqlite in the same way as any other dynamically loadable 144 SQLITE_MAX_LIKE_PATTERN_LENGTH macro as the maximum length of a
|
| /sqlite-3.40.0/tool/ |
| H A D | sqltclsh.c.in | 4 ** The startup script is located as follows: 6 ** (1) Open the executable as an appended SQLite database and try to 10 ** as an SQLite database and read the startup script out of that 16 ** If none of the above steps work, then the program runs as an interactive
|
| /sqlite-3.40.0/src/ |
| H A D | sqlite.h.in | 267 ** interfaces (such as 1722 ** is always at least as big as the requested size but may be larger. 1743 ** holds the [SQLITE_MUTEX_STATIC_MEM] mutex as long as the 1798 ** environment as long as no two threads attempt to use the same 2467 ** as an undeclared column named ROWID, OID, or _ROWID_ as long as those 2493 ** return the [rowid] of the inserted row as long as the trigger is 2821 ** is as follows: 3444 ** to use SQLite at the same time, as long as each thread is using 5734 ** Then as long as the pattern string remains the same, 8099 ** a keyword as an identifier as long as such use does not result in a [all …]
|