Supabase Realtime Postgres Changes doesn't trigger on "lost" data

I have a table named

rides

rides

that contain a column named

pro_id

pro_id

which is a foreign key but not really relevant.

When using Supabase channel on

postgres_changes

postgres_changes

with a filter on

pro_id

pro_id

like so :

                .channel('rides-changes')
                .on(
                    'postgres_changes',
                    {
                        event: '*',
                        schema: 'public',
                        table: 'rides',
                        filter: `pro_id=eq.${id}`
                    },
                    payload => {
                     //Do Something
                    }
                )

                .channel('rides-changes')
                .on(
                    'postgres_changes',
                    {
                        event: '*',
                        schema: 'public',
                        table: 'rides',
                        filter: `pro_id=eq.${id}`
                    },
                    payload => {
                     //Do Something
                    }
                )

It doesn't trigger when the

pro_id

pro_id

of a row is changing to an other

id

id

Basically a row that was "linked" to a user now is owned by an other user.

I understand that the problem is the filter that react only on changes on row that match the filter. But how do you do to react on change that impact directly the filter ?

Thank you for your help.

Supabase Realtime Postgres Changes doesn't trigger on "lost" data

I have a table named

rides

rides

that contain a column named

pro_id

pro_id

which is a foreign key but not really relevant.

When using Supabase channel on

postgres_changes

postgres_changes

with a filter on

pro_id

pro_id

like so :

                .channel('rides-changes')
                .on(
                    'postgres_changes',
                    {
                        event: '*',
                        schema: 'public',
                        table: 'rides',
                        filter: `pro_id=eq.${id}`
                    },
                    payload => {
                     //Do Something
                    }
                )

                .channel('rides-changes')
                .on(
                    'postgres_changes',
                    {
                        event: '*',
                        schema: 'public',
                        table: 'rides',
                        filter: `pro_id=eq.${id}`
                    },
                    payload => {
                     //Do Something
                    }
                )

It doesn't trigger when the

pro_id

pro_id

of a row is changing to an other

id

id

Supabase Realtime Postgres Changes doesn't trigger on "lost" data

Similar Threads

Supabase Realtime Postgres Changes doesn't trigger on "lost" data

Similar Threads

Similar Threads

Similar Threads