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

Skip to content

Added buffering of dbms_output before the run.#495

Merged
jgebal merged 1 commit intodevelopfrom
feature/dbms_output_buffer_fix
Oct 17, 2017
Merged

Added buffering of dbms_output before the run.#495
jgebal merged 1 commit intodevelopfrom
feature/dbms_output_buffer_fix

Conversation

@jgebal
Copy link
Copy Markdown
Member

@jgebal jgebal commented Oct 17, 2017

dbms_output buffer content is now cached before the run starts.
The outcomes from the output are spooled back to the buffer at the end of the run.
That results in the outputs getting shown in the right order when executing ut.run in a PLSQL block that has some buffered data already.
Resolves #482

`dbms_output` buffer content is now cached before the run starts.
The outcomes from the output are spooled back to the buffer at the end of the run.
That results in the outputs getting shown in the right order when executing `ut.run` in a PLSQL block that has some buffered data already.
Resolves #482
@jgebal jgebal added this to the v3.1.0 milestone Oct 17, 2017
@ghost ghost assigned jgebal Oct 17, 2017
@ghost ghost added the in progress label Oct 17, 2017
@pesse
Copy link
Copy Markdown
Member

pesse commented Oct 17, 2017

Do you think that could have impact on utplsql-cli output? I'd like to try it out but will need a bit to do so for being pretty busy atm

@jgebal
Copy link
Copy Markdown
Member Author

jgebal commented Oct 17, 2017

Client does not consume from DBMS_OUTPUT at all.

@Pazus
Copy link
Copy Markdown
Member

Pazus commented Oct 17, 2017

I think we can merge it.
Approved.

@jgebal jgebal merged commit 66b0034 into develop Oct 17, 2017
@ghost ghost removed the in progress label Oct 17, 2017
@jgebal jgebal deleted the feature/dbms_output_buffer_fix branch October 20, 2017 07:05
@jgebal jgebal modified the milestones: v3.1.0, v3.0.4 Nov 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants