Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
UT_SONAR_TEST_REPORTER: wrong/missing encoding information #676
Atm the encoding charset of the result-XML of
We should add charset encoding based on the current session's charset setting.
Trouble is - I cant find any valuable info on how to detect current encoding and put it into XML.
After some digging around here is what I've found.
Converting between Oracle and IANA names
Having that function we can now convert Oracle character-set name to IANA name.
select utl_i18n.map_charset(value) iana_charser, value oracle_charset from v$nls_valid_values x where parameter = 'CHARACTERSET';
We could now use the below query to get the XML/HTML
select utl_i18n.map_charset(value), value from v$nls_parameters where parameter = 'NLS_CHARACTERSET';
The trouble is however that we don't know client-side encoding.
We need to take one of 2 actions:
New plan after ongoing discussion in utPLSQL/utPLSQL-cli#78:
I guess the latter two tasks will require to add new param to ut_output_reporter type - might also need additional care in java-api for compatibility.