Enable jsonGroupArray on optional columns
#221
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We can already call
jsonGroupArray()on columns sourced from a regular join, because the column is guaranteed to exist:Left joins were different: the only helper that understood optional tables worked at the table level, so if you wanted just one column you had to build the
CASE … FILTER …scaffolding yourself.This PR adds the missing column-level overload for optional tables, so the same syntax now works when the join may return
NULLrows:Tests cover the new overload alongside the existing distinct/order/filter behavior.