R. Vassallo
R. Vassallo
In keeping with issue #63, chains of synonyms are not traversed by the `lineage_util` package. Reason: `dd_util.resolve_synonym` performs only a "shallow" resolution, as opposed to "in-depth" resolution of chains of...
**Case 1**: for objects of type synonym, the following disjunction voids the filter on `owner` : ``` where (owner = :OBJECT_OWNER or upper(replace(:OBJECT_TYPE, 'plscope-utils-')) = 'SYNONYM') ``` The effect can...
Actual:  Expected:  Cause: wrong filter applied to `dba_source` / `all_source` The "Text" column is supposed to show the source text in _referencing_ code units, not that...
E.g. the "Identifiers" tab is shown (as expected) from child nodes of the PL/Scope -> Packages node, but not from child nodes of the main Packages node at schema level,...
As of v1.0.0, the "Compile with PL/Scope" action recompiles PL/SQL code by calling `dbms_utility.compile_schema` [^types_special_case]. Replacing that procedure should be considered, for the following reasons: 1. It's not complete, as...
Synonyms compiled with PL/Scope can be found in sys.plscope\_identifier$, with the following identifying properties: * type# = 37 * symrep = name of the synonym * obj# = object\_id of...
Example: Using utPLSQL, release 3.1.12, installed in the UT3 schema. ``` exec plscope_context.set_attr('OWNER', 'UT3'); exec plscope_context.set_attr('OBJECT_TYPE', 'PACKAGE BODY'); exec plscope_context.set_attr('OBJECT_NAME', 'UT_SUITE_CACHE_MANAGER'); select line, col, operation, ref_owner, ref_object_type, ref_object_name, direct_dependency, text...
If using an account with DBA privileges, I'd expect to be able to use the "Compile with PL/Scope" action in order to recompile _any_ schema of my own choosing[^expected_restrictions]. This...
Test setup: ``` alter session set current_schema = "SCOTT"; alter session set plscope_settings = "IDENTIFIERS:ALL, STATEMENTS:ALL"; create table ta (id number); create table tb (id number); create or replace view...
Test setup: ``` alter session set current_schema = "SCOTT"; alter session set plscope_settings = "IDENTIFIERS:ALL, STATEMENTS:ALL"; create table t1 (c1 number); create synonym s_t1 for t1; create view vw_t1 as...