Skip to content

A new option: ignore_warnings #85

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

Merged
merged 1 commit into from
Oct 11, 2017

Conversation

harawata
Copy link
Member

@harawata harawata commented Oct 11, 2017

The default value is true, i.e. warnings do not stop migrations.
If set to false, a warning raised by the database stops migration.
This should fix #84 #89 #91.

…f set to true, a warning raised by the database is ignored and migration continues.
@harawata harawata added this to the 3.3.2 milestone Oct 11, 2017
@harawata harawata self-assigned this Oct 11, 2017
@harawata harawata merged commit dc87865 into mybatis:master Oct 11, 2017
@harawata harawata changed the title A new option: ignoreWarnings A new option: ignore_warnings Oct 14, 2017
@@ -64,6 +64,9 @@ full_line_delimiter=false
# but some do.
auto_commit=false

# If set to true, warnings from the database do not interrupt migrations.
ignore_warnings=false
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When this PR was merged, the default value was false. It was changed in 2f38956

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate fail when postgreSQL issue a Notice
1 participant