From: | Max Khon <fjoe(at)iclub(dot)nsu(dot)ru> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: Re: more odbc patches |
Date: | 2000-12-16 09:10:04 |
Message-ID: | Pine.BSF.4.21.0012161508060.31139-100000@iclub.nsu.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces pgsql-odbc pgsql-patches |
hi, there!
how about this?
--- cut here ---
>From cs(at)plesk(dot)com Sat Dec 16 15:08:40 2000
Date: Thu, 14 Dec 2000 17:00:43 +0600 (NOVT)
From: Constantin S. Svintsoff <cs(at)plesk(dot)com>
To: fjoe(at)iclub(dot)nsu(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ingo Luetkebohle | 2000-12-16 14:06:57 | updateable JDBC result sets? |
Previous Message | Emmanuel Charpentier,,, | 2000-12-16 08:29:04 | Coppatibility of ODBC drivers with forecoming 7.1 |
From | Date | Subject | |
---|---|---|---|
Next Message | Katsuyuki Tanaka | 2000-12-18 13:41:48 | jdbc connectint ot db |
Previous Message | Bruce Momjian | 2000-12-15 19:12:15 | Re: Re: more odbc patches |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Davis | 2000-12-16 21:09:10 | Bug fix |
Previous Message | Michael Davis | 2000-12-16 00:05:48 | Bug fix |