From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
---|---|
To: | "Corey Huinker" <corey(dot)huinker(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Foreign key joins revisited |
Date: | 2021-12-27 08:22:22 |
Message-ID: | b75b532e-000f-41e4-8253-37b36402bffd@www.fastmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Dec 26, 2021, at 23:25, Corey Huinker wrote:
> My second guess would be:
> FROM permission p
> LEFT JOIN role AS r ON [FOREIGN] KEY [(p.col1 [, p.col2 ...])]
>
> where the key spec is only required when there are multiple foreign keys in permission pointing to role.
>
> But my first guess would be that the standards group won't get around to it.
It's a quite nice idea. It would definitively mean an improvement, compared to today's SQL.
Benefits:
* Ability to assert the join is actually performed on foreign key columns.
* Conciser thanks to not always having to specify all key columns on both sides.
However, I see one problem with leaving out the key columns:
First, there is only one FK in permission pointing to role, and we write a query leaving out the key columns.
Then, another different FK in permission pointing to role is later added, and our old query is suddenly in trouble.
/Joel
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2021-12-27 09:02:14 | Add Boolean node |
Previous Message | Teodor Sigaev | 2021-12-27 07:51:42 | CREATE TABLE ( .. STORAGE ..) |