I Use This!
Very High Activity

Commits : Listings

Analyzed about 24 hours ago. based on code collected 1 day ago.
Feb 14, 2025 — Feb 14, 2026
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Add new assert() statements to demonstrate that the complaint given in [forum:/forumpost/56ad8b632c|forum post 56ad8b632c] is not a real bug. More... 3 days ago
Use only a single bit, rather than a whole byte, to store infrequently accessed boolean values in the Parse object. More... 3 days ago
Add a "const" to avoid a harmless false-positive compiler warning. More... 3 days ago
Respect "const" strings in the sqlite3ShadowTableName() function. Patch moved to trunk, where it was intended. More... 4 days ago
Correction to date/time computations associated with the timestamp-vfs. More... 5 days ago
Minor tweaks to the star-query optimization in the query planner. More... 5 days ago
Immediately reset all pending prepared statements on any call to sqlite3_set_authorizer(), even if the authorizer is being disabled. More... 6 days ago
Do not allow table-function argument expressions on the RHS of an OUTER join to refer to FROM clause elements to their right. More... 7 days ago
Fix a method name typo in test-only code which could hide the triggering error condition. More... 8 days ago
JS doc touchups. More... 8 days ago
Improved output from calls to sqlite3ShowSrcList() made from a symbolic debugger. More... 9 days ago
Do a better job of not generating unnecessary Bloom filters associated with IN operators. More... 10 days ago
Fix harmless compiler warning when the CLI is compiled with SQLITE_OMIT_PROGRESS_CALLBACK. More... 11 days ago
Display scanstatus results in neat columns. More... 11 days ago
Improved output for ".scanstatus est" in the CLI. More... 12 days ago
Improved display of scan-status estimates. More... 12 days ago
Render scan-status values with 3 or 4 significant digits only, for improved readability. More... 12 days ago
Fix scanstatus output in QRF so that it shows the total number of cycles on the "QUERY PLAN" line. More... 12 days ago
Improve the query planner by reducing the estimated number of output rows for each stage of a join if there are LIKE, GLOB, REGEXP, or MATCH constraints on the table where the pattern string is a constant. The reduction in the output row estimate is proportional to the length of the pattern string. More... 13 days ago
Minor change to test/dotcmd01.test so that it works with STAT4. More... 13 days ago
Improved comments on this enhancement. No code changes. More... 13 days ago
Refactor the implementation of this enhancement to keep all the code inside the query planner, not leaking out into SQL function implementations. Expand the enhancement to cover MATCH and REGEXP operators and overloads of LIKE and GLOB. More... 13 days ago
When reducing the truth probability of a LIKE/GLOB constraint, only consider non-wildcard characters in the pattern. More... 13 days ago
Do not reduce the estimated truth probability of LIKE and GLOB operators by quite so much. Fix a single test case whose output changed. More... 14 days ago
Merge the latest trunk enhancements into the prune-by-like-glob branch. More... 14 days ago
Update session module test code to correctly use Tcl_Size instead of int. More... 14 days ago
Add the "--timeout SECONDS" option to the ".progress" command in the CLI. More... 14 days ago
Enhance the ".timer" command in the CLI to accept the "once" argument, and so that it leaves its last real-time result in the $TIMER variable. Also fix a harmless warning from an earlier check-in. More... 15 days ago
An experimental query-planner change that reduces the estimated number of output rows for FROM clause terms that are restricted by a LIKE or GLOB operator, based on the number of bytes in the pattern. The idea is that longer patterns will match fewer records and hence should reduce the estimated output count. The implementation is not workable as it stands now. This is just a crazy idea, saved for future reference. More... 15 days ago
Fix a missed optimization opportunity due to a typo in check-in [898bfa1afd8260ea]. Reported by [forum:/forumpost/2026-01-31T00:49:53z|forum post 2026-01-31T00:49:53z]. More... 16 days ago