Skip to content

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

Merged
merged 4 commits into from
Oct 26, 2017

Conversation

viniciusam
Copy link
Member

@ghost ghost assigned viniciusam Oct 22, 2017
@ghost ghost added the in progress label Oct 22, 2017
@viniciusam viniciusam requested a review from jgebal October 22, 2017 16:15
* @param bufferLen the buffer length
*/
public static void enableDBMSOutput(Connection conn, int bufferLen) {
try (CallableStatement call = conn.prepareCall("BEGIN dbms_output.enable(?); END;")) {
Copy link
Member

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.

Copy link
Member Author

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";
Copy link
Member

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

@viniciusam viniciusam merged commit 390980e into develop Oct 26, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants