Fix dbms output in case of exception #77
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Decouple dbms_output logging implementation from the main begin/end call block. This enables dumping dbms_output even when the database call raises exception.
Bugfix for the following issue: dbms_output logging didn't work properly when the database call failed with exception: it was suppressed for the failing call and was displayed with the next (succesful) call. Fixed by moving dbms output logging to the "ensure" section.
javornikolov
force-pushed
the
fix-dbms-output-in-case-of-exception
branch
from
d792b54 to
7ea55c8
Compare
javornikolov
added a commit
that referenced
this pull request
May 6, 2015
Fix dbms output in case of exception
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix for the following issue: dbms_output logging didn't work properly when the database call failed with exception: it was suppressed for the failing call and was displayed with the next (successful) call.
Fixed by moving dbms output logging to the
ensuresection.