Beta Notes
Blank lines in PL/SQL DDL
Blank lines in PL/SQL DDL cause incorrect syntax error when the =QP5_SHL_SET_SQLPLUS_SQLBLANKLINES= option is used.
Case-only formatting
Case-only formatting did convert tabs to single spaces rather than converting them to the number of spaces given in the Indenting control, causing the layout to get messed up.
Code Analysis Rule 4409
Code Analysis Rule 4409 (“Ensure END [LOOP] statement is not missing a semi-colon.”) : The test code was invalid.
Formatter: token alignment after a comment
Tokens preceded by a single line comment (on the previous line of course) were not aligned to the comment. Sometimes the comment was output to the right of its preceding token rather than on the next line at the same column.
Examples:
Old …
IF qu_datatype_xp.is_query (attribute_io.data_type.universal_id) /* Not just select * - any select with non comparables! qu_all_objects.query_is_select_star(attribute_io.ATTRIBUTE.value1)*/ AND attribute_io.column_set.uncomparable_columns.COUNT > 0
new…
IF qu_datatype_xp.is_query (attribute_io.data_type.universal_id) /* Not just select * - any select with non comparables! qu_all_objects.query_is_select_star(attribute_io.ATTRIBUTE.value1)*/ AND attribute_io.column_set.uncomparable_columns.COUNT > 0
Old ...
FUNCTION tabfunc_pkg_name (key_in IN VARCHAR2, subobject_name_in IN VARCHAR2 DEFAULT NULL-- 1.8 not used )
new…
FUNCTION tabfunc_pkg_name (key_in IN VARCHAR2, subobject_name_in IN VARCHAR2 DEFAULT NULL-- 1.8 not used )
Old ...
value_string qu_config.maxvarchar2/* fp.value and exp.value */ ,
new…
value_string qu_config.maxvarchar2/* fp.value and exp.value */ ,
Old ...
THEN l_query := l_query || 'qu_config.random_integers(' || tdg_in.num_of_values -- doubled_quotes || ',' || tdg_in.min_value -- doubled_quotes || ',' || tdg_in.max_value -- doubled_quotes || '))';
new…
THEN l_query := l_query || 'qu_config.random_integers(' || tdg_in.num_of_values -- doubled_quotes || ',' || tdg_in.min_value -- doubled_quotes || ',' || tdg_in.max_value -- doubled_quotes || '))';
SELECT … CONNECT BY NOCYCLE (expr)
SELECT ... CONNECT BY NOCYCLE ( expr ) did yield an “ambiguous syntax” error.