You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(sql): canonicalize WHERE predicate operand order before planning
Normalize comparisons to column-first (`literal = col` -> `col = literal`,
flipping the operator) at the shared WHERE-to-filter conversion point used
by both regular SELECT/DELETE planning and recursive CTE join links. Without
this, a literal-first predicate bypassed the primary-key point-get rewrite
and fell back to a sequential scan, letting the same logical predicate route
to two different physical operators that could disagree after crash
recovery or DROP/recreate cycles.
Add regression coverage for the affected scenarios: point-get plan parity
for both operand orders, PK index vs. scan agreement after kill -9 and
after DROP/recreate on document_strict collections, and IS NULL polarity
on filtered reads/deletes. Reformat an unrelated assertion in the native
transaction visibility test to satisfy line-length formatting.
0 commit comments