This Day In History For 2025-11-10
2 Years Ago (more context)
|
2023-11-10
| ||
| 21:03 | Fix another problem with mixed join types and the RIGHT JOIN strength-reduction optimization. (check-in: 8f01f8b260 user: drh tags: branch-3.44) | |
| 20:55 | Fix another problem with mixed join types and the RIGHT JOIN strength-reduction optimization. Forum post befdab472d. (check-in: f1eae19231 user: dan tags: trunk) | |
| 20:46 | Additional debugging information on the tree-dump of the BETWEEN operator. (check-in: aca31e49d1 user: drh tags: trunk) | |
| 20:35 | Remove an incorrect ALWAYS() that was inserted yesterday [1e039b6eb59c0001]. (check-in: 12885e298b user: drh tags: trunk) | |
| 18:59 | Merge recent trunk enhancements and fixes into the jsonb branch. (check-in: 091a5f058d user: drh tags: jsonb) | |
| 17:49 | Ensure 8-byte alignment of data structues in sqlite3_database_file_object(). This should have appeared on trunk originally and then be cherry-picked onto the branch. Oh well.... (check-in: ac39800bb2 user: drh tags: trunk) | |
| 16:29 | Remove a NEVER() from whereAddIndexedExpr() that is reachable if there is an unknown indexed function in the schema. (check-in: a976b7208f user: drh tags: trunk) | |
| 16:11 | • Edit [530d10e93a5f63b7|530d10e93a]: Edit check-in comment. (artifact: 5777b91b1b user: drh) | |
| 15:20 | Fix an obscure problem with the join-strength-reduction optimization that could occur when mixing LEFT and RIGHT joins in the same query. (check-in: dcf1c13781 user: drh tags: branch-3.44) | |
| 15:03 | Fix an obscure problem with the join-strength-reduction optimization that could occur when mixing LEFT and RIGHT joins in the same query. Forum post 7f74ce0bee and separately post d64f0abe723ac98e. The problem was introduced by check-in [d747afda5683ca5f]. (check-in: 530d10e93a user: dan tags: trunk) | |
| 15:01 | Expose the missing SQLITE_SUBTYPE to wasm. (check-in: 7bebfe20e7 user: stephan tags: branch-3.44) | |
| 15:00 | Expose the missing SQLITE_SUBTYPE to wasm. (check-in: ac9534b2ce user: stephan tags: trunk) | |
| 15:00 | Expose the missing SQLITE_SUBTYPE to JNI. (check-in: 0f92f4c90e user: stephan tags: trunk) | |
| 14:15 | Expose SQLITE_RESULT_SUBTYPE to JNI. (check-in: 3bf75875b8 user: stephan tags: trunk) | |
| 13:13 | Fix a potential UAF caused by JSON parser cache spill. (Leaf check-in: ce3fc4fc23 user: drh tags: bedrock-3.43) | |
3 Years Ago (more context)
|
2022-11-10
| ||
| 23:10 | Remove unnecessary tabs in the ChaCha20 implementation. Forum post 0cdce5db8c. (check-in: b7179efbdb user: drh tags: trunk) | |
| 19:19 | Avoid returning SQLITE_SCHEMA if the first query run on a connection is "SELECT nosuchcolumn" or similar. Forum post c1798f77ef (Closed-Leaf check-in: d31c019fd6 user: dan tags: schema-error-fix) | |
| 13:22 | Automatically relinquish implicitly-acquired OPFS file locks during VFS idle time in an attempt to help alleviate cross-tab locking contention like that described in forum post 58a377083cd24a. (check-in: 8daf24ff73 user: stephan tags: trunk) | |
| 13:14 | Rework automatically acquired OPFS locks to be released during idle time. This eliminates the performance hit reported in [46304ba057707c]. (Closed-Leaf check-in: a7fe91afca user: stephan tags: opfs-lock-without-xlock) | |
| 11:38 | • Edit [46304ba057707c3b|46304ba057]: Edit check-in comment. (artifact: d394242c2a user: stephan) | |
| 11:35 | OPFS: if an op which needs a lock is called when no lock has been obtained, automatically lock it at the start of the op and unlock it at the end of that op. This is an attempt to alleviate the cross-tab contention described in forum post 58a377083cd24a but it increases speedtest1 run time by approximately 4x. Perhaps auto-lock can be combined with the older idle-time-based auto-unlock to unlock such locks (but not those from xLock()) to improve this? (check-in: 46304ba057 user: stephan tags: opfs-lock-without-xlock) | |
4 Years Ago (more context)
|
2021-11-10
| ||
| 15:23 | Load new test cases into test/fuzzdata8.db (check-in: 8b53ffe99d user: drh tags: trunk) | |
| 10:59 | Make SQLITE_CORRUPT sticky: If a CORRUPT error is returned, all subsequent write statements within the same transaction also fail early with SQLITE_CORRUPT. (check-in: 3feb0f1c38 user: drh tags: trunk) | |
10 Years Ago (more context)
|
2015-11-10
| ||
| 14:51 | Improved output formatting for "PRAGMA parser_trace=ON;". (check-in: e43e1171fd user: drh tags: trunk) | |
| 14:27 | Make the output of "PRAGMA parser_trace" go to stdout instead of stderr. (check-in: 1e4849911e user: drh tags: trunk) | |
| 13:45 | Save a few bytes in the parser by using "int" instead of "u8" or "u16" for all small integer types. (check-in: 5dcd212bf6 user: drh tags: trunk) | |
| 12:41 | Change all parsers to use the standard "lempar.c" template in the tool/ folder and remove the customized lempar.c from src/, plus other compiler performance and space enhancements. (check-in: 0e7fb24ad3 user: drh tags: trunk) | |
| 12:31 | Fix harmless compiler warnings in FTS5. (Closed-Leaf check-in: 09752e51a1 user: drh tags: parser-enhancements) | |
| 03:46 | • Edit [0a72991f4e54548f|0a72991f4e]: Move to branch parser-enhancements. (artifact: 339db74349 user: drh) | |
| 03:30 | Performance enhancement to the tokenizer. (check-in: 6ea2df86c9 user: drh tags: parser-enhancements) | |
| 00:02 | Remove an unused non-terminal from the grammar. (check-in: 3c37c52288 user: drh tags: parser-enhancements) | |