Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Ability to enable/disable DBMS_OUTPUT from cli #137

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

Closed
jgebal opened this issue Mar 28, 2019 · 3 comments · Fixed by #141
Closed

Ability to enable/disable DBMS_OUTPUT from cli #137

jgebal opened this issue Mar 28, 2019 · 3 comments · Fixed by #141
Assignees
Labels
Milestone

Comments

@jgebal
Copy link
Member

jgebal 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
Copy link
Member Author

jgebal 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
Copy link
Member Author

jgebal 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
Copy link
Member

pesse 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
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants