Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 most recent check-ins that include changes to files matching 'src/*'
|
2024-04-25
| ||
| 23:26 | Improvement to the way that affinity is determined for columns of a compound subquery. The affinity is the affinity of the left-most arm of the compound subquery that has an affinity other than NONE, adjusted to accommodate the data types coming out of the other arms. (Leaf check-in: e6df846f36 user: drh tags: trunk) | |
| 17:52 | Further improvements to the computation of affinity for compound subqueries: make sure that the selected affinity is compatible with a literal values in arms to the left of the arm that is used to determine affinity. (Closed-Leaf check-in: bbdf22e3d9 user: drh tags: compound-subquery-affinity) | |
| 16:55 | Back out the previous change on this branch. In its place: Determine the affinity of a subquery by the left-most arm of the subquery that has an affinity other than NONE. In other words, scan from left to right looking for an arm of the compound subquery with an affinity of BLOB, TEXT, INTEGER, or REAL and pick the first one found. Or stay with NONE if no arm has a defined affinity. Test cases added. (check-in: b8ec8511b1 user: drh tags: compound-subquery-affinity) | |
|
2024-04-24
| ||
| 19:49 | An experimental minor tweak to the way affinities are computed for compound subqueries, when the actual affinity is ambiguous. (check-in: 779723ad79 user: drh tags: compound-subquery-affinity) | |
| 16:36 | If a RETURNING clause contains a subquery that references the table that is being updated in the statement that includes the RETURNING clause, then mark the subquery as correlated so that it is recomputed for each result and not just computed once and reused. See [forum:/forumpost/2c83569ce8945d39|forum post 2c83569ce8945d39]. (check-in: 9ea6bcc8fd user: drh tags: trunk) | |
| 14:18 | Fix a case where a corrupt stat4 record could go unrecognized due to integer overflow. (check-in: 240a4a48b2 user: dan tags: trunk) | |
| 11:51 | Add comments linking the assert() added in [cef4d9e3ba586735] to the places where the precondition that the assert() tests are actually required. (check-in: 6f0e7e1952 user: drh tags: trunk) | |
| 11:40 | Avoid slowdown when exprNodeIsConstant() is called on deeply nested SQL functions. (check-in: 1c0b034545 user: dan tags: trunk) | |
| 11:21 | Ensure that temporary SrcItem objects created by trigger processing have either SrcItem.zName or SrcItem.pSelect defined. Every SrcItem should have one or the other. (check-in: cef4d9e3ba user: drh tags: trunk) | |
|
2024-04-23
| ||
| 12:02 | Fix a problem with vector IN operators used with an index where the affinities and collations for the various vector terms are different. (check-in: 86e8c782e7 user: drh tags: trunk) | |
| 11:56 | Fix an uninitialized variable problem in the new code on this branch. (Closed-Leaf check-in: 85625b3871 user: dan tags: vector-in-fix) | |
|
2024-04-22
| ||
| 13:31 | Extra robustness in the code that causes cursors to return NULL when they are participating in an OUTER JOIN. (check-in: 672c2869ef user: drh tags: trunk) | |
| 00:42 | Continuation of the fix at [8c0f69e0e4ae0a44]: If a viaCoroutine FROM clause term is participating in a RIGHT or FULL JOIN, we have to create an always-NULL pseudo-cursor for that term when processing the RIGHT join. dbsqlfuzz 6fd1ff3a64bef4a6c092e8d757548e95698b0df5. (check-in: e1040e51eb user: drh tags: trunk) | |
|
2024-04-21
| ||
| 23:35 | Fix an indentation problem in debugging routine sqlite3ShowSrcList(). No changes to production code. (check-in: 5560df2726 user: drh tags: trunk) | |
|
2024-04-20
| ||
| 19:19 | Slight performance improvement for the new code on this branch. (check-in: 500c67f134 user: dan tags: vector-in-fix) | |
| 15:14 | Fix a problem where an expression like (a, b) IN (SELECT ...) might not use an index on (a, b) if the affinities and collation sequences of "a" and "b" are not identical. (check-in: 4d870fd8b5 user: dan tags: vector-in-fix) | |
|
2024-04-18
| ||
| 16:11 | Correct handling of OUTER JOIN when on or the other operand is a subquery implemented using the VALUES-as-coroutine optimization. dbsqlfuzz bde3bf80aedf25afa56e2997a0545a314765d3f8. (check-in: 8c0f69e0e4 user: drh tags: trunk) | |
|
2024-04-15
| ||
| 20:43 | The first assert() added in [0ebc65481f4a3e79] is not necessarily true in a corrupt database file. So add a term to make it true. (check-in: 6b21cccdee user: drh tags: trunk) | |
| 14:59 | Merge version 3.45.3 patches into the reuse-schema-3.45 sub-branch. (Leaf check-in: a1ff415341 user: drh tags: reuse-schema-3.45) | |
| 14:45 | Merge all of the latest trunk enhancements into the bedrock branch. (Leaf check-in: 16dac180b5 user: drh tags: bedrock) | |
| 14:39 | Merge the latest trunk enhancements into the wal2 branch. (Leaf check-in: 4a72acbc4b user: drh tags: wal2) | |
| 14:36 | Merge the latest trunk enhancements into the begin-concurrent branch. (Leaf check-in: eedf6bed2a user: drh tags: begin-concurrent) | |
| 14:29 | Merge from wrong branch. Bedrock should be updated from wal2, not from trunk. (Closed-Leaf check-in: 4c23cad98d user: drh tags: mistake) | |
| 14:21 | Merge all 3.45.3 changes into the wal2-3.45 branch. (Leaf check-in: 2ccc018546 user: drh tags: wal2-3.45) | |
| 14:18 | Merge all 3.45.3 changes into the begin-concurrent-3.45 subbranch. (Leaf check-in: 3dda82e001 user: drh tags: begin-concurrent-3.45) | |
|
2024-04-12
| ||
| 15:15 | Mark the BTree cell overflow cache as invalid whenever the rowid goes invalid. (Leaf check-in: 0ec6669c84 user: drh tags: branch-3.44) | |
| 15:06 | Mark the BTree cell overflow cache as invalid whenever the rowid goes invalid. (check-in: 5266bb6dc9 user: drh tags: branch-3.45) | |
| 15:02 | Fixes and new tests logic to ensure that the btree overflow page cache is only used when it is consistent. This resolves the malfunction observed in [forum:/forumpost/284955a3cd454a15|forum post 284955a3cd454a15]. (check-in: 5dede50d9e user: drh tags: trunk) | |
| 13:05 | Add assert() statements to help verify the overflow page cache. (Closed-Leaf check-in: 0ebc65481f user: drh tags: btree-ovfl-cache) | |
| 12:32 | New assert() statements to verify the correctness of the BTCF_AtLast flag on btree cursors. (check-in: 4efecd6167 user: drh tags: btree-ovfl-cache) | |
| 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-11
| ||
| 19:09 | Fix handling of the SQLITE_OMIT_WAL check in one place. Resolves [forum:87cc13302de160eb|forum post 87cc13302de160eb]. (check-in: ce86d30d91 user: stephan tags: branch-3.45) | |
| 19:08 | Fix handling of the SQLITE_OMIT_WAL check in one place. Resolves [forum:87cc13302de160eb|forum post 87cc13302de160eb]. (check-in: 5dae6e6df4 user: stephan tags: trunk) | |
|
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) | |
| 14:07 | Ignore CHECK constraints when qualifying the xfer optimization while running VACUUM. (check-in: bb6f990809 user: drh tags: branch-3.45) | |
| 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:/forumpost/3ec177d68fe7fa2c|forum post 3ec177d68fe7fa2c]. (check-in: a6e26e7788 user: drh tags: trunk) | |
|
2024-04-08
| ||
| 12:02 | Merge the latest trunk enhancements, and especially the enhancement to the WHERE-clause push-down optimization, into the bedrock branch. (check-in: 0f93b52c77 user: drh tags: bedrock) | |
| 11:57 | Merge the latest trunk enhancements into the wal2 branch. (check-in: 59ccea7db7 user: drh tags: wal2) | |
| 11:50 | Enhance the WHERE-clause push-down optimization so that it is able to push down WHERE clause terms that contain uncorrelated subqueries. (check-in: 69ec714b2d user: drh tags: trunk) | |
|
2024-04-07
| ||
| 18:55 | Merge trunk testing enhancements into the pushdown-subquery branch. (check-in: 287ff24b26 user: drh tags: pushdown-subquery) | |
| 18:23 | If SQLITE_ALLOW_ROWID_IN_VIEW is set to 2, then all rowids for views return a value of NULL. (check-in: 0a53dde214 user: drh tags: trunk) | |
| 10:30 | Merge trunk enhancements into the pushdown-subquery branch. (check-in: 27865e316f user: drh tags: pushdown-subquery) | |
| 10:27 | Add comments to note the name abiguity between the MySQL push-down optimization and the WHERE-clause push-down optimization. (check-in: 3d5fb1ec7a user: drh tags: trunk) | |
|
2024-04-06
| ||
| 23:09 | Add comments to note the name abiguity between the MySQL push-down optimization and the WHERE-clause push-down optimization. (Leaf check-in: 681dfe2dd6 user: drh tags: wrong-branch) | |
| 18:30 | Do not allow changes to sqlite3ExprIsTableConstant() that support pushdown of subqueries interfere with the hash-join logic. (check-in: 8682931f9c user: drh tags: pushdown-subquery) | |
| 12:19 | Generalize pushdown to allow any uncorrelated subquery to be pushed down. (check-in: 87c45fb0d5 user: drh tags: pushdown-subquery) | |
| 11:59 | Generalize the pushdown of IN right-hand sides to cover more SELECTs. (Closed-Leaf check-in: 4120bc740a user: drh tags: pushdown-IN-table) | |
|
2024-04-05
| ||
| 20:01 | Experimental enhancement in which expressions of the form "expr IN table" can be pushed down into subexpressions. (check-in: 2cbd7838fd user: drh tags: pushdown-IN-table) | |
| 15:04 | Merge all recent trunk enhancements into the reuse-schema branch. (Leaf check-in: e556f3d381 user: drh tags: reuse-schema) | |
| 14:54 | Merge the latest trunk enhancements into the bedrock branch. (check-in: 7a2a64b646 user: drh tags: bedrock) | |