Print stack trace of wrapped SQLException #22
Merged
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In PostgreSQL, in case there is SQLException during migration, the stack trace printed out is a generic statement like:
Exception in thread "main" java.sql.BatchUpdateException: Batch entry 0 alter table foo rename column bar to bar2 was aborted. Call getNextException to see the cause.
This patch will get next exception and print out stack trace for the root cause of this failure. The result will look like below:
org.postgresql.util.PSQLException: ERROR: relation "foo" does not exist
...
Exception in thread "main" java.sql.BatchUpdateException: Batch entry 0 alter table foo rename column bar to bar2 was aborted. Call getNextException to see the cause.eError(QueryExecutorImpl.java:457)