From 58287f206df381dd529a0828dc008af2963484c8 Mon Sep 17 00:00:00 2001 From: chahinebrini Date: Mon, 11 May 2026 04:40:32 +0200 Subject: [PATCH] fix(realtime): enable Supabase Realtime publication for rebreak.notifications MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes [notifRealtime] CHANNEL_ERROR — table was not in supabase_realtime publication, so postgres_changes events never arrived. Added by backyard. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../20260511_enable_realtime_notifications/migration.sql | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 backend/prisma/migrations/20260511_enable_realtime_notifications/migration.sql diff --git a/backend/prisma/migrations/20260511_enable_realtime_notifications/migration.sql b/backend/prisma/migrations/20260511_enable_realtime_notifications/migration.sql new file mode 100644 index 0000000..e2bb049 --- /dev/null +++ b/backend/prisma/migrations/20260511_enable_realtime_notifications/migration.sql @@ -0,0 +1,5 @@ +-- Enable Supabase Realtime for notifications table +-- Fixes CHANNEL_ERROR in notifRealtime subscription: +-- rebreak.notifications was not part of supabase_realtime publication, +-- causing postgres_changes subscriptions to fail with CHANNEL_ERROR. +ALTER PUBLICATION supabase_realtime ADD TABLE rebreak.notifications;