`--migrations` to specify output directory for migrations

With --schema we can now specify the file path of where the Prisma Schema is located, instead of the default ./prisma/schema.prisma. This has the unfortunate side effect, that migrations are also output next to that file - which might not be what you want.

We want to have a --migrations parameter that takes the path to a folder where all the migration related content is output. The default path for that parameter, if it is not supplied, thus is ./prisma/migrations.

[zakthedev]

it would be better if the migrations output could be set via package.json as follows:

“prisma”: { “schema”: “src/schema.prisma”, “migrateOutput” : “src/migrations/” }

[Jolg42]

@benhickson Thank you for the detailed explanation!

I guess a workaround could be something like this, one folder per schema:

• ./src/db1/schema.prisma
• ./src/db2/schema.prisma

And then calling prisma commands with --schema="./src/db1/schema.prisma"

Migrate will then create a migrations directory next to each schema like

• ./src/db1/migrations/…
• ./src/db2/migrations/…

Is that a good enough workaround or customizing the name of the migrations directory would be better here?