Home
last modified time | relevance | path

Searched refs:point (Results 1 – 25 of 158) sorted by relevance

1234567

/sqlite-3.40.0/ext/rbu/
H A Drbuvacuum2.test32 INSERT INTO t1 VALUES('fix this issue', 'at some point');
39 } {{fix this issue} {at some point}}
57 {fix this issue} {at some point}
70 INSERT INTO t1 VALUES('fix this issue', 'at some point');
77 } {{fix this issue} {at some point}}
95 {fix this issue} {at some point}
H A Drbu12.test68 # It is stuck in a permanent SQLITE_BUSY state at this point.
198 # Start stepping the RBU. From the point of view of [db1] and [db2], the
200 # modified. At which point the values are incremented.
/sqlite-3.40.0/test/
H A Dnan.test14 # Make sure IEEE floating point NaN values are handled properly.
85 # convert floating point values to text internally before returning them
87 # problems converting "inf" and "-inf" from floating point to text format.
149 # of tests writes a normal floating point value (0.5) into the database,
234 # convert from floating point value "-inf" to a string.
282 # These tests test some really, really small floating point numbers.
H A Dtkt-3998683a16.test14 # floating point values with a decimal point at the beginning or end
H A DcorruptF.test84 # At one point this was causing an assert to fail.
92 # it (which at this point are keys that have been inserted into t4). And
95 # b-tree for table t4 increased. From the point of view of the t1 cursor,
H A DcorruptB.test100 # Set the right-child pointer of the right-child of the root page to point
115 # point back to the root page.
143 # point back to the root page.
H A Dtkt1644.test27 # Create two tables T1 and T2 and make V1 point to T1.
40 # It will continue to point to T1 unless the cache is invalidated when
H A Dcorrupt.test202 # index b-tree as expected. At one point this was causing an assert()
227 # At one point, the specific corruption caused by this test case was
289 # no longer looks like a real cell). At one point the code assumed that
290 # detecting corruption was not possible at that point, and an assert() failed.
H A Dwal9.test74 # At this point connection [db2] has mapped the first 32KB of the *shm file
79 # However, at one point if a transaction that had not yet written to the
H A Dwalcrash2.test23 # existed at one point: If a process crashes mid-transaction, it may have
25 # If the transaction were to be explicitly rolled back at this point, the
H A Dshared3.test67 # The cache-size should now be 10 pages. However at one point there was
109 # At one point this was causing a faulty assert to fail.
H A Drollback.test100 # At this point files testA.db and testA.db-journal are present in the
127 # point the first query would attempt a hot rollback, attempt to open
H A Dpcache.test88 # At this point connection db2 has a read lock on the database file and a
116 # Rolling back the transaction held by db2 at this point releases a pinned
H A Dshared9.test107 # At one point, the following would cause a collation sequence belonging
216 # At one point the following would fail, showing that the busy-handler
H A Dtkt3718.test65 # that throws an exception. At one point, before #3718 was fixed, this
87 # exception is run. At one point, before #3718 was fixed, this caused the
H A Dloadext.test166 # entry point is not.
178 # Try to load an extension for which the entry point fails (returns non-zero)
H A DcorruptI.test195 # point this led to an integer overflow that caused an assert() to fail.
237 # At one point an assert() would fail if attempt was made to free page 1.
H A Dround1.test11 # Test cases for rounding behavior of floating point values.
H A Dfts3ao.test125 # This test was crashing at one point.
222 # At one point this was causing a memory leak.
H A Dtemptrigger.test33 # point of view of process 1, the temp trigger just disappeared.
143 # on tables located in attached databases. At one point when SQLite reloaded
H A Dbigsort.test18 # At one point there was an overflow problem if the product of the
H A Dovfl.test26 # an overflow page. This was at one point exposing an obscure bug in the
H A Dfts1n.test35 # This test was crashing at one point.
/sqlite-3.40.0/ext/misc/
H A DREADME.md46 of "sha3.c" because the default entry point names in SQLite are based
48 "sha3.c" then the entry point would conflict with the prior "sha1.c"
/sqlite-3.40.0/ext/rtree/
H A Drtree7.test13 # database page-size is modified. At one point (3.6.22), this was causing

1234567