JohnBra
JohnBra
@sweatybridge as mentioned in the issue #2784 there are a few different options to implement this. I have opted for a simple solution where repeatable migrations are treated like a...
I guess I should also add the repeatable migrations to the `supabase db reset` and add tests in `supabase migration squash`.
@sweatybridge that should be everything now. I wasn't aware the seed files are versioned as well. I think it would be good to version repeatable migrations, too if possible. Does...
> > I think it would be good to version repeatable migrations, too if possible. > > What's the use case for tracking repeatable migrations? My understanding is that repeatable...
> A few more complications that need answers > > 1. What should happen when user runs `supabase db reset --version `? Some repeatable migrations might depend on new schemas...
@sweatybridge the current implementation should satisfy most requirements. I changed it so repeatable migrations are now treated as versioned migrations, with their name as version. Leaving it as an empty...
@sweatybridge any updates?
Hey @sweatybridge, just checking in if this still relevant. Happy to close if not.