| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, 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-28 19:47:19 |
| Message-ID: | CAMjNa7ds1HRKA8zXVm858Be--a33YvvN+XnEqi1=yXHPPVdr-Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> How about JOIN WITH?
I'm -1 on this, reusing WITH is just likely to cause confusion because WITH
can appear other places in a query having an entirely different meaning.
I'd just avoid that from the start.
>> Can with think of some other suitable reserved keyword?
>FOREIGN? Or even spell out "JOIN FOREIGN KEY".
I like the conciseness of just FOREIGN.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-12-28 19:53:14 | Re: [PROPOSAL] Make PSQLVAR on \getenv opitional |
| Previous Message | Vik Fearing | 2021-12-28 19:45:12 | Re: Foreign key joins revisited |