Some compilers do not offer any practical way to derive the list of dependencies as a side-effect of the compilation, requiring a separate run (maybe of another tool) to. The econf helper now adds -disable-dependency-tracking to the configure arguments if the string disable-dependency-tracking occurs in the output of.Config.status: executing depfiles commandsWe can disable tracking protection by setting privacy.trackingprotection.enabled false.
Call signature is the parameter list (order, names, and types of parameters), return type, ACCESSIBLE BY clause ("white list"), purity Foot 1, determinism, parallelism, pipelining, and (if the procedure or function is implemented in C or Java) implementation properties.ACCESSIBLE BY clause ("white list") changes.Dependent object references a dropped or renamed package item.Dependent object references a package procedure or function whose call signature or entry-point number Foot 2, changed.If referenced procedure or function has multiple overload candidates, dependent object is invalidated if any overload candidate's call signature or entry point number changed, or if a candidate was added or dropped.Dependent object references a package cursor whose call signature, rowtype, or entry point number changed.Dependent object references a package type or subtype whose definition changed.Dependent object references a package variable or constant whose name, data type, initial value, or offset number changed.Purity refers to a set of rules for preventing side effects (such as unexpected data changes) when invoking PL/SQL functions within SQL queries. The cases in the right column, and all operations not listed in Table 26-2, cause coarse-grained invalidation.Table 26-2 Operations that Cause Fine-Grained Invalidation OperationDependent object (except a view) uses SELECT * on table.Dependent object performs INSERT on table without specifying column list.Dependent object references table in query that contains a join.Dependent object references table in query that references a PL/SQL variable.ALTER TABLE table columnALTER TABLE table DROP CONSTRAINT not_null_constraintDependent object directly references column.Dependent object is a trigger that depends on an entire row (that is, it does not specify a column in its definition).Dependent object is a trigger that depends on a column to the right of the dropped column.Online Table Redefinition ( DBMS_REDEFINITION)Column lists of new and old definitions differ, and at least one of these is true:Dependent object references column that is modified or dropped in new view or table definition.Dependent object uses view %rowtype or table %rowtype.Dependent object performs INSERT on view or table without specifying column list.New view definition introduces new columns, and dependent object references view or table in query that contains a join.New view definition introduces new columns, and dependent object references view or table in query that references a PL/SQL variable.Dependent object references view or table in RELIES ON clause.New and old synonym targets differ, and one is not a table.Both old and new synonym targets are tables, and the tables have different column lists or different privilege grants.Both old and new synonym targets are tables, and dependent object is a view that references a column that participates in a unique index on the old target but not in a unique index on the new target.The index is a function-based index and the dependent object is a trigger that depends either on an entire row or on a column that was added to table after a function-based index was created.The index is a unique index, the dependent object is a view, and the view references a column participating in the unique index.Call signature changes. This is called cascading invalidation.With coarse-grained invalidation, a data definition language (DDL) statement that changes a referenced object invalidates all of its dependents.With fine-grained invalidation, a DDL statement that changes a referenced object invalidates only dependents for which either of these statements is true:The dependent relies on the attribute of the referenced object that the DDL statement changed.The compiled metadata of the dependent is no longer correct for the changed referenced object.For example, if view v selects columns c1 and c2 from table t, a DDL statement that changes only column c3 of t does not invalidate v.The DDL statement CREATE OR REPLACE object has no effect under these conditions:Object is a PL/SQL object, the new PL/SQL source text is identical to the existing PL/SQL source text, and the PL/SQL compilation parameter settings stored with object are identical to those in the session environment.Object is a synonym and the statement does not change the target object.The operations in the left column of Table 26-2 cause fine-grained invalidation, except in the cases in the right column. If a change to C invalidates B, it invalidates A (and all other direct and indirect dependents of B). If object A depends on object B, which depends on object C, then A is a direct dependent of B, B is a direct dependent of C, and A is an indirect dependent of C.Direct dependents are invalidated only by changes to the referenced object that affect them (changes to the signature of the referenced object).Indirect dependents can be invalidated by changes to the reference object that do not affect them.
Otherwise, go to step d.Search for a schema whose name matches the first piece.If found, and if the object name has a second piece, go to step e. Otherwise, go to step c.Search for a public synonym that matches the first piece.If found, go to step 2. Otherwise, go to step b.Search the current schema for an object whose name matches the first piece.If found, go to step 2. Department_id, the first piece is hr.The procedure for trying to qualify the first piece is:If the object name is a table name that appears in the FROM clause of a SELECT statement, and the object name has multiple pieces, go to step d. Otherwise, the first piece is the piece to the left of the leftmost period for example, in hr. A procedure or function added to the end of a PL/SQL package is given a new entry-point number.For the procedure to succeed, all pieces of the object name must be visible in the current edition.Try to qualify the first piece of the object name.If the object name has only one piece, then that piece is the first piece.
All other local procedures that depend on the remote procedure with the new time stamp are also invalidated.Time stamp comparison occurs when a statement in the body of the local procedure calls the remote procedure. Neither is recompiled.If the two time stamps do not match, the local procedure is invalidated and an error is returned to the calling environment. If the two time stamps match, both the local and remote procedures run. The time stamp shows when the procedure was created, altered, or replaced.A compiled procedure contains information about each remote procedure that it calls, including the schema, package name, procedure name, and time stamp of the remote procedure.In time-stamp dependency mode, when a local stored procedure calls a remote procedure, Oracle Database compares the time stamp that the local procedure has for the remote procedure to the current time stamp of the remote procedure. Otherwise, return an error—the object name cannot be qualified.Whenever a procedure is compiled, its time stamp is recorded in the data dictionary.
For example, the UPDATE statement rolls back in this code:But the UPDATE statement does not roll back in this code:The disadvantages of time-stamp dependency mode are:Dependent objects across the network are often recompiled unnecessarily, degrading performance.If the client-side application uses PL/SQL, this mode can cause situations that prevent the application from running on the client side.An example of such an application is Oracle Forms. The local procedure must be recompiled.If DML statements precede the invalid call, they roll back only if they and the invalid call are in the same PL/SQL block. Statements after the invalid call do not run.
0 kommentar(er)
