Error in migration when updating enum
See original GitHub issueHi Prisma Team! Prisma Migrate just crashed.
Command
migrate dev
Versions
Name | Version |
---|---|
Platform | windows |
Node | v16.15.0 |
Prisma CLI | 4.2.1 |
Engine | 2920a97877e12e055c1333079b8d19cee7f33826 |
Error
Error: Error in migration engine.
Reason: [migration-engine\connectors\sql-migration-connector\src\sql_renderer\postgres_renderer.rs:908:22] We should only be setting a changed default if there was one on the previous schema and in the next with the same enum.
Please create an issue with your `schema.prisma` at
https://github.com/prisma/prisma/issues/new
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Migration doesn't work when adding new value to enum and ...
Migration doesn't work when adding new value to enum and using new value as default, New enum values must be committed before they...
Read more >Getting Entity Framework migration error with enum
It's a known issue that EntityFramework doesn't play well with enum values. I don't know that this works with code-first, ...
Read more >Upgrading PostgreSQL's Enum type with ... - Makimo
In this tutorial we've successfully generated the migration file which can automatically upgrade enum types on PostgreSQL server. If you want to read...
Read more >Error when updating schema enum type - Elixir Forum
Hi,. I previously had the below migration and schema with statuses [:start, :closed]. def up do update_statuses([:open, :closed], ...
Read more >Postgres: Enum type fields | Hasura GraphQL Docs
As enum tables have a requirement to contain at least 1 row, it is necessary to have a migration which inserts values into...
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 FreeTop 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
Top GitHub Comments
Yes, it was the same situation as described above.
Another report: https://prisma-errors.netlify.app/report/14266