Re: Parser failed to return an error

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: rob stone <floriparob(at)gmail(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Parser failed to return an error
Date: 2017-02-02 19:14:26
Message-ID: CAKFQuwYrr8Qs2rJey=C=2yjktMN8U-i+wEn=vZW-6XMMaT8J8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thursday, February 2, 2017, rob stone <floriparob(at)gmail(dot)com> wrote:

>
>
> Linux roblaptop 4.9.0-1-amd64 #1 SMP Debian 4.9.2-2 (2017-01-12) x86_64
> GNU/Linux
>
>
> I was running a query like:-
>
> SELECT TO_CHAR(my_date,'dd-mm-yyyy) FROM my_table;
>
> and I forgot to type the second single quotation mark at the end of the
> mask string.
>
> Under psql it just hung and I had to Ctrl-C to go back to a prompt and
> under JDBC it hung as well and EQ just said "error", as in a failure of
> some sort.
>
> I would have expected either a 42601 error or maybe a 03000 error to
> have been returned.
>
>
At least in psql that isn't a query. It's a multi-line query fragment.
The UI is waiting for you to enter more of the query and end the string
literal that you've begun.

David J.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-02-02 22:48:05 Re: BUG #14524: Commands compare with nested subquery expressions fail with "should not reference subplan var"
Previous Message rob stone 2017-02-02 19:02:33 Parser failed to return an error