This Day In History For 2019-06-08
1 Year Ago (more context)
2018-06-08
| ||
23:24 | • Edit [2cbbabdf5ef624d8|2cbbabdf5e]: Edit check-in comment. (artifact: 1521d91737 user: drh) | |
23:23 | 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: 2cbbabdf5e user: drh tags: trunk) | |
21:21 | 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: 30e874661d user: drh tags: in-scan-vs-index) | |
20:58 | Add support for the WINDOW clause. (check-in: 19c983b511 user: dan tags: exp-window-functions) | |
19:54 | Merge the btreeNext() assertion bug fix from trunk. (check-in: 11bd66e090 user: drh tags: in-scan-vs-index) | |
19:13 | 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: 99057383ac user: drh tags: trunk) | |
18:22 | 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: 1fa40a78fe user: drh tags: in-scan-vs-index) | |
16:11 | Do not flatten sub-queries that contain window functions. (check-in: 236cb75bd1 user: dan tags: exp-window-functions) | |
11:45 | Fixes to allow group_concat() to be used as a window function. (check-in: 89bbc9ba8f user: dan tags: exp-window-functions) | |
2 Years Ago (more context)
2017-06-08
| ||
16:23 | Update the recent auto-vacuum fix so that it works for the in-memory pointer-map structure used by this branch. (check-in: 8e311a6dba user: dan tags: begin-concurrent) | |
16:10 | Merge 3.19.3 changes with this branch. (check-in: e2d38d51a9 user: dan tags: begin-concurrent) | |
15:54 | Merge changes for version 3.19.0 with this branch. (check-in: 0f59bb94d5 user: dan tags: begin-concurrent) | |
14:41 | Merge the auto_vacuum bug fix and all other changes from the 3.19.3 release. (check-in: 93f32dd2dd user: drh tags: apple-osx) | |
14:35 | Add a testcase() to confirm that an OOM on sqlite3DbStrNDup() is handled correctly in trigger.c. (check-in: 343e55992f user: drh tags: trunk) | |
14:26 | Version 3.19.3 (check-in: 0ee482a1e0 user: drh tags: release, version-3.19.3, branch-3.19) | |
13:10 | • Fixed ticket [fda2210880]: Corruption due to REPLACE in an auto-vacuumed database plus 3 other changes (artifact: eee8ce590c user: drh) | |
11:32 | Fix an issue with OPT_FEATURE_FLAGS in configure.ac. (check-in: 97b5c4a53d user: drh tags: branch-3.19) | |
11:27 | Increase the version number to 3.19.3. (check-in: 903fff53b3 user: drh tags: branch-3.19) | |
11:26 | Ensure pointer map entries are always added when a row that does use overflow pages replaces one that does not in an auto-vacuum database. Fix for [fda22108]. (check-in: 9478106ca9 user: drh tags: branch-3.19) | |
11:14 | Ensure pointer map entries are always added when a row that does use overflow pages replaces one that does not in an auto-vacuum database. Fix for [fda22108]. (check-in: b30dfba811 user: dan tags: trunk) | |
11:08 | • Ticket [fda2210880] Corruption due to REPLACE in an auto-vacuumed database status still Open with 6 other changes (artifact: 7b1cb0c798 user: drh) | |
11:07 | • New ticket [fda2210880]. (artifact: 548c43a861 user: drh) | |
3 Years Ago (more context)
2016-06-08
| ||
18:07 | Prefer to use partial indexes for full table scans when that is possible. (check-in: fe1874321b user: drh tags: trunk) | |
14:04 | Add the "dbhash.exe" utility program that computes a SHA1 hash over the invariant content of an SQLite database file. Free space in the file, the page size, auto_vacuum status, text encoding, and so forth do not change the hash. Only the content matters. (check-in: f48a4ad33e user: drh tags: trunk) | |
13:59 | Fix an undersized buffer in the SHA1 implementation. (Closed-Leaf check-in: fb2768154c user: drh tags: dbhash) | |
13:49 | Fix the dbhash utility so that it ignores the root page number when hashing the sqlite_master table. Add new command-line options. Add the ability to hash multiple databases with a single command. (check-in: 44f157e0f0 user: drh tags: dbhash) | |
01:03 | An initial attempt at a "dbhash" command-line utility. (check-in: 2247649ca2 user: drh tags: dbhash) | |
4 Years Ago (more context)
2015-06-08
| ||
22:59 | Code refactoring to try to shift FROM-clause subquery manifesting until after the query planner runs. Except this does not currently work because the query planner needs an estimated of the number of rows in the manifested table. Work in progress. (check-in: cabf218716 user: drh tags: view-optimization) | |
19:15 | Add the valgrindfuzz target to unix makefile. (check-in: e62aed01f1 user: drh tags: trunk) | |
18:48 | If a query contains "FROM t1 LEFT JOIN t2, t3, t4", ensure that tables t3 and t4 are not scanned before t2. The trunk already does this. (check-in: 0d9edfab9f user: dan tags: vtab-left-join) | |
18:05 | Avoid passing constraints that are unusable due to LEFT or CROSS joins to virtual table xBestIndex() methods. (check-in: 80ee56dda7 user: dan tags: vtab-left-join) | |
17:42 | Fix typo in comment. No changes to code. (check-in: e49c291735 user: mistachkin tags: trunk) | |
17:40 | Split out some source code into new files: wherecode.c, whereexpr.c, and treeview.c. Other minor refactoring changes. (check-in: 50f336818c user: drh tags: trunk) | |
15:08 | Factor out the TreeView parse tree printing module into a separate file. (check-in: c32ce54ca4 user: drh tags: view-optimization) | |
14:23 | Split more subfunctions of where.c out into a new whereexpr.c source file, for improved maintainability. (check-in: 46ef95c108 user: drh tags: view-optimization) | |
10 Years Ago (more context)
2009-06-08
| ||
19:44 | Additional comments to clarify the operation of the LIKE optimizer in where.c. (CVS 6731) (check-in: cc9c12170c user: drh tags: trunk) | |
17:11 | Clarification of the operation of the OR-term optimizer in where.c. (CVS 6730) (check-in: 6b42dc3d04 user: drh tags: trunk) | |
14:49 | Change the btree balance code so that it does not call balance_nonroot() recursively. (CVS 6729) (check-in: 7863db904d user: danielk1977 tags: trunk) | |
12:52 | Increase the version number to 3.6.15 in preparation for the next release. (CVS 6728) (check-in: 456ea541d6 user: drh tags: trunk) | |
15 Years Ago (more context)
2004-06-08
| ||
00:47 | Do not require a RESERVED lock when transitioning from SHARED to EXCLUSIVE. (CVS 1542) (check-in: 4dfdea7373 user: drh tags: trunk) | |
00:39 | Enhance the built-in function quote() to support blob values. (CVS 1541) (check-in: 97aa54bb70 user: danielk1977 tags: trunk) | |
00:02 | Remove the third argument from the sqlite3_open() API. (CVS 1540) (check-in: 62e31f396c user: danielk1977 tags: trunk) | |