-
-
Notifications
You must be signed in to change notification settings - Fork 54
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.
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
Realtime RLS Broadcasts Errors #50
Labels
Comments
3 tasks
Closed
Woah it's been a while - I'm going to move this to the realtime-py repo so this can be taken into consideration for the |
This issue is stale because it has been open for 365 days with no activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Realtime RLS will be broadcasting database changes with
errors
so that clients can capture what went wrong when listening to database changes.Please see here for the current error states: https://github.com/supabase/walrus/tree/generic_claims#error-states.
Realtime RLS will broadcast
errors
as eithernull
(no errors) or an array of strings (at least one error present).Here are two example Realtime RLS JSON payloads with errors:
Notice:
columns
will always be an array but can be emptycommit_timestamp
will either be a string or nullold_record
/record
will always be an object but can be emptyThe text was updated successfully, but these errors were encountered: