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
test(v3): pin ore_cllw ROW(NULL) RAISE divergence from eql_v2
eql_v3.compare_ore_cllw_term guards with `a::text IS NULL` (true only for a
genuine SQL-NULL composite), so a hand-crafted ROW(NULL) falls through to the
`a.bytes IS NULL` check and RAISES the extractor-invariant violation. eql_v2
guards with `a IS NULL`, which — for a single-field composite — is also true
for ROW(NULL), so v2 silently returns NULL and its RAISE branch is unreachable.
No committed test exercised this divergence: both the existing v3 and v2 tests
only cover the shared SQL-NULL -> RETURN NULL path. Add
comparator_raises_on_row_null_composite to validate v3 raises on ROW(NULL), and
clarify the sibling NULL-return test's comment to make the divergence explicit.
0 commit comments