| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | rob stone <floriparob(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Parser failed to return an error |
| Date: | 2017-02-03 23:16:48 |
| Message-ID: | CAKFQuwbbowbrcSdRHtO_Ya3S1Vd1frzNJO0ZBnOjnhsSp_1r+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Feb 3, 2017 at 4:09 PM, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
>
> Sounds like psql application or JDBC specific behaviors (not sure
> expected ones though).
Its quite expected in psql. If it didn't do this certain queries would be
impossible to write and execute. As soon as you being a string psql just
continually captures text into said string until you end the string. It
gives hints that its doing this too. It won't send anything to the backend
until the complete query is written - which is good since the backend isn't
setup to deal with partial queries.
The OP just expected a higher level of artificial intelligence than what is
worth coding into this kind of application.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranjeet Singh03 | 2017-02-04 07:40:20 | Re: postgres client connection issue |
| Previous Message | Tatsuo Ishii | 2017-02-03 23:09:29 | Re: Parser failed to return an error |