Home
last modified time | relevance | path

Searched refs:generated (Results 1 – 25 of 91) sorted by relevance

1234

/sqlite-3.40.0/test/
H A Dfts3expr2.test28 # The tests in this file are pseudo-randomly generated. They test
34 # 1. A random expression tree is generated using proc [random_expr_tree].
38 # expression text generated in step (2), returning a parsed expression
40 # 4. Test that the tree returned in step (3) matches that generated in
47 # "a OR b AND (c OR d)" or "a OR (b AND (c OR d))" is generated.
50 # "a OR b AND c" or "a OR b c" is generated.
H A Dgencol1.test12 # Test cases for generated columns.
219 # constraints on tables that have generated columns.
309 } {1 {generated column loop on "c2"}}
311 # 2019-11-21 Problems in the new generated column logic
397 # With generated columns, the sqlite3ExprGetColumnOfTable() routine might
399 # make sure that the last instruction generated is an OP_column prior to
412 # generated column appears in the USING clause of a join.
451 # The schema is malformed in that it has a subquery on a generated
457 # is to change the generated column expression to NULL before adding it
489 # false, make sure any generated columns evaluate to NULL.
[all …]
H A Dfuzz.test16 # The tests in this file are really about testing fuzzily generated
17 # SQL parse-trees. The majority of the fuzzily generated SQL is
305 # Test some fuzzily generated expressions.
319 # Test some fuzzily generated SELECT statements.
325 # some more generated SELECT statements.
H A Derrmsg.test25 # errmsg-2.* Errors generated by the VDBE (constraint failures etc.)
70 # Test error messages generated directly by VDBE code (e.g. constraint
H A Ddate2.test46 } {1 {non-deterministic use of date() in a generated column}}
174 } {1 {non-deterministic use of julianday() in a generated column}}
H A Dfts3rnd.test16 # query. This is done using pseudo-randomly generated data and queries.
27 # generated as in step 1. The docid is a pseudo-randomly selected
31 # set to contain a new document generated in the same way as the
H A Dalterdropcol.test139 # Test that generated columns can be dropped. And that other columns from
140 # tables that contain generated columns can be dropped.
H A Din2.test55 # This bug only applied to b-trees generated to evaluate IN (..)
H A DvtabK.test81 } {1 {error in table t2 after add column: subqueries prohibited in generated columns}}
H A Dfuzz_malloc.test77 # generated expressions.
H A Dsort3.test14 # configured to use mmap(), but the temporary files generated by the
H A DwhereF.test285 # And TERM_VNULL entries are only generated when compiling with
292 # a GLOB operator do not appear anywhere in the generated code. This
H A Djson103.test59 # Invalid JSON generated by json_group_array()
/sqlite-3.40.0/
H A DREADME.md122 a lot of generated code and Tcl is used to do much of that code generation.
149 for building generated source code files or for testing or for generating
154 Several of the C-language source files used by SQLite are generated from
156 section will summarize those automatically-generated files. To create all
157 of the automatically-generated files, simply run "make target_source".
160 manually-edited files and automatically-generated files.
163 generated from src/sqlite.h.in, ./manifest.uuid, and ./VERSION. The
183 file is generated by scanning the src/vdbe.c source file. The
192 generated by a C-language program at tool mkkeywordhash.c.
195 and implement the PRAGMA statements. The header is generated by a
[all …]
H A Dltmain.sh4088 generated=
7081 generated="$generated $gentop"
7332 generated="$generated $gentop"
7447 generated="$generated $gentop"
7902 generated="$generated $gentop"
7916 generated="$generated $gentop"
7937 generated="$generated $gentop"
8023 test -n "$generated" && \
8024 func_show_eval "${RM}r$generated"
/sqlite-3.40.0/tool/
H A Dgenfkey.README87 SET NULL foreign key are the same table, the generated triggers will
110 no error messages are printed. No "CREATE TRIGGER" statements are generated
114 All triggers generated by this command have names that match the pattern
124 generated.
126 If the --exec option was passed, then all generated SQL is immediately
127 executed on the database. Otherwise, the generated SQL strings are output
H A Dmkctimec.tcl13 ** This file is automatically generated by the script in the canonical
17 ** which specify categories of generated conditionals in this file.
H A Domittest.tcl21 Almost any SQLite makefile (except those generated by configure - see below)
34 Makefiles generated by the sqlite configure program cannot be used as
H A Dmkccode.tcl50 ** This file was generated by \"$argv0 $infile\".
H A Dmkshellc.tcl16 ** This file is automatically generated by the script in the canonical
/sqlite-3.40.0/ext/wasm/jaccwabyt/
H A Djaccwabyt.md136 individual instances of generated struct types.
157 3. [Feed (2) to the function generated by (1)](#step-3) to create JS
301 generated code includes `p` as an alias for `i`, presumably to mean
442 functions and types are generated. The binder factory's signature is:
505 `console.log` is used but by default no debug output is generated.
554 resolves to a struct of _any type_ generated via the same Struct
580 only called by the [StructBinder][]-generated
776 constructor was generated.
780 was generated.
896 Struct definitions are _ideally_ generated from WASM-compiled C, as
[all …]
/sqlite-3.40.0/ext/fts2/
H A Dmkfts2amal.tcl35 ** This amalgamation was generated on $today.
/sqlite-3.40.0/doc/
H A Dtrusted-schema.md9 or views, or add new CHECK constraints or generated columns or indexes
33 generated columns, index expressions, or in the WHERE clause of a
/sqlite-3.40.0/ext/fts5/test/
H A Dfts5bigpl.test52 # The generated database is roughly 635MiB.
/sqlite-3.40.0/ext/wasm/api/
H A DREADME.md100 files, and `sqlite3.js`, which is the Emscripten-generated amalgamated
111 into the build-generated `sqlite3.js` along with `sqlite3-api.js`.

1234