Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Shouldn't Natural JOINs Follow FK Constraints?
- From: Jeff Davis <pgsql(at)j-davis(dot)com>
- To: "David E. Wheeler" <david(at)justatheory(dot)com>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Shouldn't Natural JOINs Follow FK Constraints?
- Date: Fri, 30 May 2008 14:52:39 -0700
- Message-id: <1212184359(dot)15167(dot)1(dot)camel(at)dogma(dot)ljc(dot)laika(dot)com>
On Fri, 2008-05-30 at 13:19 -0700, David E. Wheeler wrote: > Howdy, > > I just saw this in the docs: > > > Finally, NATURAL is a shorthand form of USING: it forms a USING list > > consisting of exactly those column names that appear in both input > > tables. As with USING, these columns appear only once in the output > > table. > > That sounds useful if I happen to have named my columns exactly the > same between the two tables, but couldn't a NATURAL JOIN follow the FK > constraints, instead? That would be so much more useful and much less > magical, I should think. A good point, but I'm sure the SQL standard has something to say about this, so I don't think we have much of a choice. Regards, Jeff Davis
- References:
- Shouldn't Natural JOINs Follow FK Constraints?
- From: David E. Wheeler
- Shouldn't Natural JOINs Follow FK Constraints?
- Prev by Date: Re: Core team statement on replication in PostgreSQL
- Next by Date: Re: Core team statement on replication in PostgreSQL
- Previous by thread: Shouldn't Natural JOINs Follow FK Constraints?
- Next by thread: Shouldn't Natural JOINs Follow FK Constraints?
- Indexes: