Re: trailing junk in numeric literals

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Vik Fearing <vik(at)postgresfriends(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: trailing junk in numeric literals
Date: 2021-01-16 15:32:10
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 1/16/21 2:02 PM, Vik Fearing wrote:
> I am in favor of such a change so that we can also accept 1_000_000
> which currently parses as "1 AS _000_000" (which also isn't compliant
> because identifiers cannot start with an underscore, but I don't want to
> take it that far).
> It would also allow us to have 0xdead_beef, 0o_777, and 0b1010_0000_1110
> without most of it being interpreted as an alias.

That would be a nice feature. Is it part of the SQL standard?


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2021-01-16 15:41:20 Re: recovering from "found xmin ... from before relfrozenxid ..."
Previous Message Anastasia Lubennikova 2021-01-16 15:11:29 Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits