Pricing
Docs
Blog
Alex Jones is seeking advice on how to configure separate migration histories for two backend services using the same Supabase instance. Each service has its own database schema, and Alex wants to avoid conflicts in migration version values by using custom schemas or tables for migration history.
Service A and service B are separate backend node services. The run separately. They have their own database schema, with distinct set of tables. They share a supabase instance.