How to manage schema in teamwork?

[pizza7311]

Question

Hello. i am using mysql with prisma while developing with my team.
Our team uses one database to develop each feature. and only uses prisma db push to synchronize schema.
The problem is when each teammates are pushing schema to database previous works is overwritten

For example here's the original schema.

model A {
 //...
}

model B {
 //...
}

and teammates make each other's branches and update schema

this is my schema

//...

model C {
 //add new model
}

and this is team's schema

//...

model D {
 //...
}

If i push the schema, prisma will create a new table. after that, my teammate finish his work and push schema to database and my works will overwritten. i haven't used prisma migration dev, but can migration solve this problem? or there's any other solution?

[ludralph]

Hi @pizza7311 👋

Using Prisma Migrate can help solve this problem. Prisma Migrate is a database schema migration tool that enables you to keep your database schema in sync with your Prisma schema, and version control for your database schema.

When you make changes to your Prisma schema, you can generate a new migration with Prisma Migrate. This migration can be committed to your version control system (like Git), allowing your teammates to pull the changes and apply the migration to their local databases. This way, each teammate's changes can be applied sequentially without overwriting each other's work.

Here's a basic workflow for incorporating changes from collaborators:

1. Pull the changed Prisma schema and ./prisma/migrations folder
2. Run the migrate dev command to apply new migrations:

npx prisma migrate dev

Migrations are applied in the same order as they were created. The creation date is part of the migration subfolder name - for example, 20210316081837-updated-fields was created on 2021-03-16-08:08:37.

Please note that this guide does not apply for MongoDB. Instead of migrate dev, db push is used for MongoDB. For more details, you can refer to the Prisma documentation on team development with Prisma Migrate.

[lroal]

But this still means each team must be synchronized with a shared migration branch ? Right ?
The cannot create independent migrations in parallel branches , or ?
Because migrations must sequential and not parallel.