Re: Parser failed to return an error

From: rob stone <floriparob(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(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-06 00:20:13
Message-ID: 1486340413.6509.1.camel@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello Jeff,
On Fri, 2017-02-03 at 13:10 -0800, Jeff Janes wrote:
> On Thu, Feb 2, 2017 at 11:14 AM, David G. Johnston <david.g.johnston@
> gmail.com> wrote:
> > On Thursday, February 2, 2017, rob stone <floriparob(at)gmail(dot)com>
> > wrote:

> 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

"EQ" is a program called ExecuteQuery. You can download the deb package
from www.executequery.org.
I use it all the time. It is written in Java.

I was testing a fairly verbose query and finding my typo took ages.
Usually running a statement using EQ and there is an error, it gives
you the character position, so you can quickly find your mistake and
try again.

Instead of reproducing the entire query I posted just the part causing
the problem. It appears Tatsuo Ishii has investigated further and
illustrated better as to what happens when the to_char mask lacks the
ending single quotation mark.

Cheers,
Rob

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Euler Taveira 2017-02-06 01:07:24 Re: plpython bug
Previous Message joel.traf 2017-02-05 21:51:58 plpython bug