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

--000000000000eae62b059460ea01
Content-Type: text/plain; charset="UTF-8"

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.

--000000000000eae62b059460ea01
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Pavel,</div><div dir=3D"ltr"><br></div=
><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div dir=3D"ltr"><div class=3D"gmail_quote"><div><br></div><div>Personal=
ly I don&#39;t see any benefit of proposed feature - It breaks portability =
of SQL queries (that is not high today).</div></div></div></blockquote><div=
>It would be up to each developer which form to use. Some use only PostgreS=
QL and don&#39;t need portability.</div><div>Also, more DBs could parse the=
 new format as well in the future, so this issue will go away. Need to star=
t somewhere.</div><div><br></div><div><br></div><div><br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_=
quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div></div>
</blockquote></div></div>

--000000000000eae62b059460ea01--