Received: from smtp018.mail.yahoo.com (smtp018.mail.yahoo.com [216.136.174.115]) by postgresql.org (8.11.3/8.11.4) with SMTP id f77J7n605310 for ; Tue, 7 Aug 2001 15:07:49 -0400 (EDT) (envelope-from janwieck@yahoo.com) Received: from jupiter.us.greatbridge.com (65.196.69.55) by smtp.mail.vip.sc5.yahoo.com with SMTP; 7 Aug 2001 19:07:47 -0000 X-Apparently-From: Received: (from wieck@localhost) by jupiter.us.greatbridge.com (8.11.2/8.11.2) id f77JGan02607 for pgsql-sql@PostgreSQL.org; Tue, 7 Aug 2001 15:16:36 -0400 From: Jan Wieck Message-Id: <200108071916.f77JGan02607@jupiter.us.greatbridge.com> Subject: Re: Are circular REFERENCES possible ? To: PostgreSQL SQL Date: Tue, 7 Aug 2001 15:16:36 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200108/107 X-Sequence-Number: 4328 Tom Lane wrote: > Jan Wieck writes: > > The point is that we based our implementation of foreign keys > > on the SQL3 specs. DEFERRED is not in SQL-92 AFAIK. > > I still have a concern about this --- sure, you can set up the circular > references using ALTER TABLE, but will pg_dump dump them correctly? AFAIK yes. I'm not sure if it still uses the CONSTRAINT TRIGGER syntax or does it now with ALTER TABLE. But for sure it creates all tables first, then loads the data, then activates the constraints (wouldn't work very well otherwise). Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com # _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com