At current state which Migrate is 'more stable' fo...
# prisma-migrate
m
At current state which Migrate is 'more stable' for use (I'm aware that both are not full stable yet) ?The new 'early access' one or the earlier '--experimental'?. Anyone had any issues, database breakage using migrate? I was holding off prisma1>prisma2 upgrade, cause of lack of migrations. I'm eager to do the upgrade to prisma2 now, but am a little scared. I'm not comfortable with raw sql migrations. Any info will be great, thank you.
a
Hello @Maciek K! I’m the product manager working on Migrations. The version of migrate in Early Access is an evolution of the experimental migrate. We have made some fundamental changes in the way Migrate works, but we are reusing many (most?) of the existing components. If you wait for a few more weeks, we are planning eventually release this evolved Migrate in Preview. At this stage it should be considered as stable as the current experimental version in the stable package.
Regarding your feeling not comfortable with raw SQL migrations: Note that you don’t have to write SQL in your migrations, but you can. The SQL in the migration files is the same that Prisma Migrate would apply to make the changes happen. By putting the DDL/SQL statements in a file, we are providing the ability for developers to have some extra control over how migrations are carried out, and make modifications if needed.
Hope this answers your questions. Please let me know if you have any follow up questions or comments!
j
Note @Alberto Perdomo it’s better to refer to
latest
(which is actually the npm channel) than
stable
💯 1
🙏 1