Strategy to handle wrong migrations locally
How would I go about when I did a mistake in my schema locally when developing and migrated my local database. Do I need to always drop everything and run migrations from the start?..
I would love something where I can just push to the local database after I fixed my latest migration.
e.g.
drizzle-kit regenerate -> Generates the last migration file again containing my fixed schema and then drizzle-kit push but in a manner that it also correctly updates the migration table so I can proceed with additional migrations later on..
The way I see it I have to drop my database schema as well as the drizzle schema in postgres locally to be able to run the migrations in order again. Right?0 Replies