| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Non-decimal integer literals |
| Date: | 2021-09-07 11:13:10 |
| Message-ID: | 1e3118df-bd41-0f36-7e02-14ff31392a84@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16.08.21 17:32, John Naylor wrote:
> The one thing that jumped out at me on a cursory reading is
> the {integer} rule, which seems to be used nowhere except to
> call process_integer_literal, which must then inspect the token text to
> figure out what type of integer it is. Maybe consider 4 separate
> process_*_literal functions?
Agreed, that can be done in a simpler way. Here is an updated patch.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Non-decimal-integer-literals.patch | text/plain | 24.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2021-09-07 11:17:40 | Re: UNIQUE null treatment option |
| Previous Message | Michael Banck | 2021-09-07 10:35:40 | Re: Patching documentation of ALTER TABLE re column type changes on binary-coercible fields |