Skip to content

fix: empty array on select yields error#82

Merged
filipecabaco merged 1 commit into
masterfrom
fix/select-empty-handling-real-843
Jun 13, 2026
Merged

fix: empty array on select yields error#82
filipecabaco merged 1 commit into
masterfrom
fix/select-empty-handling-real-843

Conversation

@filipecabaco

Copy link
Copy Markdown
Member

What kind of change does this PR introduce?

Fixes the behaviour where empty array would be handled as a NULL meaning the user could be mislead into thinking that they were properly filtering data when they weren't.

The behaviour now is:

  • NULL returns all columns
  • {} errors out so we can inform the user

https://linear.app/supabase/issue/REAL-843/treat-empty-pg-changes-select-as-an-error

Fixes the behaviour where empty array would be handled as a NULL meaning the user could be mislead into thinking that they were properly filtering data when they weren't.

The behaviour now is:
* `NULL` returns all columns
* `{}` errors out so we can inform the user

https://linear.app/supabase/issue/REAL-843/treat-empty-pg-changes-select-as-an-error
@filipecabaco filipecabaco force-pushed the fix/select-empty-handling-real-843 branch from 5f357f7 to 1f8285f Compare June 3, 2026 10:04
@filipecabaco filipecabaco merged commit 6150c6d into master Jun 13, 2026
3 checks passed
@filipecabaco filipecabaco deleted the fix/select-empty-handling-real-843 branch June 13, 2026 09:10
filipecabaco added a commit that referenced this pull request Jun 13, 2026
Fixes the behaviour where empty array would be handled as a NULL meaning the user could be mislead into thinking that they were properly filtering data when they weren't.

The behaviour now is:
* `NULL` returns all columns
* `{}` errors out so we can inform the user

https://linear.app/supabase/issue/REAL-843/treat-empty-pg-changes-select-as-an-error
filipecabaco added a commit that referenced this pull request Jun 13, 2026
Fixes the behaviour where empty array would be handled as a NULL meaning the user could be mislead into thinking that they were properly filtering data when they weren't.

The behaviour now is:
* `NULL` returns all columns
* `{}` errors out so we can inform the user

https://linear.app/supabase/issue/REAL-843/treat-empty-pg-changes-select-as-an-error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants