From d62eadd630548cf5ebfc274603dfd557a6142ad2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Filipe=20Caba=C3=A7o?= Date: Thu, 22 Feb 2024 15:57:37 +0000 Subject: [PATCH] fix: Add limitation to Postgres Changes docs regarding Delete events ignoring filtering (#21412) --- apps/docs/content/guides/realtime/postgres-changes.mdx | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/apps/docs/content/guides/realtime/postgres-changes.mdx b/apps/docs/content/guides/realtime/postgres-changes.mdx index b267316bb2a..252e79330e5 100644 --- a/apps/docs/content/guides/realtime/postgres-changes.mdx +++ b/apps/docs/content/guides/realtime/postgres-changes.mdx @@ -86,7 +86,7 @@ In this example we'll set up a database table, secure it with Row Level Security - + Go to your project's [Replication settings](https://supabase.com/dashboard/project/_/database/replication), and under `supabase_realtime`, toggle on the tables you want to listen to. @@ -96,7 +96,7 @@ In this example we'll set up a database table, secure it with Row Level Security - + Install the Supabase JavaScript client. @@ -114,7 +114,7 @@ In this example we'll set up a database table, secure it with Row Level Security - + This client will be used to listen to Postgres changes. @@ -1347,6 +1347,10 @@ myChannel.updateAuth("fresh-token") ## Limitations +### Delete events are not filterable + +You can't filter Delete events when tracking Postgres Changes. This limitation is due to the way changes are pulled from Postgres. + ### Spaces in table names Realtime currently does not work when table names contain spaces.