I recently upgraded to prisma 1.34. I noticed that...
# orm-help
a
I recently upgraded to prisma 1.34. I noticed that migrations: false has no effect anymore? I assume that this was removed?
n
Hey Andre, yes the
migration
flag was removed in a recent release: https://www.prisma.io/blog/datamodel-v11-lrzqy1f56c90/#simpler-migrations--improved-introspection
👍 1
a
Hahah thats quite scary. Don’t know if I like the fact that they can alter my database. I kinda liked having that control
Soo what they are saying there is that you can still perform manual migrations. But then you just dont use prisma deploy, but just prisma generate? am I understanding this correctly?
m
You can now control this behaviour with the
prisma deploy
command. If you do want the old behaviour you can run
prisma deploy --no-migrate
a
@marcus this is quite interesting. I just ran this and it gave me errors that I need to make some updates to my datamodel. Basically just making some optional fields required. am I correct if I am say that running --no-migrate prisma looks at the database structure, compares it with your datamodel en then asks for updates to your datamodel. So its the initial sql that the database was created with that becomes the ‘master’ ?
m
yes. With
--no-migrate
we don’t perform a migration and so we ensure that your datamodel and database schema are in sync.
a
perfect makes total sense now. Thank you