]> git.ipfire.org Git - thirdparty/sqlite.git/commit
For the MULTI-INDEX-OR optimization, when pushing down WHERE clause terms from
authordrh <>
Fri, 4 Feb 2022 13:05:29 +0000 (13:05 +0000)
committerdrh <>
Fri, 4 Feb 2022 13:05:29 +0000 (13:05 +0000)
commit02e3e041343e6ac950771bb5ef813f1876f5036b
tree3cdfecba52004f51df6e964cf135252142ce9079
parent7f1c11194825583ffee08ef1a57e6e0d0082c33b
For the MULTI-INDEX-OR optimization, when pushing down WHERE clause terms from
the main query into the various OR-term subqueries, do not push down slices
of a vector comparison, since the right-hand operand of the comparison might
have only been initialized in a different OR branch that was not taken.
dbsqlfuzz 80a9fade844b4fb43564efc972bcb2c68270f5d1.

FossilOrigin-Name: 9f67ad00cd38b7c5ec6d14b379e1a611777bbdf6901d843a80712ba7d94d6d33
manifest
manifest.uuid
src/whereInt.h
src/wherecode.c
src/whereexpr.c
test/rowvalue.test