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

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."
Date: 2010-10-29 00:57:36
Message-ID: AANLkTinEqV5U7wqnQRcGMdNQ-LkFNYWq6BJrHQGzo1qY@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Oct 28, 2010 at 8:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Josh Kupershmidt" <schmiddy(at)gmail(dot)com> writes:
>> I noticed that Postgres in many cases will happily tokenize WHERE clauses
>> having no space between a condition and "AND" or "OR".
>
> This has nothing to do with AND or OR.  Any situation where you have
> some digits followed by something that can't be part of a number will
> be lexed as two separate tokens.

Yeah, I hadn't tried to pinpoint how widespread this feature/bug is in
the syntax. Though note, you can see this with e.g. text columns as
well, such as in:
SELECT * FROM mytab WHERE mycol = 'abc def'AND true;

Josh

In response to

Browse pgsql-bugs by date

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