Re: trailing junk in numeric literals - Mailing list pgsql-hackers

From Tom Lane
Subject Re: trailing junk in numeric literals
Date
Msg-id 1850223.1609188899@sss.pgh.pa.us
Whole thread Raw
In response to trailing junk in numeric literals  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: trailing junk in numeric literals
List pgsql-hackers
Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
> I was surprised to find that this doesn't error:
> => select 100a;
>    a
> -----
>   100

> I suspect this and similar cases used to error before aliases without AS 
> were introduced.  But now this seems possibly problematic.  Should we 
> try to handle this better?

Meh.  I think you'd get more brickbats than kudos if you start insisting
on a space there.

I'm too lazy to try to decipher the SQL spec right now, but ISTR that
it insists on whitespace between a numeric literal and an identifier.
So strictly speaking this SQL code is nonstandard anyway.  But our
lexer has always been forgiving about not requiring space if it's
not logically necessary to separate tokens.  I doubt trying to
change that would improve matters.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: trailing junk in numeric literals
Next
From: Peter Geoghegan
Date:
Subject: Re: New IndexAM API controlling index vacuum strategies