| /sqlite-3.40.0/test/ |
| H A D | whereD.test | 247 c0=1 or c1=1 or c2=1 or c3=1 or 248 c4=1 or c5=1 or c6=1 or c7=1 or 249 c8=1 or c9=1 or c10=1 or c11=1 or 250 c12=1 or c13=1 or c14=1 or c15=1 or 257 c0=1 or c1=1 or c2=1 or c3=1 or 258 c4=1 or c5=1 or c6=1 or c7=1 or 259 c8=1 or c9=1 or c10=1 or c11=1 or 260 c12=1 or c13=1 or c14=1 or c15=1 or 267 c0=1 or c1=1 or c2=1 or c3=1 or 268 c4=1 or c5=1 or c6=1 or c7=1 or [all …]
|
| H A D | randexpr1.test | 182 …or (11) not in (b,t1.a,t1.a) then b else b end-11),f) then 13 else 11 end-t1.e*a) FROM t1 WHERE f … 185 …or (11) not in (b,t1.a,t1.a) then b else b end-11),f) then 13 else 11 end-t1.e*a) FROM t1 WHERE NO… 188 …or (11) not in (b,t1.a,t1.a) then b else b end-11),f) then 13 else 11 end-t1.e*a) FROM t1 WHERE f … 383 …or t1.b>=t1.c and t1.a<>e) then coalesce((select max(13) from t1 where 11>11), -(e)) | t1.a when (… 386 …or t1.b>=t1.c and t1.a<>e) then coalesce((select max(13) from t1 where 11>11), -(e)) | t1.a when (… 389 …or t1.b>=t1.c and t1.a<>e) then coalesce((select max(13) from t1 where 11>11), -(e)) & t1.a when (… 671 …or (t1.e=(a)) and -11 in (select t1.f from t1 union select c from t1)),a)*coalesce((select max(f)… 674 …or (t1.e=(a)) and -11 in (select t1.f from t1 union select c from t1)),a)*coalesce((select max(f)… 923 …1.c,11) or 17 between t1.f and b or not f in (select 19 from t1 union select t1.e from t1) and b<>… 2933 …c+t1.c then 11 else 11 end or (c in (select t1.c from t1 union select c from t1) or 11<=t1.a) or d… [all …]
|
| H A D | sqllimits1.test | 254 # string or BLOB or table row, in bytes. 264 } {1 {string or blob too big}} 267 } {1 {string or blob too big}} 275 } {1 {string or blob too big}} 283 } {1 {string or blob too big}} 293 } {1 {string or blob too big}} 304 } {1 {string or blob too big}} 310 } {1 {string or blob too big}} 315 } {1 {string or blob too big}} 583 # columns in a table definition or in the result set of a SELECT or the [all …]
|
| H A D | diskfull.test | 43 } {1 {database or disk is full}} 51 } {1 {database or disk is full}} 67 set r {1 {database or disk is full}} 71 set r {1 {database or disk is full}} 74 } {1 {database or disk is full}}
|
| H A D | zeroblob.test | 95 # NULLs can follow the zeroblob() or be intermixed with zeroblobs and 199 } {1 {string or blob too big}} 202 } {1 {string or blob too big}} 281 } {1 {string or blob too big}} 284 # Test the zeroblob() function on its own with negative or oversized 292 } {1 {string or blob too big}} 295 } {1 {string or blob too big}}
|
| H A D | e_changes.test | 29 # of database rows that were changed or inserted or deleted by the most 30 # recently completed INSERT, DELETE, or UPDATE statement, exclusive of 88 # whether or not they are executed inside an explicit transaction. 133 # UPDATE or DELETE statement are considered - auxiliary changes caused 134 # by triggers, foreign key actions or REPLACE constraint resolution are 234 # immediately after an INSERT, UPDATE or DELETE statement run on a view 393 # function (or similar) is used by the first INSERT, UPDATE or DELETE 397 # EVIDENCE-OF: R-53215-27584 If it is used by the second or subsequent 399 # the number of rows modified by the previous INSERT, UPDATE or DELETE
|
| H A D | e_createtable.test | 876 # CURRENT_TIME, CURRENT_DATE or CURRENT_TIMESTAMP. 896 # column or table references, bound parameters, or string literals 1105 } {1 {string or blob too big}} 1276 # or the table is a WITHOUT ROWID table or a STRICT table or the column 1677 # identifiers: "ROWID", "OID", or "_ROWID_". 1730 # the rowid, or 0 otherwise. 1769 # "BIGINT" or "SHORT INTEGER" or "UNSIGNED INTEGER" causes the primary 1831 # using one of the built-in aliases ("rowid", "oid" or "_rowid_") or by 1884 # values, strings, BLOBs, or NULLs. 1898 # integer primary key or rowid column to a NULL or blob value, or to a [all …]
|
| H A D | schema2.test | 20 # When any of the following types of SQL statements or actions are 31 # Setting or changing the authorization function......schema2-8.* 36 # Test cases schema2-11.* test that it is impossible to delete or 37 # change a collation sequence or user-function while SQL statements 38 # are executing. Adding new collations or functions is allowed. 297 # Attempting to delete or replace a user-function or collation sequence
|
| H A D | e_fkey.test | 621 # constraint, or have a UNIQUE index created on it. 626 # to a UNIQUE constraint or have a UNIQUE index. 1389 # classified as either immediate or deferred. 1770 # it's parent row is updated or deleted. 1809 # or updating a parent table row when there exists one or more child keys 1815 # or more child keys mapped to it. 1942 # keys is deleted or modified. 2317 # 3. Update or delete the row in the parent table, 2365 # is 'distinct' from the old or not. 2459 # does not exist, or to parent key columns that do not exist or are not [all …]
|
| H A D | schema.test | 19 # When any of the following types of SQL statements or actions are 30 # Setting or changing the authorization function......schema-8.* 36 # Test cases schema-11.* test that it is impossible to delete or 37 # change a collation sequence or user-function while SQL statements 38 # are executing. Adding new collations or functions is allowed. 308 # Attempting to delete or replace a user-function or collation sequence 352 # there is a rollback (explicit or otherwise).
|
| H A D | e_walckpt.test | 158 # EVIDENCE-OF: R-00653-06026 If parameter zDb is NULL or points to a 190 # EVIDENCE-OF: R-38207-48996 If zDb is not NULL (or a zero length 424 # without waiting for any database readers or writers to finish, then 504 # writer lock retried until either the busy-handler returns 0 or the 550 # was "restart" or "truncate", then the busy-handler will have 574 # writer lock is obtained or while waiting for database readers, the 647 # EVIDENCE-OF: R-41299-52117 If no error (SQLITE_BUSY or otherwise) is 728 # the total number of frames in the log file or to -1 if the checkpoint 729 # could not run because of an error or because the database is not in 734 # any that were already checkpointed before the function was called) or [all …]
|
| /sqlite-3.40.0/doc/ |
| H A D | trusted-schema.md | 9 or views, or add new CHECK constraints or generated columns or indexes 10 with expressions in the index list or in the WHERE clause. If the 11 added features invoke SQL functions or virtual tables with side effects, 33 generated columns, index expressions, or in the WHERE clause of a 44 An innocuous function or virtual table is one that can only read content 72 to TEMP. A TEMP VIEW or a TEMP TRIGGER can use any valid SQL function 73 or virtual table. The idea is that TEMP views and triggers must be 114 <li> _enc_ → 'utf8', 'utf16le', or 'utf16be' 131 SQL functions that are never allowed to be used in the schema or in 132 trigger or views: [all …]
|
| H A D | json-enhancements.md | 27 such as TEXT, INTEGER, REAL, or NULL. If a JSON object or array 28 is selected, that object or array is rendered as text. If a JSON 32 * The json_extract() interface returns JSON when a JSON object or 33 array is selected, or a primitive SQL datatype when a JSON value 39 In MySQL and PG, the ->> operator always returns TEXT (or NULL) and never 41 of those systems. In MySQL and PG, the result type a function or operator 80 * The -> operator always returns either JSON or NULL. 82 * The ->> operator never returns JSON. It always returns TEXT or NULL, or in the 83 case of SQLite, INTEGER or REAL. 104 a JSON object label or an integer array index for the right-hand side [all …]
|
| H A D | vfs-shm.txt | 59 A particular lock manager implementation may coalesce one or more of 63 only one reader or one writer or one checkpointer could be active at a 66 coexist with a reader, but no reader or writers could coexist with a 73 (3) None of WRITE, PENDING, CHECKPOINT, or RECOVER can coexist. 80 kind of SHM lock or an EXCLUSIVE lock on the original database. 88 will the size of the wal-index grow without holding a WRITE or 92 WRITE, CHECKPOINT, or RECOVER on the wal-index or an EXCLUSIVE on 95 (9) A CHECKPOINT or RECOVER must be held on the wal-index, or an 102 CHECKPOINT, or RECOVER to the lock manager. The SQLite core will never 103 request a READ_FULL or PENDING lock though the lock manager may deliver [all …]
|
| H A D | wal-lock.md | 17 Threads or processes that access a single database at a time never deadlock as 30 fails to obtain the WRITER lock and either invokes the busy-handler callback or 51 * the transaction is an implicit one consisting of a single DML or DDL 52 statement, or 53 * the transaction is opened using BEGIN IMMEDIATE or BEGIN EXCLUSIVE, or 54 * the first SQL statement executed following the BEGIN command is a DML or
|
| /sqlite-3.40.0/src/ |
| H A D | in-operator.md | 12 The "x" is referred to as the LHS (left-hand side). The list or subquery 17 The LHS can be a scalar (a single quantity) or a vector (a list of 18 two or or more values) or a subquery that returns one or more columns. 19 We use the term "vector" to mean an actually list of values or a 20 subquery that returns two or more columns. An isolated value or 24 that returns two or more columns, or a list of scalars. It is not 32 NULL values can occur in either or both of the LHS and RHS. 38 a total-NULL if it contains one or more rows that contain only NULL values. 42 The result of an IN operator is one of TRUE, FALSE, or NULL. A NULL result 46 the system only needs a binary result: TRUE or NOT-TRUE. One can also [all …]
|
| H A D | sqlite.h.in | 704 ** energetic or rigorous or forceful the sync operations are and 3998 ** or in an ORDER BY or GROUP BY clause.</dd>)^ 4488 ** or sqlite3_bind_text16() or sqlite3_bind_text64() then 4602 ** ^(SQL parameters of the form "?NNN" or ":AAA" or "@AAA" or "$AAA" 4603 ** have a name which is the string "?NNN" or ":AAA" or "@AAA" or "$AAA" 4605 ** In other words, the initial ":" or "$" or "@" or "?" 4735 ** If two or more threads call one or more 4786 ** or [sqlite3_prepare16_v3()] or one of the legacy 5104 ** described above, or until [sqlite3_step()] or [sqlite3_reset()] or 5155 ** one or more calls to [sqlite3_reset()], or after any call [all …]
|
| /sqlite-3.40.0/ext/fts3/ |
| H A D | README.syntax | 12 (in this case "t1"), or by the name of one of the columns of the fts3 38 matches rows (or columns, if <col> is the name of a column name) that 47 matches the first of the following two documents, but not the second or 65 they be seperated by only 10 tokens or less. The user may also specify 83 Similar to the NEAR operator, one or more tokens or phrases may be 85 or phrases must appear in the document. For example, the query: 94 not those that contain both 'sqlite' and 'fantastic' or 'impressive': 119 one term or phrase that is not preceded by the '-' prefix. 121 Regardless of whether or not a table name or column name is used on the 134 phrase or a term preceded by a '-' operator. A '*' character may be [all …]
|
| /sqlite-3.40.0/tool/ |
| H A D | genfkey.README | 25 primary key columns or subject to a UNIQUE constraint. There is no such 29 "MATCH NONE", even if the declaration specified "MATCH PARTIAL" or 40 Attempting to insert or update a row in the child table so that the 44 The effect of attempting to delete or update a row in the parent table 46 table depends on the "ON DELETE" or "ON UPDATE" actions specified as 53 that the constraint becomes untrue for one or more rows in 85 does not support recursive CASCADE or SET NULL foreign key 86 relationships. If the parent and the child tables of a CASCADE or 90 table A with a CASCADE or SET NULL foreign key constraint). 103 a foreign key that refers to a parent table that does not exist, or [all …]
|
| /sqlite-3.40.0/ext/userauth/ |
| H A D | user-auth.txt | 17 const char *aPW, /* Password or credentials */ 24 const char *aPW, /* Password or credentials */ 32 const void *aPW, /* Modified password or credentials */ 48 or write from the database will fail with an SQLITE_AUTH error until 114 login credentials or admin privilege. Any user can change their own 116 credentials or admin privilege setting. No user may change their own 120 which is the username of the currently logged in user, or NULL for a 153 To compute an appropriate sqlite_user.pw value from a new or modified 161 Extension or similar technology. Or, the application can use the
|
| /sqlite-3.40.0/autoconf/ |
| H A D | INSTALL | 7 Copying and distribution of this file, with or without modification, 27 It may also create one or more `.h' files containing system-dependent 41 diffs or instructions to the address given in the `README' so they can 44 may remove or edit it. 46 The file `configure.ac' (or `configure.in') is used to create 48 you want to change it or regenerate `configure' using a newer version 128 executables that work on multiple system types--known as "fat" or 168 having to reconfigure or recompile. 197 option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. 202 is something like `gnu-as' or `x' (for the X Window System). The [all …]
|
| H A D | README.txt | 52 Using Microsoft Visual C++ 2005 (or later) is recommended. Several Windows 61 Using Microsoft Visual C++ 2012 (or later) is required. When using the 72 Using Microsoft Visual C++ 2013 (or later) is required. When using the 83 Using Microsoft Visual C++ 2015 (or later) is required. When using the 96 Using Microsoft Visual C++ 2015 (or later) is required. When using the
|
| /sqlite-3.40.0/ext/wasm/jaccwabyt/ |
| H A D | jaccwabyt.md | 17 and makes no attempt whatsoever to accommodate "older" or 19 mid-2018 or later, with late 2021 releases required for some optional 81 to be a useful (or at least interesting) tool for mixed JS/C 180 heap: WebAssembly.Memory instance or a function which returns 181 a Uint8Array or Int8Array view of the WASM memory, 264 prefix and/or suffix to their names. 350 `p` or `P` is used). 371 and/or its sub-objects, or may even replace sub-objects, in order to 767 of this struct type or a pointer which resolves to one. 770 or does not resolve to, an instance of this struct type, [all …]
|
| /sqlite-3.40.0/ext/rtree/ |
| H A D | README | 30 less than or equal to the second. R-tree tables may be 47 Dropping or modifying the contents of these tables directly will 58 The usual INSERT, UPDATE or DELETE syntax is used to manipulate data 71 * Attempting to insert or modify a record such that the value 76 the required type (64-bit integer or 32-bit real) as if they
|
| /sqlite-3.40.0/ |
| H A D | README.md | 15 If you are reading this on GitHub or some other Git repository or service, 30 If you do not want to use Fossil, you can download tarballs or ZIP 35 [ZIP-archive](https://www.sqlite.org/src/zip/sqlite.zip), or 40 [ZIP-archive](https://www.sqlite.org/src/zip/sqlite.zip?r=release), or 43 * For other check-ins, substitute an appropriate branch name or 44 tag or hash prefix in place of "release" in the URLs of the previous 47 then click on the "Tarball" or "ZIP Archive" links on the information 51 first install Fossil version 2.0 or later. 54 a stand-alone program. To install, simply download or build the single 149 for building generated source code files or for testing or for generating [all …]
|