dan
|
cb928efd50
|
Disable the seekscan optimization for IN(...) expressions when the RHS is a SELECT that returns more than one column. This was previously only possible if the sqlite_stat1 table was populated with inconsistent information, and was malfunctioning in some circumstances. Report [bugs:/info/2026-08-13T08:45:47 | 2026-08-13T08:45:47Z].
FossilOrigin-Name: 9544d46a6d51dbc12057e33ec1a635cd2cd48101c46d4b92171b56b70ea23f53
|
2026-08-13 18:37:39 +00:00 |
|
dan
|
939165ae51
|
Ensure that if a seek-scan is used for an expression like (x, y) IN (SELECT a, b FROM ...) then the SELECT delivers rows in order of (a, b).
FossilOrigin-Name: c9661d928e9002771b586f09e7b6bad15ffba4466a52a7ca441a661ea2ffdbec
|
2026-08-13 15:16:49 +00:00 |
|
dan
|
e1afa2bd24
|
Avoid having OP_SeekScan jump over an OP_IdxGT or OP_IdxGE that follows the OP_SeekGE opcode. Fix for [b50528af4468237c].
FossilOrigin-Name: c9c4f287652933eb6262a3419efe7e7288f55d3db7e2ac032eeae025f665d306
|
2023-03-29 21:58:06 +00:00 |
|
dan
|
73c586bcbf
|
Fix a problem causing the seek-scan optimization to skip over valid rows that could occur when it is used with expressions of the form (a IN (?,?..) AND b >= ?). dbsqlfuzz ab1db6dc0efb04cba1cd3431ee6da4894fdc4520.
FossilOrigin-Name: 63d9efe277759d4daa29794846b60c6f55491496618f423f61468df72d0a4633
|
2022-10-07 18:57:15 +00:00 |
|