You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some objects following error occurs on the Identifiers, Table Usages and Column Usages tab:
The obvious reason is that the sys_connect_by_path function produces a result with more than 4000 bytes. This can happen only with more or less 130 levels (assuming a max of 30 characters per name). In a customer's case there are more than 700 levels. Most levels were artificial. Produced by the fix of inconsistent PL/Scope data (missing levels). In such a case the node was connected to the last previous consistent node. In case of a series of calls to a unit which is not compiled with PL/Scope this leads to a lot of nested levels where no nesting would be expected.
The text was updated successfully, but these errors were encountered:
This fixes issue PhilippSalvisberg#34:
ORA-01489: result of string concatenation is too long
by ensuring that the length of name_path remains <= 4000 bytes,
replacing as many levels as necessary by .../ starting from
level 4, so the first 3 levels are always kept, and the tailmost
levels should be preserved too.
For some objects following error occurs on the
Identifiers
,Table Usages
andColumn Usages
tab:The obvious reason is that the
sys_connect_by_path
function produces a result with more than 4000 bytes. This can happen only with more or less 130 levels (assuming a max of 30 characters per name). In a customer's case there are more than 700 levels. Most levels were artificial. Produced by the fix of inconsistent PL/Scope data (missing levels). In such a case the node was connected to the last previous consistent node. In case of a series of calls to a unit which is not compiled with PL/Scope this leads to a lot of nested levels where no nesting would be expected.The text was updated successfully, but these errors were encountered: