/ Timeline

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

30 ancestors of [ee431d55]

Output infinity as 1e999 in the ".dump" command of the command-line shell. Leaf check-in: ee431d55 user: drh tags: trunk
Pad out the sqlite3_value structure to be a multiple of 8 bytes. check-in: f76dc33b user: drh tags: trunk
Fix some test case numbers in expert1.test. check-in: b90c3c16 user: dan tags: trunk
Unless SQLITE_OMIT_AUTOINIT is defined, allow sqlite3_vfs_unregister() to be called before sqlite3_initialize(). check-in: ab6c1ae4 user: dan tags: trunk
Check that malloc() has not already failed when invoking the xUpdate() method of a virtual table implementation. This fixes an assert() failure in FTS5 that could occur following an OOM condition. check-in: e9a7e4d5 user: dan tags: trunk
Add the unused SQLITE_CANTOPEN_DIRTYWAL result code. This code was used in some historical versions on the apple-osx branch but was removed by check-in [27e20d699872b2b8]. Restore it so that old code that actually references that result code will still compile. check-in: 9f40383e user: drh tags: trunk
Documentation update: clarify that sqlite3_errcode() and related interfaces do not themselves modify the error code. check-in: 858fc52b user: drh tags: trunk
Documentation updates: clarify the behavior of sqlite3_column and sqlite3_value interfaces following an OOM error. check-in: 428c581e user: drh tags: trunk
Improvements to SCopy correctness tracking when SQLITE_DEBUG is enabled. check-in: b2973f23 user: drh tags: trunk
Fix the "Synopsis" on the OP_BitNot opcode. check-in: acd78df6 user: drh tags: trunk
Improvements to the --enable and --disable options for the amalgamation tarball. check-in: 02e337e0 user: drh tags: trunk
Fix various --enable and --disable options on the top-level configure script. check-in: 6fd7e8ce user: drh tags: trunk
Fix the column cache invalidation logic in the code for ROWID uniqueness constraint checking in the INSERT command. This fixes ticket [c2432ef9089ee73bd]. check-in: 0b485a57 user: drh tags: trunk
Add the OP_SetTabCol and OP_VerifyTabCol opcodes, only when compiling with SQLITE_DEBUG, to do run-time verification of the column cache. check-in: b37614a3 user: drh tags: trunk
Strengthen the sqlite3VdbeMemAboutToChange() run-time verification mechanism to better detect missed calls to AboutToChange(). check-in: 793e9422 user: drh tags: trunk
Always initialize the WhereClause.hasOr field that was added by check-in [292724ffc4]. Error detected by OSSFuzz. check-in: 9faf4171 user: drh tags: trunk
Fix a typo in the amalgamation autoconf file. check-in: de0857f3 user: drh tags: trunk
Slightly smaller and faster code by encapsulating wal-index hash table location information in a separate WalHashLoc object rather than passing around the various elements as separate variables. check-in: 538a365b user: drh tags: trunk
Improved comments an presentation for the recent IN operator decision improvement. check-in: 31e480f6 user: drh tags: trunk
Performance improvement to sqlite3WhereExprUsage(). check-in: fd093413 user: drh tags: trunk
Compute the bitmask of indexed columns for each index once when the Index objecct is constructed, instead of recomputing it every time it is needed. check-in: d735872e user: drh tags: trunk
Avoid invoking the whereLoopAddOr() routine in the query planner if there are no OR operators in the WHERE clause, thus speeding up query planning slightly. check-in: 292724ff user: drh tags: trunk
When the query planner has the opportunity to use an IN operater constraint on a term of an index other than the left-most term, use the estimated number of elements on the right-hand side of the IN operator to determine if makes sense to use the IN operator with index lookups, or to just do a scan over the range of the table identified by the index terms to the left. Only do this if sqlite_stat1 measurements are available as otherwise the performance estimates will not be accurate enough to discern the best plan. Bias the decision slightly in favor of using index lookups on each element of the IN operator. check-in: 2cbbabdf user: drh tags: trunk
Only choose to scan an IN operator rather than use an index if we have real STAT1 data to suggest it is advantageous. Closed-Leaf check-in: 30e87466 user: drh tags: in-scan-vs-index
Merge the btreeNext() assertion bug fix from trunk. check-in: 11bd66e0 user: drh tags: in-scan-vs-index
Fix an assert() that can be false for a corrupt database and a strange query that uses a recursive SQL function to delete content from a corrupt database file while it is being queried. check-in: 99057383 user: drh tags: trunk
Consider doing a partial table scan to fulfill an IN operator rather than using an index. Try to pick the plan with the lowest cost. check-in: 1fa40a78 user: drh tags: in-scan-vs-index
The IN-early-out optimization: When doing a look-up on a multi-column index and an IN operator is used on a column other than the left-most column, then if no rows match against the first IN value, check to make sure there exist rows that match the columns to the right before continuing with the next IN value. check-in: 09fffbdf user: drh tags: trunk
Fix the assert()s in the byte-code engine that prove that cursors are unidirectional. Closed-Leaf check-in: 4b0b4e14 user: drh tags: multikey-opt-idea
Remove the NextIfOpen and PrevIfOpen opcodes which are no longer needed when the IN-early-out optimization is working. check-in: 439c8162 user: drh tags: multikey-opt-idea
Test cases. check-in: 085e8637 user: drh tags: multikey-opt-idea