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

Skip to content

Fixing #273 - Failed to write to dbms_output (Oracle 11g)#278

Merged
jgebal merged 2 commits intoutPLSQL:developfrom
jgebal:feature/fix_ut_output_buffer_issues
Apr 20, 2017
Merged

Fixing #273 - Failed to write to dbms_output (Oracle 11g)#278
jgebal merged 2 commits intoutPLSQL:developfrom
jgebal:feature/fix_ut_output_buffer_issues

Conversation

@jgebal
Copy link
Copy Markdown
Member

@jgebal jgebal commented Apr 17, 2017

No description provided.

@jgebal jgebal added the bugfix label Apr 17, 2017
@jgebal jgebal added this to the v3.0.0 milestone Apr 17, 2017
@coveralls
Copy link
Copy Markdown

coveralls commented Apr 17, 2017

Coverage Status

Coverage remained the same at 75.456% when pulling d47dd10 on jgebal:feature/fix_ut_output_buffer_issues into c2497a9 on utPLSQL:develop.

Comment thread source/core/types/ut_varchar2_rows.tps Outdated
See the License for the specific language governing permissions and
limitations under the License.
*/
table of varchar2(4000)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lets fix it's bytes

@coveralls
Copy link
Copy Markdown

coveralls commented Apr 18, 2017

Coverage Status

Coverage remained the same at 75.456% when pulling 4209764 on jgebal:feature/fix_ut_output_buffer_issues into c2497a9 on utPLSQL:develop.

@jgebal jgebal merged commit c13710c into utPLSQL:develop Apr 20, 2017
@jgebal jgebal deleted the feature/fix_ut_output_buffer_issues branch April 27, 2017 23:25
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 this pull request may close these issues.

3 participants