Re: What is Type "NON-EXISTENT" in v$access ?

Google search:

http://groups.google.com/groups?q=non-existent+jonathan+lewis&hl=en&lr=&ie=U TF-8&selm=926453356.1892.0.nnrp-02.9e984b29%40news.demon.co.uk&rnum=1

(which will do doubt be broken).

A cut and paste follows:

<quote>
'Non-existent' objects exist to handle'negative dependency' tracking.

Say you have a view create or replace view v1 as

    select * from t1;

but T1 is actually a public synonym to a table in someone else's schema. The validity of this view is dependent on the fact that there is no object named T1 in your schema; so
Oracle creates a 'non-existent' object in your schema that the view can depend on.

Then, when you create an object called T1 in your schema, this causes the elimination of the 'non-existent' object, which automatically causes the invalidation and recompilation of the view to use your table.
</quote>

--
Jonathan Lewis
http://www.jlcomp.demon.co.uk

Next Seminars
 UK  Sept
 Australia August
 Malaysia September
 USA x 2  November

http://www.jlcomp.demon.co.uk/seminar.html

Jan Gelbrich wrote in message ...


>> If it's in v$access, it is probably there for

>> negative dependency checking.  See a note

>> I wrote about a week ago.

>>

>> Search google on this newsgroup for

>>     NON-EXISTENT

>> or possibly

>>     NONEXISTENT.

>>

>Thank You *very* much for your FAQ list tip, Jonathan !
>