This Day In History For 2025-06-20
1 Year Ago (more context)
|
2024-06-20
| ||
| 12:07 | Do not attempt the exists-to-join optimization if the FROM clause is full. (check-in: 8e3a1d2850 user: drh tags: exists-to-join) | |
2 Years Ago (more context)
|
2023-06-20
| ||
| 17:45 | Omit unnecessary calls to table locking routines in the common case when there is no shared cache. (check-in: f94f3021cd user: drh tags: trunk) | |
| 16:26 | Avoid unnecessary calls to sqlite3DeleteTable() with NULL pointers. (check-in: 4a35f39199 user: drh tags: trunk) | |
| 15:48 | Avoid unnecessary calls to sqlite3CodeRowTrigger(). (check-in: 27c174dbd0 user: drh tags: trunk) | |
| 11:46 | Performance optimization in sqlite3VdbeAddOp4Int(). (check-in: 456a24324b user: drh tags: trunk) | |
3 Years Ago (more context)
|
2022-06-20
| ||
| 19:12 | Add an ALWAYS() macro to an always-true branch. (check-in: 364645d8fe user: drh tags: trunk) | |
| 18:26 | Do not allow FROM-clause terms on the left side of a RIGHT or FULL JOIN to be reordered. forum post 6650cd40b5634f35. This is probably more strict that necessary to get correct behavior, but for the first release that supports RIGHT/FULL JOIN it is perhaps better to be correct than fast. A less strict constraint might be to prohibit FROM-clause terms that originate on the left side of a RIGHT JOIN from crossing from the right side to the left side of a LEFT JOIN. Revisit this later. (check-in: 238453ffab user: drh tags: trunk) | |
| 17:04 | Do not allow an ON clause to references tables to its right if there is a RIGHT or FULL join anywhere in the query. Other RDBMSes prohibit this always, but SQLite must allow ON clauses to reference tables to their right for legacy compatibility, unless there is a RIGHT or FULL join someplace in the query, in which case there is no legacy to support. (check-in: e615dbe02c user: drh tags: trunk) | |
| 12:42 | The fix at [cab9b4cccd13bf0a] was incomplete, as demonstrated by forum post 57bdf2217d. This check-in should complete the fix. (check-in: fb0a23b678 user: drh tags: trunk) | |
4 Years Ago (more context)
|
2021-06-20
| ||
| 22:52 | Load recent dbsqlfuzz cases into test/fuzzdata8.db. (check-in: a766bba0ee user: drh tags: trunk) | |
| 22:49 | Remove a NEVER() that is reachable by a corrupt database. dbsqlfuzz 8456a0f88e39a49fb675d8f77394979ebb2a03c1. Test case in TH3. (check-in: 1c41e86fa1 user: drh tags: trunk) | |
| 22:17 | Do not allow an SQLITE_CORRUPT error to mask a prior SQLITE_IOERR in balance_nonroot(). dbsqlfuzz 5e1c86e7f18023f2b9abe3429977d7ea726f50d8 (check-in: 50e818767e user: drh tags: trunk) | |
5 Years Ago (more context)
|
2020-06-20
| ||
| 03:43 | Work around a bug (an incorrect warning) in Clang-8. (check-in: 067291143a user: drh tags: trunk) | |
10 Years Ago (more context)
|
2015-06-20
| ||
| 18:13 | Split out all four cases of cellSizePtr() into different methods, each optimized for the specific page type. This gives a 0.36% performance increase at a cost of about 300 bytes of code. (Leaf check-in: 522502ec18 user: drh tags: btree-opt) | |
| 14:11 | Update the fuzztest data using the latest test vectors discovered by AFL. (check-in: b97f9cf73e user: drh tags: trunk) | |
| 13:18 | Make sure that the likelihood() function does not mess up generation of result-set code when it is used (inappropropriately) in a result-set expression. (check-in: 7cdbae625e user: drh tags: trunk) | |