-
Notifications
You must be signed in to change notification settings - Fork 5
Enable dbms_output before calling ut_runner.run #22
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
Conversation
* @param bufferLen the buffer length | ||
*/ | ||
public static void enableDBMSOutput(Connection conn, int bufferLen) { | ||
try (CallableStatement call = conn.prepareCall("BEGIN dbms_output.enable(?); END;")) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would use NULL as max value of the buffer.
As per Oracle doc, ENABLE(NULL) makes the buffer size unlimited.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, I will remove the one with the size parameter, I think we don't need that anyways...
@@ -12,6 +12,8 @@ | |||
*/ | |||
public final class DBHelper { | |||
|
|||
public static final String UTPLSQL_VERSION = "3.0.3"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be called: UTPLSQL_COMPATIBILITY_VERSION
ut_runer.run
needs to have DBMS_OUTPUT enabled #20