Hello @amerryma,

Can you please give us the full error log and filters?

Hello @amerryma, thanks for the issue.

We discussed with the core team and decided not to add filters to the subscription since complex and relation-based filters might not work as expected in Supabase Realtime.

After removing filters, any change in the posts table will trigger the posts query again, ignoring the filters. We believe this approach is correct. What do you think?

My workaround for now was picking one filter that did 90% of the server side filtering then did the rest on the client side. So you're saying that you will remove the filtering altogether?

My workaround for now was picking one filter that did 90% of the server side filtering then did the rest on the client side. So you're saying that you will remove the filtering altogether?

I was wrong. In this use case, the filters must work. We'll investigate this issue and see what we can do.

We're currently considering showing a warning when multiple filters are used and allowing users to override the liveProvider's filters using the meta.realtimeFilters prop.

I've also bumped an issue directly inside supabase/realtime to see what the status is there.

Until there are any updates in the supabase side, we should have this working without an error. Picking the first filter will work for many cases but it must be configurable (like meta.realtimeFilter). When working with multiple filters, realtime subscription may log a warning (like @alicanerdurmaz stated) about the current issue and say that only the first filter is picked etc.

If Supabase starts supporting multiple filters in the future, we can just deprecate the realtimeFilter and revert back to the current state 🤔

Maybe @alicanerdurmaz can provide a detailed description for the implementation we want and it will be a guide for anyone interested in working on this issue 🚀 🚀

@amerryma @aliemir

I think it would be good to warn if there is more than one filter and allow the user to override the filter if needed.

1. Warning for Multiple Filters
   If more than one filter is used, show a warning to user. If meta.realtimeFilter is available, use that instead of params.filter.
   Code Link

2. Fix Filter Syntax Errors
   There are some syntax errors in the generated filter. These need to be fixed and tested.

3. Skip Unsupported Filters
   Some filters that work in Refine don't work with Supabase Realtime. Ignore those filters when generating for Realtime.
   Supabase Realtime Docs

Hey!
I want to work on this issue.

Hey! I'd like to work on this issue.

Plan:

• If multiple filters are passed, warn the dev
• Use only the first filter by default
• Allow override via meta.realtimeFilter

Does this sound good?

Hi! I’m new to open source and I’d love to contribute to this issue. Can I work on this? Any additional context or guidance would be appreciated 🙌

Hello @sajalshh,

Thanks a lot for your interest, we’d love to have your contribution!
Feel free to pick this up. If you have any questions while working on it, don’t hesitate to ask.

Please also check our contribution guide: https://refine.dev/docs/guides-concepts/contributing/

Looking forward to your PR! 🙌

Is this ticket still open?

Is it still open?

@OmkarBansod02 seemed to have worked a lot on this one. Can you tell us what is missing on his proposition so that we can iterate on them instead of redoing all from scratch ?

still up for grabs??
would love to contribute here!

Is it still open, if open I would love to contribute