Skip to content
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

Ability to enable/disable DBMS_OUTPUT from cli #137

Closed
jgebal opened this issue Mar 28, 2019 · 3 comments

Comments

@jgebal
Copy link
Member

commented Mar 28, 2019

Previous versions of cli had DBMS_OUTPUT.ENABLED;
With release 3.1.6 this is no longer the case.
Some of our tests are relying on DBMS_OUTPUT and were working properly on previous version of cli. They started failing after upgrade.

@pesse pesse self-assigned this Mar 29, 2019

@pesse pesse added the bug label Mar 29, 2019

@pesse pesse added this to the 3.1.7 milestone Mar 29, 2019

@jgebal

This comment has been minimized.

Copy link
Member Author

commented Mar 31, 2019

Ideally that schold be parameter to cli.
This way user can have control over that behavior.
I woyld leave default enabled probably.

@jgebal

This comment has been minimized.

Copy link
Member Author

commented Mar 31, 2019

Or follow sqlcl and sqlplus (default=disabled)

@jgebal jgebal changed the title DBMS_OUTPUT disabled in test-runner Ability to enable/disable DBMS_OUTPUT from cli Mar 31, 2019

@pesse

This comment has been minimized.

Copy link
Member

commented Apr 1, 2019

Love the idea of a parameter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.