Error in migration engine - no current timer when using prisma2 migrate
See original GitHub issueI’m using the latest release 2.0.0-preview020
and I’m getting the following error when running prisma2 migrate save --experimental
.
Error in migration engine.
Reason: [src/libcore/option.rs:1185:5] no current timer
Report id 1254
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Migration troubleshooting in production - Prisma
The following guide describes issues relating to Prisma Migrate that can occur in production, and how to resolve them. This guide does not...
Read more >Migration with transaction fails without good error message
Bug description According to this blog post Prisma supports transactions for migrations when using the postgres database.
Read more >Error when migrating models to database Prisma
I tried Introspect. But, my DB currently has no tables and that threw an error. I tried npx prisma migrate save -experimental b/c...
Read more >prisma-rays - npm
In prisma migrate , attempting to create multiple migrations without applying any of them is not supported. if you attempt to create another ......
Read more >Prisma - Supabase
By default, Prisma migrations will try to drop the postgres database, which can lead to conflicts with Supabase databases. For this scenario, use...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have a fix - PR: https://github.com/prisma/prisma-engine/pull/405
Will keep updating this issue until the fix is released.
@tomhoule I’m on macOS and using a MySQL database.
this is the schema I’m using.