March 6, 2023 - Bug description so this --create-only is not working and it still asks for wiping the data How to reproduce by running "npx prisma migrate dev --create-only" this cmd Expected behavior No response Prisma information model ui_account { id...

In your development environment, you use prisma migrate dev --create-only to create a migration file without applying it. This command generates the migration.sql file based on the changes in your schema.prisma.

March 11, 2022 - bug/1-unconfirmedBug should have enough information for reproduction, but confirmation has not happened yet.Bug should have enough information for reproduction, but confirmation has not happened yet.kind/bugA reported bug.A reported bug.tech/enginesIssue for tech Engines.Issue for tech Engines.topic: drifttopic: prisma migrate dev --create-onlyCLI: prisma migrate dev --create-onlyCLI: prisma migrate dev --create-only

January 15, 2022 - Bug description Imagine a situation where you are iterating on your schema, and using the following command to create the migration files without actually applying any of them. prisma migrate dev --create-only Suppose you initially run i...

bunx prisma migrate dev --create-only · This creates the migration file but doesn't apply it. Run prisma migrate dev again to apply. bun · pnpm · yarn · npm · bunx prisma migrate dev --schema=./alternative/schema.prisma · Conceptual overview ...

-- DropForeignKey ALTER TABLE "Profile" DROP CONSTRAINT "Profile_userId_fkey"; -- DropIndex DROP INDEX "Profile_userId_unique"; -- AlterTable ALTER TABLE "Profile" DROP COLUMN "userId"; -- AlterTable ALTER TABLE "User" ADD COLUMN "profileId" INTEGER NOT NULL; -- CreateIndex CREATE UNIQUE INDEX "User_profileId_unique" ON "User"("profileId"); -- AddForeignKey ALTER TABLE "User" ADD FOREIGN KEY ("profileId") REFERENCES "Profile"("id") ON DELETE CASCADE ON UPDATE CASCADE; Save and apply the migration: bun · pnpm · yarn · npm · bunx prisma migrate dev · Edit on GitHub ·

October 18, 2021 - Create a migration with prisma migrate dev --create-only

August 10, 2022 - have a simple database (mysql) do npx prisma db pull then prisma migrate dev --name initial-migration --create-only

Edit on GitHub · Overview of Prisma Migrate · Learn everything you need to know about Prisma Migrate · Understanding Migrations · A mental model guide for working with Prisma Migrate in your project · Adding to a new projectCreate an initial migrationAdditional migrationsCommitting to versions controlAdding to an existing projectIntrospect to create or update your Prisma schemaCreate a baseline migrationWork around features not supported by Prisma Schema LanguageApply the initial migrationsCommit the migration history and Prisma schemaGoing furtherWhere to go next

April 14, 2021 - ... yes √ Name of migration ... init Prisma Migrate created the following migration without applying it 20210414181550_init You can now edit it and apply it by running prisma migrate dev. --create-only needing to reset my database, and supposedly even doing that, was unexpected.

August 7, 2024 - For --create-only flag. So I though I cannot use it for creating an empty migration file. Then I read this Stackoverflow Q&A and tried it. Surprisingly they were right about it; you can create an empty migration without the need to have anything changed in schema.prisma.

December 23, 2025 - Next, create a migration file that records these changes without actually applying them (since they already exist in the database). You can do this with npx prisma migrate dev --create-only --name fix_drift.

December 21, 2020 - Then when you run prisma migrate dev --preview-feature to apply the changes (without changing the SQL), you are prompted for a migration name. Once entered, everything applies but you end up with a migration file that just drops and adds FK's. I assume this is because you're expecting --create-only to only be used as a precursor to manual sql changes being made to the generated SQL files but that's not the case with me - it's just easier to build into my flow and I also like to check the SQL before it's applied.

You will use the --create-only flag and then add the changes you want. Read more · Q5: If the complexity lent itself better to a script, is there a way to run a script to do the same task ONCE just at the point of the migration?

April 13, 2022 - @janpio it seems like baselining needs a migration file to skip and even with prisma migrate dev --name initial-migration --create-only after prisma db pull following this instruction for that, I get the same error. it feels like --create-only option is not working.

June 11, 2024 - I splitted my existing scheme with already applied migrations, I decided to check what would happen if I called the command npx prisma migrate dev --create-only --skip-generate --schema prisma There are no changes to the models. As a res...

You want to rename a field (by ... Language - such as a stored procedure or a trigger. The --create-only command allows you to create a migration without applying it:...

I agree that you would need to create a new migration using prisma migrate dev --create-only. This will generate a new migration file in your prisma/migrations directory. You can then modify the migration script.

March 16, 2021 - Run prisma migrate dev --create-only to create the SQL migration without applying it.