-
Notifications
You must be signed in to change notification settings - Fork 52
Make migration errors more strict #5197
Copy link
Copy link
Open
Labels
1 - BugIncorrect behavior of the productIncorrect behavior of the product2 - Database/SchemaIssues that are related to the underlying database and schemaIssues that are related to the underlying database and schemapri:highMust be resolved before releasingMust be resolved before releasing
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
1 - BugIncorrect behavior of the productIncorrect behavior of the product2 - Database/SchemaIssues that are related to the underlying database and schemaIssues that are related to the underlying database and schemapri:highMust be resolved before releasingMust be resolved before releasing
Currently, user often fails to provide the "root" user for migrations. This leads to scenarios where DDL migrations partially run.
I think this can be solved with #1037.