Re: Parser failed to return an error

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
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 21:10:12
Message-ID: CAMkU=1yEo0qBh6peb_4w0ZYLZ4xPO0zkKtGL=0kGva4wr99Spg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Feb 2, 2017 at 11:14 AM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> 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.
>

Also, that is indicated by the change in prompt from => to '> (assuming you
are using the default prompts).

That would seem to be bug in JDBC, though. Rob, can you provide a full
example code?
What is "EQ"?

Cheers,

Jeff

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tatsuo Ishii 2017-02-03 23:09:29 Re: Parser failed to return an error
Previous Message Tom Lane 2017-02-03 14:51:10 Re: postgres client connection issue