Feature request: In-Database migration lock

[joeyaurel]

Problem

Consider deploying a Node.js server twice (because of horizontal scaling; maybe load balancing), and both of them would call a prisma migrate up while deploying. What could happen now is that Node.js server 1 tries to migrate while Node.js server 2 also tries the same. This could maybe result in conflicts within the database.

Solution

A "In-Database" migration lock on a table designed specifically for locking.

Workflow would be as follows:

• First prisma migrate up tries to create special table and maybe sets a boolean value indicating that a migration is running
• Any other script now running prisma migrate up sees the lock in the table and skips the migration
• When the initial prisma migrate up finishes, the lock within the database "unlocks"

[joeyaurel]

@albertoperdomo Have you guys put a thought on this? :) Or is there a "best practice" to this kind of issue?

[tomhoule]

It is something we have plans for, it will come as soon as there is time to work on it: prisma/prisma-engines#1118

[tomhoule]

Let's close this issue as a duplicate of prisma/prisma-engines#1118

Work on this is planned.