This Day In History For 2023-10-22
1 Year Ago (more context)
|
2022-10-22
| ||
| 23:09 | More frequently send the complete SELECT statement into sqlite3WhereBegin() so that it can more accurately determine index coverage. (check-in: f6d09c5a0d user: drh tags: covering-index-enh) | |
| 20:13 | Enhance the query planner with the ability to discern when an index is covering even when it indexes columns well beyond the 63rd column. (check-in: 1390417be4 user: drh tags: covering-index-enh) | |
| 14:16 | This branch attempts to improve the detection of covering indexes. This first check-in merely improves a parameter name to sqlite3WhereBegin() to be more descriptive of what it contains, and ensures that a subroutine is not inlines so that sqlite3WhereBegin() runs slightly faster. (check-in: cadf5f6bb1 user: drh tags: covering-index-enh) | |
| 13:49 | Clarification on the meaning of SrcList and SrcItem and especially the SrcItem.colUsed and Index.colNotIdxed fields. Comment changes only - no changes to code. (check-in: d96f6cc847 user: drh tags: trunk) | |
2 Years Ago (more context)
|
2021-10-22
| ||
| 11:17 | Fix harmless compiler warnings. Improve the independence of some TCL tests. (check-in: 1a038242dc user: drh tags: trunk) | |
3 Years Ago (more context)
|
2020-10-22
| ||
| 18:59 | • Edit [263293f1e6db2603|263293f1e6]: Edit check-in comment. (artifact: 37c2e79b15 user: drh) | |
| 18:58 | Minor tweaks to query planning weights so that when STAT4 is enabled and functioning, a full table scan is more likely to be selected if that seems like the fastest solution. Only do this when STAT4 info is available because an error has a large potential downside. (check-in: 263293f1e6 user: drh tags: branch-3.28) | |
| 18:50 | Minor tweaks to query planning weights so that when STAT4 is enabled and functioning, a full table scan is more likely to be selected if that seems like the fastest solution. Only do this when STAT4 info is available because an error has a large potential downside. (check-in: 0e7e113d9f user: drh tags: trunk) | |
| 18:16 | Test case updates. (Closed-Leaf check-in: 27c681c9c6 user: drh tags: avoid-bad-indexes) | |
| 15:47 | Sometimes it makes sense to do a full table scan rather than try to use an index when most of the rows will be selected. This branch is trying to tune the query planner to make that happen more often. (check-in: 0f42099ad6 user: drh tags: avoid-bad-indexes) | |
4 Years Ago (more context)
|
2019-10-22
| ||
| 21:01 | Take the declared column time into account when computing the values for generated columns, and apply appropriate affinity. (check-in: 9e04ba22df user: drh tags: generated-columns) | |
| 20:16 | Merge the row-value fix from trunk. (check-in: 1fbd743861 user: drh tags: generated-columns) | |
| 19:51 | • Fixed ticket [6ef984af89]: Row value comparison yields incorrect result plus 5 other changes (artifact: 52b4cb4450 user: drh) | |
| 19:51 | Disqualify row-value comparisons for use by an index if the right-hand side has an affinity that does not match the index. Fix for ticket [6ef984af8972c2eb] (check-in: 5c118617cf user: drh tags: trunk) | |
| 15:45 | Do not allow generated columns in the PRIMARY KEY. (check-in: 1a54743a3d user: drh tags: generated-columns) | |
| 14:05 | • New ticket [6ef984af89] Row value comparison yields incorrect result. (artifact: eb28040c9a user: mrigger) | |
| 13:59 | In UPDATE processing, include generated columns in the set of columns being updated if and only if their generator expressions reference some other column that is being updated. (check-in: d38176e93a user: drh tags: generated-columns) | |
| 13:01 | New testcase() macros. Fix a problem with INSERT when the IPK is to the right of generated columns. (check-in: 412799fc55 user: drh tags: generated-columns) | |
| 12:02 | Merge changes on trunk into the generated-columns branch. (check-in: ba123b8c20 user: drh tags: generated-columns) | |
| 11:29 | Previous check-in to fix [b47e3627ecaadbde] was incomplete. This check-in completes the fix and adds a test cases. (check-in: c7da1c01f1 user: drh tags: trunk) | |
| 10:43 | • Ticket [b47e3627ec] Comparison of row values results in incorrect result status still Fixed with 3 other changes (artifact: e283b6c1b8 user: mrigger) | |
| 01:00 | Move the sqlite3LocateCollSeq(), sqlite3FindCollSeq(), and sqlite3GetCollSeq() routines so that they are all beside one another in the callback.c source file. No logic changes. (check-in: 9ff80a9bf8 user: drh tags: trunk) | |
| 00:03 | • Fixed ticket [b47e3627ec]: Comparison of row values results in incorrect result plus 5 other changes (artifact: f7f3b529b7 user: drh) | |
| 00:03 | When flipping ("commuting") a comparison operator, set the new EP_Commuted bit rather than adding extra EP_Collate bits, to single later processing that the order of precedence for COLLATE operators is inverted. Fix for ticket [b47e3627ecaadbde] (check-in: 90f7c47735 user: drh tags: trunk) | |
10 Years Ago (more context)
|
2013-10-22
| ||
| 18:01 | The Index object now has nKeyCol and nColumn. nColumn is the total number of columns and nKeyCol is the number of key columns. Currently these always differ by one. Refactor aiColumn[] to be of type i16 instead of int. (check-in: a106ce86cd user: drh tags: omit-rowid) | |
| 14:28 | Add a procedure to handle the messy details of allocating an Index object from the heap. (check-in: 45efc94f9a user: drh tags: omit-rowid) | |
| 10:23 | Extra backwards-compatibility tests verify that UNIQUE and PRIMARY KEY indices are created in the correct order. Other backwards-compatibility tests already cover this, but it does not hurt to double up. (check-in: 5ca0ea2e9b user: drh tags: omit-rowid) | |
| 01:18 | • Edit [4e69dd5f9bc566e7|4e69dd5f9b]: Mark "Closed". (artifact: d91aa0d1fd user: drh) | |
| 01:18 | Previous refactor is not going to be helpful because implied indices must be created in the same order that they appear in the CREATE TABLE statement for backwards compatibility. This is a much smaller change to clean up a few loose ends. (check-in: 824b549f9b user: drh tags: omit-rowid) | |
15 Years Ago (more context)
|
2008-10-22
| ||
| 18:27 | Updated configure/makefiles to handle SQLITE_ENABLE* compile options. Made sure makefile passes command line options (OPTS=-Dfoo) to the compiler. Add -DSQLITE_COVERAGE_TEST=1 if gcov being used. (CVS 5838) (check-in: acb106e51f user: shane tags: trunk) | |
| 16:55 | Removed some more dead code and fixed some unresolved externals for WINCE. Ticket #3420. (CVS 5837) (check-in: 5276e31d42 user: shane tags: trunk) | |
| 16:26 | Make sure variable declarations occur first in code blocks. (CVS 5836) (check-in: b78f44c91f user: shane tags: trunk) | |
| 16:04 | Test cases for ticket #3442. (CVS 5835) (check-in: a8bb5acf70 user: shane tags: trunk) | |
| 10:45 | Fix an assert() failure that can occur following a malloc() failure. Ticket #3455. (CVS 5834) (check-in: e0d3aa75b4 user: danielk1977 tags: trunk) | |
20 Years Ago (more context)
|
2003-10-22
| ||
| 22:15 | Comment changes to the lemon parser template. Change some sqliteMalloc() calls to sqliteMallocRaw() for speed. Update the website template. (CVS 1114) (check-in: c637caf13f user: drh tags: trunk) | |