Re: trailing junk in numeric literals

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Andreas Karlsson <andreas(at)proxel(dot)se>, 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 16:54:41
Message-ID: 4f6f8aac-d898-0bee-2d1f-654e6c648b5f@postgresfriends.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/16/21 4:32 PM, Andreas Karlsson wrote:
> 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?

Yes, all of that is in the standard.
--
Vik Fearing

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-01-16 17:03:19 Re: Alter timestamp without timezone to with timezone rewrites rows
Previous Message Tomas Vondra 2021-01-16 16:48:43 Re: PoC/WIP: Extended statistics on expressions