Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 most recent check-ins related to "branch-3.44"
|
2025-02-19
| ||
| 00:18 | Version 3.44.4 (Leaf check-in: f1e31fd996 user: drh tags: branch-3.44, version-3.44.4, patch-release) | |
|
2025-02-18
| ||
| 18:05 | Cherry pick recent fixes into branch-3.44. (check-in: 75bbd094db user: drh tags: branch-3.44) | |
|
2025-02-17
| ||
| 14:27 | Harden the SQLITE_DBCONFIG_LOOKASIDE interface against misuse. This is a simplification of [1ec4c308c76c69fb] appropriate for use in a patch release. (check-in: 78c4994c1c user: drh tags: branch-3.49) | |
|
2025-02-16
| ||
| 10:57 | Add a typecast to avoid 32-bit integer overflow in the concat_ws() function with an enormous separator values and many arguments. (check-in: 498e3f1cf5 user: drh tags: trunk) | |
|
2024-04-12
| ||
| 15:15 | Mark the BTree cell overflow cache as invalid whenever the rowid goes invalid. (check-in: 0ec6669c84 user: drh tags: branch-3.44) | |
| 02:57 | Mark the BTree cell overflow cache as invalid whenever the rowid goes invalid. (check-in: 74c9e19c92 user: drh tags: btree-ovfl-cache) | |
|
2024-04-09
| ||
| 14:08 | Ignore CHECK constraints when qualifying the xfer optimization while running VACUUM. (check-in: 944d1b6eb3 user: drh tags: branch-3.44) | |
| 13:57 | The read-only CHECK-constraint optimization of [34ddf02d3d21151b] inhibits the xfer optimization for tables with CHECK constraints. However, the xfer optimization is required for correct operation of VACUUM INTO on tables that contain generated columns. Fix this by ignoring CHECK constraints when qualifying the xfer optimization while running VACUUM. Problem reported by forum post 3ec177d68fe7fa2c. (check-in: a6e26e7788 user: drh tags: trunk) | |
|
2024-04-05
| ||
| 14:13 | Check-in a9657c87c53c1922 is wrong: the IndexedExpr.bMaybeNullRow flag is required for virtual columns if they are part of an outer join. Add a test case to prove it. (check-in: 083b0f7e77 user: drh tags: branch-3.44) | |
| 13:56 | Check-in [a9657c87c53c1922] is wrong: the IndexedExpr.bMaybeNullRow flag is required for virtual columns if they are part of an outer join. Add a test case (derived from dbsqlfuzz b9e65e2f110df998f1306571fae7af6c01e4d92b) to prove it. (check-in: 4484ec6d26 user: drh tags: trunk) | |
| 11:28 | When compiling with SQLITE_ALLOW_ROWID_IN_VIEW, if the RETURNING clause of an UPDATE of a view specifies a rowid, then return NULL for the value of that rowid. This is version 3.44.3. (check-in: d38cfa6067 user: drh tags: branch-3.44, version-3.44.3) | |
| 11:23 | When compiling with SQLITE_ALLOW_ROWID_IN_VIEW, if the RETURNING clause of an UPDATE of a view specifies a rowid, then return NULL for the value of that rowid. dbsqlfuzz 7863696e9e5ec10b29bcf5ab2681cd6c82a78a4a. (check-in: c7896e8885 user: drh tags: trunk) | |
|
2024-03-24
| ||
| 21:15 | Fix the xBestIndex method of the pragma virtual table so that it correctly gives a higher cost to plans where the schema hidden parameter is unconstrained. (check-in: d68fb8b5db user: drh tags: branch-3.44) | |
| 21:10 | Fix the xBestIndex method of the pragma virtual table so that it correctly gives a higher cost to plans where the schema hidden parameter is unconstrained. Fix for the problem reported by forum post 85b6a8b6705fb77a. (check-in: bc516ff520 user: drh tags: trunk) | |
| 16:42 | Do not automatically assume that ROWID is NOT NULL when compiled with SQLITE_ALLOW_ROWID_IN_VIEW. dbsqlfuzz 31b38eeb63a4e1562de665078f52b7b47a7543cf (check-in: b5d2dce18f user: drh tags: branch-3.44) | |
| 16:33 | Do not automatically assume that ROWID is NOT NULL when compiled with SQLITE_ALLOW_ROWID_IN_VIEW. dbsqlfuzz 31b38eeb63a4e1562de665078f52b7b47a7543cf (check-in: 80c4223098 user: drh tags: trunk) | |
|
2024-03-21
| ||
| 22:12 | Fix a assert() that is incorrect, though harmless. Also add a test case. (check-in: 90537ce044 user: drh tags: branch-3.45) | |
| 22:08 | Fix a assert() that is incorrect, though harmless. Also add a test case. (check-in: 57b0c98460 user: drh tags: branch-3.44) | |
|
2024-03-20
| ||
| 16:29 | Fix test cases for rtree and fts5. No changes to code. (check-in: 633dca9074 user: drh tags: branch-3.44) | |
| 16:04 | Have rtree avoid keeping a blob handle open following an error. (check-in: 1303716a11 user: drh tags: branch-3.44) | |
| 15:26 | Following a ROLLBACK that reverts changes to an RTREE, any pending queries against that same RTREE abort with code SQLITE_ABORT_ROLLBACK. dbsqlfuzz de7d17b72d0e842352c998dd86a47b7d0f707be9. (check-in: b26e5a500e user: drh tags: branch-3.44) | |
| 12:19 | Back port various minor patches (check-in: a1a5c427c2 user: drh tags: branch-3.44) | |
| 11:36 | Automatically disable the DISTINCT optimization during query planning if the ORDER BY clause exceeds 63 terms. dbsqlfuzz afd1d61fc27d14938a0d78a50970fa1e9fbfee58. (check-in: e8d5caef26 user: drh tags: branch-3.44) | |
| 11:30 | Ignore COLLATE operators when determining whether the result of a subexpression should be shallow-copied or deep-copied. (check-in: dd58d1178f user: drh tags: branch-3.44) | |
| 11:25 | Fix a harmless compiler warning in the randomjson.c extension. (check-in: a4c9351234 user: drh tags: branch-3.44) | |
| 11:24 | If a term of an ORDER BY or GROUP BY contains an aggregate function or column, then it is not an alias that needs to be resolved, so don't try to. This fixes a harmless assertion found by dbsqlfuzz. (check-in: e7ba2af5a1 user: drh tags: branch-3.44) | |
| 11:04 | Fix the SQLITE_ALLOW_ROWID_IN_VIEW bug-compatibility option so that it works again. Add the SQLITE_CONFIG_ROWID_IN_VIEW sqlite3_config() value to optionally disable the bug-compatibility mode at start-time. Enable testing of SQLITE_ALLOW_ROWID_IN_VIEW. (check-in: acc08353e2 user: drh tags: branch-3.44) | |
| 10:45 | Fix the SQLITE_ALLOW_ROWID_IN_VIEW bug-compatibility option so that it works again. Add the SQLITE_CONFIG_ROWID_IN_VIEW sqlite3_config() value to optionally disable the bug-compatibility mode at start-time. Enable testing of SQLITE_ALLOW_ROWID_IN_VIEW. (check-in: b6802565df user: drh tags: trunk) | |
|
2024-03-19
| ||
| 10:58 | Fix a problem involving infinities int the Kahan-Babushka-Neumaier summation algorithm. (check-in: 8af5878138 user: drh tags: branch-3.45) | |
| 10:46 | Fix a problem involving infinities int the Kahan-Babushka-Neumaier summation algorithm. (check-in: 0984e5cd25 user: drh tags: branch-3.44) | |
| 10:41 | Adjustments to the test cases for the previous check-in to make them cross-platform Linux/Mac/Windows. Test changes only. No change to core code. (check-in: 0dddadbd5b user: drh tags: trunk) | |
| 10:16 | Fix another problem from [c63e26e705f5e967] involving infinities and the Kahan-Babushka-Neumaier summation algorithm. Problem reported by forum post 23b8688ef4. (check-in: 45d272ef38 user: drh tags: trunk) | |
|
2024-03-16
| ||
| 21:04 | Fix a assert() that is incorrect, though harmless. (Closed-Leaf check-in: 9ba3cff9d4 user: drh tags: enhanced-expr-is-const) | |
|
2024-03-08
| ||
| 14:16 | Silently ignore redundant ON CONFLICT clauses in an UPSERT. (check-in: e546d8c685 user: drh tags: branch-3.44) | |
| 14:01 | Silently ignore redundant ON CONFLICT clauses in an UPSERT. Only the first ON CONFLICT for each index is active. Do not issue an error, since that might break legacy queries. But ignore the redundant ON CONFLICT clauses to prevent problems such as described in forum post 919c6579c8. (check-in: d0ea6b6ba6 user: drh tags: trunk) | |
|
2024-02-25
| ||
| 21:30 | Make sure key comprisons are done correctly if the index key contains NaN values that have not been shifted into NULLs. That can only happen due to database corruption, but we need to deal with it nevertheless. (check-in: 7e4c743f9e user: drh tags: trunk) | |
|
2024-02-12
| ||
| 16:12 | Have rtree avoid keeping a blob handle open following an error. (check-in: 1cd5d4623f user: dan tags: trunk) | |
|
2024-02-11
| ||
| 22:56 | In the RTREE extension, allow the xBeginTransaction() entry point to be invoked multiple times without intervening calls to xEndTransaction(). (check-in: f023cb541b user: drh tags: trunk) | |
| 20:53 | If a term of an ORDER BY or GROUP BY contains an aggregate function or column, then it is not an alias that needs to be resolved, so don't try to. This fixes a harmless assertion found by dbsqlfuzz. This yet another problem that orginated at check-in [6e6b3729e0549de0]. (check-in: d4ec2a5d22 user: drh tags: trunk) | |
|
2024-02-03
| ||
| 19:19 | Following a ROLLBACK that reverts changes to an RTREE, any pending queries against that same RTREE abort with code SQLITE_ABORT_ROLLBACK. dbsqlfuzz de7d17b72d0e842352c998dd86a47b7d0f707be9. (check-in: af5c425114 user: drh tags: trunk) | |
|
2024-02-01
| ||
| 14:57 | In PRAGMA integrity_check, defer running xIntegrity on virtual tables until after all ordinary tables have been checked. (check-in: 8f4b1ceafe user: drh tags: trunk) | |
|
2024-01-28
| ||
| 17:39 | Automatically disable the DISTINCT optimization during query planning if the ORDER BY clause exceeds 63 terms. dbsqlfuzz afd1d61fc27d14938a0d78a50970fa1e9fbfee58. (check-in: d4c193f0b4 user: drh tags: trunk) | |
| 00:31 | Apply the same fix found in [99057383acc8f920] to descending scans. dbsqlfuzz afd1d61fc27d14938a0d78a50970fa1e9fbfee5. (check-in: e1d463c2d6 user: drh tags: trunk) | |
|
2024-01-23
| ||
| 16:21 | In os_unix.c and os_win.c, do not allow xFetch() to return a pointer to a page buffer that is right at the end of the mapped region - if the database is corrupted in a specific way such a page buffer might be overread by several bytes. (check-in: 198a1daae0 user: drh tags: branch-3.44) | |
| 16:09 | In os_unix.c and os_win.c, do not allow xFetch() to return a pointer to a page buffer that is right at the end of the mapped region - if the database is corrupted in a specific way such a page buffer might be overread by several bytes. (check-in: 2684feac3b user: dan tags: trunk) | |
|
2024-01-11
| ||
| 14:03 | In fts5, flush the contents of the in-memory hash table whenever the secure-delete option is toggled. This prevents spurious corruption reports under some circumstances. (check-in: ccf552319a user: dan tags: trunk) | |
|
2024-01-02
| ||
| 21:08 | Fix a problem in fts5 caused by a COMMIT involving fts5 data that immediately follows a ROLLBACK TO that does not. (check-in: 55c61f6a8d user: dan tags: trunk) | |
|
2023-12-24
| ||
| 11:31 | Avoid signed integer overflow during integrity_check of FTS5. (check-in: 5937df3b25 user: drh tags: trunk) | |
|
2023-12-22
| ||
| 15:42 | Update #ifdef checks in pager.c and util.c to account for [0462a2612d1fc1d0] to resolve the build problem reported in forum post 9819032aac. (check-in: 7374c2342e user: stephan tags: branch-3.44) | |
| 15:41 | Update #ifdef checks in pager.c and util.c to account for [0462a2612d1fc1d0] to resolve the build problem reported in forum post 9819032aac. (check-in: 0f22d809a1 user: stephan tags: trunk) | |