DB Migration issues when syncing Prod and Dev DB
Prisma✅SolvedBackend
To keep my local dev DB sane I created a shell script to dump my prod (deployed) DB to a local file, drop my local database and restore the dump locally.
When I then run wasp clean and try to start the server, it prompts me that the migrations do not match and I need to wipe the Database. After that I rerun my sync script to have some Data which works fine, but the next time I need to run wasp clean, I need to repeat the process. It's not a Shopstopper nor Dealbreaker. Just wanted to point it out and ask how you detect the migration changes?
I tried to prevent this by excluding the migrations table from the remote dump and do a local dump first and after dropping the local db and restoring the remote dump I also restore the local migrations table hoping to prevent the issue, which sadly did not work.
I hope I managed to describe the "issue" well enough.
Do you Guys have any Insights why this might be happening or how to prevent it?
When I then run wasp clean and try to start the server, it prompts me that the migrations do not match and I need to wipe the Database. After that I rerun my sync script to have some Data which works fine, but the next time I need to run wasp clean, I need to repeat the process. It's not a Shopstopper nor Dealbreaker. Just wanted to point it out and ask how you detect the migration changes?
I tried to prevent this by excluding the migrations table from the remote dump and do a local dump first and after dropping the local db and restoring the remote dump I also restore the local migrations table hoping to prevent the issue, which sadly did not work.
I hope I managed to describe the "issue" well enough.
Do you Guys have any Insights why this might be happening or how to prevent it?
