| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com> |
| Cc: | "Reg Me Please" <regmeplease(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: NATURAL JOINs |
| Date: | 2008-10-15 18:27:32 |
| Message-ID: | dcc563d10810151127w51b0b84cx40bc67a7780faf98@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Oct 15, 2008 at 10:17 AM, Richard Broersma
<richard(dot)broersma(at)gmail(dot)com> wrote:
> On Wed, Oct 15, 2008 at 9:03 AM, Reg Me Please <regmeplease(at)gmail(dot)com> wrote:
>
>> Both are perfectly right, indeed.
>> Nonetheless, in my opinion a NATURAL JOIN exploiting the FKs
>> instead of the column names would be much more helpful and much less error
>> prone!
>>
>> As far as I know there is no way to exploit FKs in JOINs, right?
>
> Yes AFAIK, this would make postgresql's implementation of natural join
> violate the SQL standard. Perhaps you could propose an "UNNATURAL
> JOIN" syntax extension. ;)
Or a "VERY VERY NATURAL JOIN" syntax? :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-10-15 18:29:08 | slony and fill factor |
| Previous Message | Scott Marlowe | 2008-10-15 18:25:28 | Re: UPDATE and Indexes and Performance |