visualize-admin
Improve database migrations
Currently, we update database schema in a non-production way (using prisma db push, which updates the database in place, which generating SQL migration files).
As we expand our database schema more and more, we should switch to using a recommended way of conducting migrations, by generating migrations locally with prisma db dev, validating them, adding to source control, and actually migrating our TEST / INT / PROD databases using prisma migrate deploy.
Limited local testing revealed no straightforward way to move to migrations without resetting the DB. Obviously, it would be preferable not to have to do this. Our version of prisma is quite old at this point – it's possible there are limitations that no longer hold true with the current version. Will continue investigating this with @bprusinowski as resources allow.
