Received: from ambr.mtholyoke.edu (ambr.mtholyoke.edu [138.110.1.10]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0NLoR006994 for ; Tue, 23 Jan 2001 16:50:27 -0500 (EST) (envelope-from ron.peterson@yellowbank.com) Received: from yellowbank.com (pagoda.mtholyoke.edu [138.110.30.68]) by ambr.mtholyoke.edu (8.9.1/v001215-0259) with ESMTP id QAA29294 for ; Tue, 23 Jan 2001 16:50:25 -0500 (EST) Message-ID: <3A6DFCA1.248D0979@yellowbank.com> Date: Tue, 23 Jan 2001 16:50:25 -0500 From: Ron Peterson Organization: Yellowbank X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.4.0-test9 i686) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: finding foreign keys Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/299 X-Sequence-Number: 968 Can anyone suggest a more elegant way of finding foreign keys than parsing the tgargs value returned by this query? I'd really rather do pure SQL, sans string parsing, if possible. ------------------------------------------------------------------------ -- Find tables and foreign keys CREATE VIEW foreignkeysa AS SELECT t.oid as toid, c1.relname AS relid, c2.relname AS constrrelid, t.tgargs AS tgargs FROM pg_trigger AS t, pg_class AS c1, pg_class AS c2 WHERE t.tgrelid=c1.oid AND t.tgconstrrelid=c2.oid AND t.tgfoid=1644; ------------------------------------------------------------------------ -Ron-