| /sqlite-3.40.0/test/ |
| H A D | fts3ad.test | 31 SELECT rowid FROM t1 WHERE content MATCH 'run jump'; 36 SELECT snippet(t1) FROM t1 WHERE t1 MATCH 'run jump'; 69 SELECT rowid FROM t1 WHERE content MATCH 'run jump'; 77 SELECT rowid FROM t1 WHERE content MATCH 'run jump'; 85 SELECT rowid FROM t1 WHERE content MATCH 'run jump'; 93 SELECT rowid FROM t1 WHERE content MATCH 'run jump'; 101 SELECT rowid FROM t1 WHERE content MATCH 'run jump';
|
| H A D | soak.test | 21 # By default, guarantee that the tests will run for at least 1 hour. 44 # The general principle is to run those SQLite tests that use 46 # long time. The number of tests run depends on the value of 47 # global variable $TIMEOUT - tests are run for at least $TIMEOUT 59 # List of test files that are run by this file.
|
| H A D | stmtvtab1.test | 36 SELECT run, sql FROM sqlite_stmt ORDER BY 1; 37 } {1 {SELECT run, sql FROM sqlite_stmt ORDER BY 1;} 1 {CREATE INDEX t1a ON t1(a);} 1 {INSERT INTO t… 43 SELECT reprep,run,SQL FROM sqlite_stmt WHERE sql LIKE '%INSERT%' AND NOT busy; 50 SELECT reprep,run,SQL FROM sqlite_stmt WHERE sql LIKE '%INSERT%' AND NOT busy; 58 SELECT reprep,run,SQL FROM sqlite_stmt WHERE sql LIKE '%INSERT%' AND NOT busy;
|
| H A D | insert4.test | 86 # Do not run the transfer optimization if there is a LIMIT clause 107 # Do not run the transfer optimization if there is a DISTINCT 159 # Do run the transfer optimization if tables have identical 169 # Do run the transfer optimization if the destination table lacks 177 # Do run the transfer optimization if the destination table omits 184 # Do not run the optimization if the destination has NOT NULL 201 # Do run the transfer optimization if the destination table and 218 # Do not run the optimization if any corresponding table 229 # run here.
|
| H A D | walthread.test | 25 # How long, in seconds, to run each test for. If a test is set to run for 70 # -seconds SECONDS How many seconds to run the test for 71 # -init SCRIPT Script to run before test. 72 # -thread NAME COUNT SCRIPT Scripts to run in threads (or processes). 74 # -check SCRIPT Script to run after test. 287 # Turn off auto-checkpoint. Otherwise, an auto-checkpoint run by a 312 # This test has clients run the following procedure as fast as possible
|
| H A D | veryquick.test | 7 # This file runs all the tests run by quick.test except for those related 9 # run time is reduced by about 75%.
|
| H A D | wapptest.tcl | 793 --platform PLATFORM (which tests to run) 794 --config GLOB (only run configurations matching GLOB) 795 --smoketest (run "make smoketest" only) 796 --veryquick (run veryquick.test only) 797 --buildonly (build executables, do not run tests) 802 --debug (Also run [n]debugging versions of tests)
|
| H A D | waloverwrite.test | 38 # be run on it. 45 # + Check that if recovery is run on the resulting wal file, the rolled 48 # The above is run twice - once where the wal file is empty at the start of
|
| H A D | func3.test | 119 # during run-time (that is, during calls to sqlite3_step()). 150 # run-time (that is, during calls to sqlite3_step()). 194 # run-time (that is, during calls to sqlite3_step()).
|
| H A D | thread003.test | 78 puts "Starting thread003.2 (should run for ~$nSecond seconds)" 114 puts "Starting thread003.3 (should run for ~$nSecond seconds)" 153 puts "Starting thread003.4 (should run for ~$nSecond seconds)"
|
| H A D | fts1d.test | 31 SELECT rowid FROM t1 WHERE content MATCH 'run jump'; 36 SELECT snippet(t1) FROM t1 WHERE t1 MATCH 'run jump';
|
| H A D | fts2d.test | 31 SELECT rowid FROM t1 WHERE content MATCH 'run jump'; 36 SELECT snippet(t1) FROM t1 WHERE t1 MATCH 'run jump';
|
| /sqlite-3.40.0/ext/fts5/test/ |
| H A D | fts5version.test | 48 } {1 {invalid fts5 file format (found 5, expected 4) - run 'rebuild'}} 54 } {1 {invalid fts5 file format (found 5, expected 4) - run 'rebuild'}} 62 } {1 {invalid fts5 file format (found 0, expected 4) - run 'rebuild'}}
|
| /sqlite-3.40.0/ |
| H A D | README.md | 56 Then run commands like this: 76 build directory and then from the build directory run the configure 77 script found at the root of the source tree. Then run "make". 120 SQLite does not require [Tcl](http://www.tcl.tk/) to run, but a Tcl installation 157 of the automatically-generated files, simply run "make target_source". 198 parser for your new PRAGMA, then run the script to regenerate the 215 tool/mksqlite3c.tcl script is run to copy them all together in just the 221 can be run on the amalgamation to break it up into a single small C file 267 virtual machine code to run queries efficiently. This file is 281 between SQLite and the underlying operating system using the run-time [all …]
|
| /sqlite-3.40.0/ext/recover/ |
| H A D | recovercorrupt2.test | 33 $R run 54 $R run 95 $R run 137 $R run 158 catch { $R run } 284 catch { $R run }
|
| H A D | recover1.test | 47 $R run 63 $R run 210 $R run 211 $R run
|
| H A D | recoverold.test | 42 $R run 60 $R run 176 $R run
|
| H A D | recoversql.test | 33 $R run 44 $R run
|
| H A D | recoverfault.test | 51 $R run 77 $R run
|
| H A D | recoverfault2.test | 54 $R run 86 $R run
|
| /sqlite-3.40.0/ext/repair/test/ |
| H A D | README.md | 1 To run these tests, first build sqlite3_checker: 7 Then run the "test.tcl" script using:
|
| /sqlite-3.40.0/tool/ |
| H A D | kvtest-speed.sh | 23 valgrind --tool=cachegrind ./kvtest run kvtest.db $KVARGS 2>&1 | tee summary-kvtest-$NAME.txt 28 valgrind --tool=cachegrind ./kvtest run kvtest.db $KVARGS --blob-api 2>&1 | tee -a summary-kvtest-$…
|
| /sqlite-3.40.0/ext/wasm/ |
| H A D | README.md | 24 Those parts only need to be run once, but the SDK can be updated using: 32 The following needs to be run for each shell instance which needs the 73 That will open the system's browser and run the index page, from which
|
| /sqlite-3.40.0/autoconf/ |
| H A D | INSTALL | 29 you can run in the future to recreate the current configuration, and a 61 3. Optionally, type `make check' to run any self-tests that come with 94 This target is generally not run by end users. 117 directory where you want the object files and executables to go and run 260 will run on. Usually, assuming the package is built to be run on the 284 eventually be run) with `--host=TYPE'. 301 environment passed to `configure'. However, some packages may run
|
| /sqlite-3.40.0/autoconf/tea/ |
| H A D | README | 10 Building under most UNIX systems is easy, just run the configure script 11 and then run make. For more information about the build process, see
|