Re: parser that could handle "FROM... SELECT..." as well as"SELECT... FROM..." - Mailing list pgsql-sql

From Pavel Stehule
Subject Re: parser that could handle "FROM... SELECT..." as well as"SELECT... FROM..."
Date
Msg-id CAFj8pRBh3SNM2KQYYpJ=5u_2xz=5YPoE0-yLVDffoQYsOYuQUg@mail.gmail.com
Whole thread Raw
In response to Re: parser that could handle "FROM... SELECT..." as well as"SELECT... FROM..."  (Marius Andreiana <marius.andreiana@gmail.com>)
List pgsql-sql


út 8. 10. 2019 v 9:14 odesílatel Marius Andreiana <marius.andreiana@gmail.com> napsal:
Hi Pavel,


Personally I don't see any benefit of proposed feature - It breaks portability of SQL queries (that is not high today).
It would be up to each developer which form to use. Some use only PostgreSQL and don't need portability.
Also, more DBs could parse the new format as well in the future, so this issue will go away. Need to start somewhere.

I cannot to accept this argument. Lot of developers miss global perspective, and expect what is supported by one database, then all others supports too. Lot of code is created by mistake, and if parser will be tolerant, then this mistake will not be fixed.

I don't like a idea, so Postgres is first database that breaks ANSI/SQL. If ANSI/SQL changes syntax, I'll be for it.

More, I think so current strict mode is better for readability - every body knows, where can expect some, it is easy and simple. Don't see any reason to change it.



pgsql-sql by date:

Previous
From: Marius Andreiana
Date:
Subject: Re: parser that could handle "FROM... SELECT..." as well as"SELECT... FROM..."
Next
From: Tom Lane
Date:
Subject: Re: parser that could handle "FROM... SELECT..." as well as "SELECT... FROM..."