Skip to content

Added Supabase Streaming Filter Limitation #209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 22, 2024
Merged

Added Supabase Streaming Filter Limitation #209

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c4a305d
Added supabase streaming filter limitation
pinkeshmars Nov 21, 2024
b6efa67
Apply suggestions from code review
pinkeshmars Nov 22, 2024
78a2402
address review comments
pinkeshmars Nov 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/resources/control-flow/backend-logic/backend-query/query-collection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,16 @@ The instructions to query a Supabase table are almost the same, except that for
</iframe>
</div>

:::warning[Limitations of Supabase Streaming with Filters]
When using Supabase query with real-time updates enabled, you have the following limitations:

1. **Only One Filter is Supported:** Supabase streaming supports only a single filter. Combining multiple filters (e.g., `isActive = true AND city = 'Los Angeles'`) is not allowed.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be a bullet list instead of ordered since this is not a ordered list right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, updated.

2. **Delete Events Are Not Filterable:** Streaming queries do not detect deletions, even if the deleted row matches the filter condition. For example, If you are streaming rows with the filter `city = 'New York’` and a row is deleted, the query output will not reflect the deletion.
3. **Updates That Remove Rows from Filteres Are Not Tracked:** Changes that make a row no longer match the filter condition (e.g., updating `isActive` from `true` to `false`) will not trigger an update in the query output.

For more details, refer the limitations [**here**](https://supabase.com/docs/guides/realtime/postgres-changes?queryGroups=language&language=js&queryGroups=database-method&database-method=dashboard#delete-events-are-not-filterable).
:::

## Using Query Data

The documents retrieved from the backend query can be used to set the record values to the widgets
Expand Down