]> git.ipfire.org Git - thirdparty/sqlite.git/commit
In the LIKE optimization, do not analyze the new virtual WHERE clause terms
authordrh <>
Mon, 13 Feb 2023 12:46:22 +0000 (12:46 +0000)
committerdrh <>
Mon, 13 Feb 2023 12:46:22 +0000 (12:46 +0000)
commit9e463e878db0ec610ec3b14d30b0bcdf5bd053ba
tree792d4b80ae1b5f60beb68bf242f1abe329c40ef8
parent0c55b5fd1ccab39a16fe0d0453c6882a83d42304
In the LIKE optimization, do not analyze the new virtual WHERE clause terms
until both have been added, since they are expected to be consecutive and
the analysis might add complementary terms.
This fixes a problem caused by [44200596aa943963] and discovered by dbsqlfuzz
and recorded as case 7e3b5983727d843b910b2d9ab556e4afcd777cfb.

FossilOrigin-Name: d35de3ad3fac6b30d3f266cbe4b1e9923eb31a1eff4a869205bbc3ba122eeec5
manifest
manifest.uuid
src/whereexpr.c