Home
last modified time | relevance | path

Searched refs:second (Results 1 – 25 of 152) sorted by relevance

1234567

/sqlite-3.40.0/test/
H A Dintpkey.test76 INSERT INTO t1 VALUES(5,'second','entry');
87 INSERT INTO t1 VALUES(6,'second','entry');
98 } {5 5 hello world 6 6 second entry}
108 } {hello one second}
117 } {4 one two 5 hello world 6 second entry}
163 } {-3 y z 4 one two 5 hello world 6 second entry}
208 SELECT rowid, * FROM t1 WHERE b<'second'
213 SELECT rowid, * FROM t1 WHERE 'second'>b
236 } {5 hello world 6 second entry 8 y z}
242 } {5 hello world 6 second entry -4 y z}
[all …]
H A Dconflict3.test46 # Insert two rows where the second conflicts on C. The first row show go
76 # Insert two rows where the second conflicts on C. The first row show go
106 # Insert two rows where the second conflicts on C. The first row show go
136 # Insert two rows where the second conflicts on C. The first row show go
166 # Insert two rows where the second conflicts on C. The first row show go
196 # Insert two rows where the second conflicts on C. The first row show go
226 # Insert two rows where the second conflicts on C. The first row show go
256 # Insert two rows where the second conflicts on C. The first row show go
286 # Insert two rows where the second conflicts on C. The first row show go
316 # Insert two rows where the second conflicts on C. The first row show go
[all …]
H A Dcrash8.test55 # Potential corruption scenario 1. A second process opens the database
56 # and modifies a large portion of it. It then opens a second transaction
62 # was loaded before the second process made its first, successful,
76 # Potential corruption scenario 2. The second process, operating in
79 # was written to the file. It then opens a second transaction and makes
81 # written to the journal file. The second change is such that the
84 # first, successful, change. The second process crashes before it can
85 # commit its second change.
88 # the second aborted transaction, then continuing to rollback the second
H A Dlock2.test24 # lock2-1.1: Connect a second process to the database.
26 # lock2-1.3: Get a SHARED lock with the second process.
30 # lock2-1.6: Release the SHARED lock held by the second process.
31 # lock2-1.7: Attempt to reaquire a SHARED lock with the second process.
H A Dfts4growth.test193 proc second {x} { lindex $x 1 }
194 db func second second
200 execsql { SELECT level, idx, second(end_block) FROM x3_segdir }
211 execsql { SELECT level, idx, second(end_block) FROM x3_segdir }
215 execsql { SELECT level, idx, second(end_block) FROM x3_segdir }
226 execsql { SELECT level, idx, second(end_block) FROM x3_segdir }
241 execsql { SELECT level, idx, second(end_block) FROM x3_segdir WHERE level=1 }
261 SELECT level, idx, second(end_block) FROM x4_segdir
H A Dfts3ak.test57 INSERT INTO t1 (rowid, content) VALUES(8, 'second world');
58 INSERT INTO t1 (rowid, content) VALUES(9, 'second sight');
76 INSERT INTO t1 (rowid, content) VALUES(10, 'second world');
77 INSERT INTO t1 (rowid, content) VALUES(11, 'second sight');
H A Dfts2k.test57 INSERT INTO t1 (rowid, content) VALUES(8, "second world");
58 INSERT INTO t1 (rowid, content) VALUES(9, "second sight");
76 INSERT INTO t1 (rowid, content) VALUES(10, "second world");
77 INSERT INTO t1 (rowid, content) VALUES(11, "second sight");
H A Dlock4.test49 # 1. Create a second database test2.db
63 # Create a script for the second process to run.
90 # Kick off the second process.
93 # Wait until the second process has started its transaction on test2.db.
H A Dfts4growth2.test79 db func second second
80 proc second {L} {lindex $L 1}
H A Dsync2.test115 # one on the wal file. The second does no syncs.
123 # First transaction syncs the wal file once, the second not at all.
124 # one on the wal file. The second does no syncs.
131 # directory, two on the journal file, one on the db. The second does
H A Dtkt3810.test35 # Create a second connection to the same database. Make sure the
36 # schema of the database has been parsed by the second connection.
45 # DROP the table using the second connection. The table no longer exists
H A Ddate.test138 datetest 2.42 {datetime('2003-10-22 12:24','345 second')} {2003-10-22 12:29:45}
139 datetest 2.43 {datetime('2003-10-22 12:24','4 second')} {2003-10-22 12:24:04}
140 datetest 2.44 {datetime('2003-10-22 12:24','56 second')} {2003-10-22 12:24:56}
141 datetest 2.45 {datetime('2003-10-22 12:24','60 second')} {2003-10-22 12:25:00}
142 datetest 2.46 {datetime('2003-10-22 12:24','70 second')} {2003-10-22 12:25:10}
144 datetest 2.48 {datetime('2003-10-22 12:24','9.4 second')} {2003-10-22 12:24:09}
145 datetest 2.49 {datetime('2003-10-22 12:24','0000 second')} {2003-10-22 12:24:00}
146 datetest 2.50 {datetime('2003-10-22 12:24','0001 second')} {2003-10-22 12:24:01}
H A Dfunc3.test105 } {1 {second argument to likelihood() must be a constant between 0.0 and 1.0}}
110 } {1 {second argument to likelihood() must be a constant between 0.0 and 1.0}}
115 } {1 {second argument to likelihood() must be a constant between 0.0 and 1.0}}
H A Dextension01.test43 SELECT writefile('./file2.txt', 'A second test line');
51 } {{A second test line} 18}
H A Dtkt3093.test49 # the lock so that there should not be a second callback. If the
50 # busy handler is called a second time, then fail so that we get
H A Dtkt4018.test46 # The database is locked by connection [db]. Open and close a second
58 # having a second process try to write the db.
H A Dwalslow.test148 # second connection is opened on the database file, it is possible
150 # second connection.
152 # 4.4.*: Same test as wal-13.3.*. Except in this case the second
H A Dtkt-b72787b1.test66 # The runsql() call on the second row of the first query will
70 # second SELECT was reached. After the fix, the current statement
H A Dtkt2820.test68 # while a second statement was active, as long as we are in autocommit
82 # constraint violation on the second inserted row. This
H A Dcapi3b.test46 # Make sure the second database connection can see the data
80 # The first connection closes its transaction. This allows the second
H A Dtemptrigger.test40 # executed by a second connection connected to the
43 # temptrigger-1.3: Using the second connection to the shared-cache, cause
247 # Check that if a second connection creates a table in an attached database
H A Dschema3.test26 # second client updates its internal cache of the database schema before
29 # but was added after the second client loaded its cache of the database
H A Dautovacuum.test175 # This test case moves the second page in an over-flow chain.
186 # Create another table. Check it is located immediately after the second.
198 # Create another table. Check it is located immediately after the second.
272 # desired root-pages reside on the second free-list trunk page, and that the
572 # logic so that if an index/table was moved twice, the second move might
/sqlite-3.40.0/ext/rbu/
H A Drburesume.test44 # 4. Opens a second RBU vacuum handle, resumes and completes the vacuum op.
81 # 4. Opens a second RBU vacuum handle on the copy, resumes and completes the
133 # 4. Opens a second RBU vacuum handle on the copy, resumes and completes the
206 # 5. Opens a second RBU handle on the copy, resumes and completes the
/sqlite-3.40.0/tool/
H A Dgenfkey.test301 "a.1 first", "b.2 second",
302 UNIQUE("a.1 first", "b.2 second")
307 REFERENCES p("a.1 first", "b.2 second")

1234567