Failed SQL migration error reporting improvement #649
Merged
Conversation
|
Thanks for the fix. I can't merge it until the build passes though. Cheers |
|
Thanks for the heads up, I missed that Travis CI report... |
|
Don't put in too much effort yet. I believe the issue is on their side: travis-ci/travis-ci#1689 |
axelfontaine
added a commit
that referenced
this pull request
Nov 29, 2013
Failed SQL migration error reporting improvement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
This pull request fixes issues #575, #587, #647.
A new exception class FlywaySqlScriptException (subclass of FlywayException) was introduced in order to explicitly capture information related to error (script line, statement, jdbc exception), so it can be used in client code to implement application-specific exception handling if required.