Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in migration engine. Reason: [migration-engine/connectors/sql-migration-connector/src/sql_renderer/postgres_renderer.rs:944: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. #15705

Closed
jkomyno opened this issue Oct 7, 2022 · 0 comments · Fixed by prisma/prisma-engines#3379
Assignees
Labels
bug/2-confirmed Bug has been reproduced and confirmed. kind/bug A reported bug. team/schema Issue for team Schema. topic: error reporting Issues created via Prisma's CLI Crash Reporting topic: postgresql topic: prisma db push CLI: prisma db push
Milestone

Comments

@jkomyno
Copy link
Contributor

jkomyno commented Oct 7, 2022

Command: prisma db push
Version: 4.4.0
Binary Version: f352a33b70356f46311da8b00d83386dd9f145d6
Report:

JS Stacktrace:

Error: Error in migration engine.
Reason: [migration-engine/connectors/sql-migration-connector/src/sql_renderer/postgres_renderer.rs:944: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.

Rust Stacktrace:

Starting migration engine RPC server
The migration was not applied because it triggered warnings and the force flag was not passed.
[migration-engine/connectors/sql-migration-connector/src/sql_renderer/postgres_renderer.rs:944: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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment