Drizzle-kit generates migration files which stay in order based on its naming pattern
<xxxx_name.sql>
<xxxx_name.sql>
Supabase, e.g. when using
supabase db pull
supabase db pull
(to ensure production/local development setup is in sync) creates migration files naming them like
<timestamp>_name.sql
<timestamp>_name.sql
This leaves us with a local list like:
0005_nice.sql0006_roy.sql0007_stiff.sql (was generated after the following remote_schema)20240117168594_remote_schema.sql
0005_nice.sql0006_roy.sql0007_stiff.sql (was generated after the following remote_schema)20240117168594_remote_schema.sql
This can cause problems when migrating because the order isn't correct. Is there a common approach to that, or how to make drizzle and supabase work in harmony?