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
{{ message }}
Repository navigation
[FEATURE] Return SQL NULL from json_equal and aws_policy_equal for NULL arguments #914
Both current implementations still reject SQL NULL arguments. This makes optional properties fail a whole query and requires COALESCE guards in stackql-deploy statechecks.
Acceptance:
json_equal(NULL, value), json_equal(value, NULL) and json_equal(NULL, NULL) return SQL NULL.
aws_policy_equal has the same NULL propagation, including NULL versus NULL.
SQL NULL remains distinct from the JSON text 'null'.
Preserve non-NULL comparison semantics, including the documented aws_policy_equal byte-identical shortcut. Do not broaden this change into unrelated JSON parsing behavior.
Keep malformed non-NULL input errors on paths that currently parse and reject it.
Update the four NULL-side golden vectors, add both-NULL cases, and update DIVERGENCES.md and function documentation in the current StackQL sqlfuncs package.
Add a local SQL-engine regression showing a NULL optional property does not abort all rows and that WHERE comparison = 1 excludes the NULL result as expected.
No live cloud credentials are needed for regression tests.
The original issue contains the motivating awscc S3 and stackql-deploy examples. This is host SQL-engine work and has no new omnisdk prerequisite.
Closing as resolved by #933, with the additional OmniSDK WHERE-evaluation fix and end-to-end coverage in #934. The corresponding OmniSDK fix was merged in stackql-labs/omnisdk#60.
Activity
fix(sqlfuncs): return SQL NULL from json_equal and aws_policy_equal f…
jeffreyaven commentedon Nov 18, 2026
Closing as resolved by #933, with the additional OmniSDK WHERE-evaluation fix and end-to-end coverage in #934. The corresponding OmniSDK fix was merged in stackql-labs/omnisdk#60.