if you are using a hierarchical query for this purpose, you might want to use the CONNECT BY NOCYCLE clause to avoid circular references ... kind regards, Lex. --------------------------------------------------------------------- Jonathan Lewis Seminar http://www.naturaljoin.nl/events/seminars.html --------------------------------------------------------------------- -----Original Message----- From: Post, Ethan [mailto:Ethan.Post@xxxxxx] Sent: Friday, November 04, 2005 19:21 To: Lex de Haan; Oracle-L Freelists Subject: RE: Circular FK's Let me just tell you a little more about why this is presently a problem. I have a request that I provide dependency trees and table load order for an application with 900+ tables. When I started writing a query to look at this the circular references became quite apparent because I can't find the top of the tree. In this case I have decided to eliminate all tables with circular references from the reporting and state that they must be loaded first and note that they have these e circular references.
BEGIN:VCARD VERSION:2.1 N:de Haan;Lex FN:Lex de Haan ORG:Natural Join B.V. TEL;WORK;VOICE:+31.30.2515022 TEL;HOME;VOICE:+31.30.2518795 TEL;CELL;VOICE:+31.62.2955714 TEL;WORK;FAX:+31.30.2523366 ADR;WORK:;;Pieter Breughelstraat 10;Utrecht;;3583 SK;Netherlands LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Pieter Breughelstraat 10=0D=0AUtrecht 3583 SK=0D=0ANetherlands URL;WORK:http://www.naturaljoin.nl EMAIL;PREF;INTERNET:lex.de.haan@xxxxxxxxxxxxxx REV:20040224T160439Z END:VCARD