Re: parser that could handle "FROM... SELECT..." as well as"SELECT... FROM..."

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: parser that could handle "FROM... SELECT..." as well as"SELECT... FROM..."
Дата
Msg-id CAFj8pRBh3SNM2KQYYpJ=5u_2xz=5YPoE0-yLVDffoQYsOYuQUg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: parser that could handle "FROM... SELECT..." as well as"SELECT... FROM..."  (Marius Andreiana <marius.andreiana@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Marius Andreiana
Дата:
Сообщение: Re: parser that could handle "FROM... SELECT..." as well as"SELECT... FROM..."
Следующее
От: Tom Lane
Дата:
Сообщение: Re: parser that could handle "FROM... SELECT..." as well as "SELECT... FROM..."