How to avoid resetting the DB when switching between branches with schema diffs
Hello,
We are a small team of 4 working with prisma every day, and we often have to switch to the branch of a coworker to review their work.
But doing so, we need to reset the DB to migrate their version of the schema if they made change to it (while we also made some changes on our end while working).
So we've made a small script to reset the DB from a .dump file. It was working fine at first, but the DB is growing and it now takes ~5+ minutes to reset.
Do you have any idea if it's possible to avoid having to reset the DB in these cases ? If not I'd be curious to how some other teams handle this kind of workflow ?
Thanks for taking the time to read, and extra thanks if you take even more to answer ❤️ !
0 Replies