From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Vik Fearing <vik(at)postgresfriends(dot)org>, Joel Jacobson <joel(at)compiler(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
Cc: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Foreign key joins revisited |
Date: | 2021-12-29 09:46:52 |
Message-ID: | 15396c9b-ad78-4c68-7dcb-17d3b8ece972@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28.12.21 20:45, Vik Fearing wrote:
> I don't particularly like this whole idea anyway, but if we're going to
> have it, I would suggest
>
> JOIN ... USING KEY ...
>
> since USING currently requires a parenthesized list, that shouldn't
> create any ambiguity.
In the 1990s, there were some SQL drafts that included syntax like
JOIN ... USING PRIMARY KEY | USING FOREIGN KEY | USING CONSTRAINT ...
AFAICT, these ideas just faded away because of other priorities, so if
someone wants to revive it, some work already exists.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2021-12-29 10:04:03 | Re: Converting WAL to SQL |
Previous Message | Fabien COELHO | 2021-12-29 07:42:53 | Re: psql - add SHOW_ALL_RESULTS option |