Re: Idea: Avoid JOINs by using path expressions to follow FKs
Julien Rouhaud <rjuju123@gmail.com>
From: Julien Rouhaud <rjuju123@gmail.com>
To: Joel Jacobson <joel@compiler.org>
Cc: Isaac Morland <isaac.morland@gmail.com>,
Vik Fearing <vik@postgresfriends.org>, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-03-31T17:16:44Z
Lists: pgsql-hackers
On Wed, Mar 31, 2021 at 5:19 PM Joel Jacobson <joel@compiler.org> wrote: > > If using the -> notation, you would only need to manually > inspect the tables involved in the remaining JOINs; > since you could be confident all uses of -> cannot affect cardinality. Talking about that, do you have some answers to the points raised in my previous mail, which is how it's supposed to behave when a table is both join using your "->" syntax and a plain JOIN, how to join the same table multiple time using this new syntax, and how to add predicates to the join clause using this new syntax. > I think this would be a win also for an expert SQL consultant working > with a new complex data model never seen before. By experience if the queries are written with ANSI JOIN it's not really a problem. And if it's a new complex data model that was never seen, I would need to inspect the data model first anyway to understand what the query is (or should be) doing.
Commits
-
Clean up generation of default names for constraints, indexes, and serial
- 45616f5bbbb8 8.0.0 cited