This is a discussion on Shouldn't Natural JOINs Follow FK Constraints? within the pgsql Hackers forums, part of the PostgreSQL category; --> Howdy, I just saw this in the docs: > Finally, NATURAL is a shorthand form of USING: it forms ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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. Thanks, David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |
| Thread Tools | |
| Display Modes | |
|
|