Re: [BUGS] Parser failed to return an error - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: [BUGS] Parser failed to return an error
Date
Msg-id CAKFQuwbbowbrcSdRHtO_Ya3S1Vd1frzNJO0ZBnOjnhsSp_1r+A@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] Parser failed to return an error  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List pgsql-bugs
On Fri, Feb 3, 2017 at 4:09 PM, Tatsuo Ishii <ishii@sraoss.co.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.

pgsql-bugs by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [BUGS] Parser failed to return an error
Next
From: Ranjeet Singh03
Date:
Subject: Re: [BUGS] postgres client connection issue