You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wandering around the doc to find out how can I create an empty migration and then I ended up herje under options section I read that it says:
Creates a new migration based on the changes in the schema but does not apply that migration. Run migrate dev to apply migration.
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.
Thus I think it is time to revise it to be more accurate. Maybe something like this would do the trick: "Creates a new migration based on the changes in the schema, or just creating an empty one when your schema has not change. Note that this does not apply that migration automatically. Run migrate dev to apply migration."
Any comment/idea/feedback?
Best of luck.
The text was updated successfully, but these errors were encountered:
@kasir-barati After making changes in the databse or prisma schema , user has to run the command npx run dev to update the prisma schema everytime to keep the database in sync with the model , Do you want that to update in the migration section ?
Hey guys,
I was wandering around the doc to find out how can I create an empty migration and then I ended up herje under options section I read that it says:
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 inschema.prisma
.Thus I think it is time to revise it to be more accurate. Maybe something like this would do the trick: "Creates a new migration based on the changes in the schema, or just creating an empty one when your schema has not change. Note that this does not apply that migration automatically. Run
migrate dev
to apply migration."Any comment/idea/feedback?
Best of luck.
The text was updated successfully, but these errors were encountered: