Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."
Date: 2010-10-29 01:29:17
Message-ID: AANLkTik-hkmbPFa=YuBX-W5vYZFg-cdcZEB_E4AVOQqG@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Oct 28, 2010 at 8:03 PM, Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> I don't really see a "bug" here. Is this causing you some kind of
> problem?

I happened to notice it while fixing up some code using multi-line
strings which had forgotten to put spaces in the SQL across lines. I
was just surprised Postgres didn't throw an error.

The only mild concern I have is if this could possibly lead to
ambiguous parsing in some situations, though I've played with some
examples and I haven't seen any yet. It would be nice to have this
behavior documented somewhere though.

Josh

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-10-29 01:52:25 Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."
Previous Message Josh Kupershmidt 2010-10-29 00:57:36 Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."