| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | "Sascha Kuhl" <yogidabanli(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Foreign key joins revisited |
| Date: | 2021-12-26 18:52:37 |
| Message-ID: | b8f75897-5bed-4056-90bb-2c2d2e3f9491@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Dec 26, 2021, at 19:33, Sascha Kuhl wrote:
> The Syntax is great. Which language does it come from. I consider it not german. But I understand it mathematically.
> Great extension.
It doesn't come from any language. But I've seen similar features in ORMs, such as the jOOQ Java project. [1]
Actually, I think jOOQ's "ON KEY" terminology might be something to take inspiration from.
In jOOQ, it's a Java method .onKey(), but I think it would look nice in SQL too:
LEFT JOIN role r ON KEY p.permission_role_id_fkey
I think it would be nice if we could simply using dot "." instead of "->" or whatever.
I think it should be possible since "ON KEY" would avoid any ambiguity in how to interpret what comes after.
We would know "permission_role_id_fkey" is a foreign key name and not a column.
Or is the grammar too sensitive for such creativity?
/Joel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sascha Kuhl | 2021-12-26 18:54:40 | Re: Foreign key joins revisited |
| Previous Message | Alvaro Herrera | 2021-12-26 16:09:18 | Re: row filtering for logical replication |