Merge pull request #404 from YuraPetrovskyi/migration-problem

403/fix deployment failure due to migration desynchronization

Author: OlenaReukova

Diff for: supabase/migrations/20241128133000_schema_v2_start.sql renamed to supabase/migrations/20250207173330_remote_schema.sql

@@ -14,12 +14,8 @@ CREATE SCHEMA IF NOT EXISTS "Test";
 
 ALTER SCHEMA "Test" OWNER TO "postgres";
 
-CREATE EXTENSION IF NOT EXISTS "pg_net" WITH SCHEMA "extensions";
-
 CREATE EXTENSION IF NOT EXISTS "pgsodium" WITH SCHEMA "pgsodium";
 
-COMMENT ON SCHEMA "public" IS 'standard public schema';
-
 CREATE SCHEMA IF NOT EXISTS "test";
 
 ALTER SCHEMA "test" OWNER TO "postgres";
@@ -453,6 +449,10 @@ CREATE POLICY "Enable read access for all users" ON "public"."user_conversations
 
 ALTER PUBLICATION "supabase_realtime" OWNER TO "postgres";
 
+CREATE PUBLICATION "supabase_realtime_messages_publication" WITH (publish = 'insert, update, delete, truncate');
+
+-- ALTER PUBLICATION "supabase_realtime_messages_publication" OWNER TO "supabase_admin";
+
 ALTER PUBLICATION "supabase_realtime" ADD TABLE ONLY "public"."conversations";
 
 ALTER PUBLICATION "supabase_realtime" ADD TABLE ONLY "public"."messages";