summaryrefslogtreecommitdiff
path: root/tests/basic
diff options
context:
space:
mode:
authorSimon Charette <charette.s@gmail.com>2025-07-05 21:19:05 -0400
committerJacob Walls <jacobtylerwalls@gmail.com>2026-06-03 16:57:18 -0400
commit4bbc27c8686f10f9556cef02dbfa9f5157fbcf56 (patch)
tree61b13b5867e057caeb41102938a4d692874a7f87 /tests/basic
parentb5d9dbdf2bba8df4c85cd0db308b3a467d763d02 (diff)
Fixed #36492 -- Restored exact boolean lookup against literals on SQLite.
Performance regression in 37e6c5b on SQLite. Just like MySQL, and presumably Oracle, which don't have a native boolean type and incidently store booleans in integer columns, indices on such columns cannot be used when explicit boolean literal equalities are omitted. Adapt the logic introduced by refs #32691 for MySQL to be used for all backends that don't support native boolean fields instead of special casing MySQL, SQLite, and Oracle in their own special way. Note that review of this work surfaced that SQLite's query planner also cannot make use of indices when dealing with expressions of form WHERE NOT (indexed_bool_field = false) but that's a long standing problem unrelated to the restorative work performed in this patch. Thanks Klaas van Schelven for the report.
Diffstat (limited to 'tests/basic')
0 files changed, 0 insertions, 0 deletions