Open acupofjose opened 1 year ago
@acupofjose thanks for reporting! we're aware of this issue and we're tracking it here: https://github.com/supabase/walrus/issues/53
almost a year later, no news / update about this?
If this is such a hard to fix issue, I would like to say it should be MANDATORY to mention that in the doc for the delete event subscriber
I just realized that issue the hard way with a live product with a huge nasty impact :/
Sorry for the lack of updates. Unfortunately this is a limitation of the underlying approach we're using https://github.com/supabase/walrus/issues/53
We are changing some elements of our implementation and this will be a concern we will take into consideration.
Bug report
Describe the bug
When subscribed to
postgres_changes
and specifying a row level filter, websocket inspector shows that rows outside of the provided filter are being sent to the client.To Reproduce
Given the following table:
And the following code:
In Supabase Inspector:
Console Behavior:
Websocket Behavior:
Expected behavior
Neither websocket nor console should produce logs for rows outside of the filter.
System information
Additional context
In reference to: supabase-community/realtime-csharp#27