From: | rafal(at)zorro(dot)isa-geek(dot)com |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: foreign key restrictions |
Date: | 2008-08-10 20:11:23 |
Message-ID: | 3767fb86c51e3bf7402503a091134ead.squirrel@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> rafal(at)zorro(dot)isa-geek(dot)com writes:
>>> The reason why is that the SQL spec says so:
>>>
>>> a) If the <referenced table and columns> specifies a
>>> <reference
>>> column list>, then the set of <column name>s contained
>>> in that <reference column list> shall be equal to the
>>> set of <column name>s contained in the <unique column
>>> list> of a unique constraint of the referenced table.
>
>> I must admit, the standard is not very easy reading for me; what exactly
>> does the standarad mean by "<unique column list>":
>> 1. is that a requirement for mathematical properties of that list, or
>
> The point is it says "shall be equal to", not "shall be a superset of".
So its the "meaning nr.2". The "syntax glue" not the actual math of sets.
This is strange, I must say. But no further questions when this is a
"syntax" requirement.
Thenx,
-R
From | Date | Subject | |
---|---|---|---|
Next Message | Matt Magoffin | 2008-08-11 00:49:42 | Re: Memory use in 8.3 plpgsql with heavy use of xpath() |
Previous Message | Tom Lane | 2008-08-10 18:53:20 | Re: foreign key restrictions |