DB migrations process and best practices

[yuval-hazaz]

DB migrations process and best practices

[tabuckner]

have you guys heard of https://github.com/liquibase/liquibase? there's even a node wrapper here https://www.npmjs.com/package/liquibase.

This tool is used internally by a similar project, https://www.jhipster.tech/

[yuval-hazaz]

Thanks @tabuckner .
Since this issue was opened, Prisma released the Prisma migrate as production-ready, so probably it should be the right tool to move forward with.
https://www.prisma.io/blog/prisma-migrate-ga-b5eno5g08d0b
I will also look into liquibase - it looks interesting

[yuval-hazaz]

I found this article from prisma about migrations
https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-migrate

It describes exactly what we are doing right now. I still feel a bit puzzled about the quantity of migrations that we'll end up with but according to the article it is by design...

They also mention it is still experimental so the fact that we sometimes have conflicts is expected

so, I assume we should keep use migration save and migrate up after each change. In a normal process a feature may include several changes in the DB and sometime we don't make all changes at once so we may end up with several migrations per features... not nice.

What do you think?