| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
| Cc: | Andreas Karlsson <andreas(at)proxel(dot)se>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: trailing junk in numeric literals |
| Date: | 2021-01-16 17:10:46 |
| Message-ID: | 1736272.1610817046@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vik Fearing <vik(at)postgresfriends(dot)org> writes:
> 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.
Really? Please cite chapter and verse. AFAICS in SQL:2011 5.3 <literal>,
a numeric literal can't contain any extraneous characters, just sign,
digits, optional decimal point, and optional exponent. Hex and octal
literals are certainly not there either.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2021-01-16 17:19:08 | Re: trailing junk in numeric literals |
| Previous Message | Tom Lane | 2021-01-16 17:03:19 | Re: Alter timestamp without timezone to with timezone rewrites rows |