| From: | Reg Me Please <regmeplease(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: NATURAL JOINs |
| Date: | 2008-10-15 16:03:25 |
| Message-ID: | 200810151803.26066.regmeplease@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Il Wednesday 15 October 2008 17:55:03 Tom Lane ha scritto:
> "Richard Broersma" <richard(dot)broersma(at)gmail(dot)com> writes:
> > For this reason, clients passing natural joins to the server can have
> > dangerous result sets returned with no warning.
>
> Yeah. A lot of people consider that NATURAL JOIN is simply a bad idea
> and shouldn't be used ever --- it's too easy to shoot yourself in the
> foot with a careless column addition or rename. Explicitly spelling out
> the join columns with ON or USING is a lot less prone to silent breakage
> after a schema change.
>
> regards, tom lane
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?
THANKS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-10-15 16:13:03 | Re: Drupal and PostgreSQL - performance issues? |
| Previous Message | Grzegorz Jaśkiewicz | 2008-10-15 15:55:46 | Re: Opptimizing projections containing unused columns |