Migrate: Migrate Up / Down to Specific Migrations

Created on 1 Jul 2020 · 6Comments · Source: prisma/migrate

Problem

To get around the imperative migration issue as stated here https://github.com/prisma/migrate/issues/492
I need to run a database migration, then migrate the data, then proceed with another database migration.
If I test this locally there's no way for me to perform this operation in production as migrate up runs all migrations and I can't do the data migration in between.

For example, if I add a non-nullable Author relation to a Post, I need to

Create a nullable migration

model Post {
  id String @default(cuid()) @id
  author Author? @relation(fields: [authorId], references: [id])
  authorId String?
}

Set up the default data

const posts = await prisma.posts.findMany()
for (const post of posts) {
    await prisma.task.update({
    where: { id: post.id },
    data: {
        author: getDefaultAuthor(),
    },
});

Then migrate the field to be nullable.

model Post {
  id String @default(cuid()) @id
  author Author @relation(fields: [authorId], references: [id])
  authorId String
}

If I perform the 3 steps above locally, then wish to do the same in production, it is not possible as migrate up will execute both steps 1 & 3, and I can't execute step 2 in between.

All 6 comments

Hi @ryanking1809

Thanks for the feedback :)

So this below already exists and would help as a workaround like you said:

      # Go up by one migration
      prisma migrate up 1 --experimental

      # Go up to a migration by timestamp
      prisma migrate up 20200205204907 --experimental

      Go up to a migration by name
      prisma migrate up "add first_name field" --experimental

This applies for both up & down commands.