| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
| Cc: | Jean-Christian Imbeault <jc(at)mega-bucks(dot)co(dot)jp>, postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Foreign key constraint accepted even when not same |
| Date: | 2003-09-23 00:41:21 |
| Message-ID: | 28672.1064277681@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> writes:
> On Mon, 22 Sep 2003, Jean-Christian Imbeault wrote:
>> Is it right for postgres to accept a foreign key constraint when the
>> type of the field is not the same as that of the foreign key?
> IIRC in SQL92 it's said that they need to be the same type, but in SQL99
> it says that the two types must be comparable. We basically implement the
> latter, basically using the existance of a usable equality operator as the
> determination of comparable.
Note however that performance may be poor with a cross-type foreign key
reference, if the planner is unable to figure out how to use an index
for the check queries.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mainlander | 2003-09-23 00:45:19 | TList.Sort |
| Previous Message | Stephan Szabo | 2003-09-23 00:14:50 | Re: Foreign key constraint accepted even when not same |