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

Bug on issue #1125 #1126

Closed
al-hexagon opened this issue Mar 8, 2021 · 2 comments
Closed

Bug on issue #1125 #1126

al-hexagon opened this issue Mar 8, 2021 · 2 comments

Comments

@al-hexagon
Copy link

Describe the bug
#1125

Provide version info
Information about utPLSQL and Database version,

set serveroutput on
declare
  l_version varchar2(255);
  l_compatibility varchar2(255);
begin
  dbms_utility.db_version( l_version, l_compatibility );
  dbms_output.put_line( l_version );
  dbms_output.put_line( l_compatibility );
end;
/

19.0.0.0.0
19.7.0

select substr(ut.version(),1,60) as ut_version from dual;
select * from v$version;
select * from nls_session_parameters;
select substr(dbms_utility.port_string,1,60) as port_string from dual;

file attached

Information about client software
What client was used to run utPLSQL tests? Was it from TOAD, SQLDeveloper, SQLPlus, PLSQL Developer etc...

SQL Developer with extension for UtPlsql - but this doesn't matter. The output is the same if unit-test run by script or other server / machines

To Reproduce
see issue

Expected behavior
covering all lines correctly

Example code
see issue

@al-hexagon
Copy link
Author

ut3_bug.txt

@PhilippSalvisberg
Copy link
Member

duplicates to #1125

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

No branches or pull requests

2 participants