Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0N4kD007671 for ; Mon, 22 Jan 2001 23:46:13 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id XAA06897; Mon, 22 Jan 2001 23:45:45 -0500 (EST) From: Bruce Momjian Message-Id: <200101230445.XAA06897@candle.pha.pa.us> Subject: Re: Re: more odbc patches In-Reply-To: "from Max Khon at Dec 16, 2000 03:10:04 pm" To: Max Khon Date: Mon, 22 Jan 2001 23:45:45 -0500 (EST) CC: pgsql-interfaces@postgresql.org X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200101/252 X-Sequence-Number: 870 Can someone comment on this? > hi, there! > > how about this? > > --- cut here --- > >From cs@plesk.com Sat Dec 16 15:08:40 2000 > Date: Thu, 14 Dec 2000 17:00:43 +0600 (NOVT) > From: Constantin S. Svintsoff > To: fjoe@iclub.nsu.ru > Subject: Bug in SQLForeignKeys() > > > Query used for checking foreign key triggers > returns too many results when there're more than one foreign > key in a table. It happens because only table's oid is used to > link between pg_trigger with INSERT check and pg_trigger with > UPDATE/DELETE check. > > I think there should be enough to add following conditions > into WHERE clause of that query: > AND pt.tgconstrname = pg_trigger.tgconstrname > AND pt.tgconstrname = pg_trigger_1.tgconstrname > > /Constantin > --- cut here --- > > /fjoe > > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026