| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Evan Jones <evan(dot)jones(at)datadoghq(dot)com> |
| Subject: | Re: Consider \v to the list of whitespace characters in the parser |
| Date: | 2023-07-03 10:17:10 |
| Message-ID: | c6a3b443-a74d-be7b-4a56-697672367bc1@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 21.06.23 08:45, Michael Paquier wrote:
> One thing I was wondering: has the SQL specification anything specific
> about the way vertical tabs should be parsed?
SQL has "whitespace", which includes any Unicode character with the
White_Space property (which includes \v), and <newline>, which is
implementation-defined.
So nothing there speaks against treating \v as a (white)space character
in the SQL scanner.
In scan.l, you might want to ponder horiz_space: Even though \v is
clearly not "horizontal space", horiz_space already includes \f, which
is also not horizontal IMO. I think horiz_space is really all space
characters except newline characters. Maybe this should be rephrased.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2023-07-03 10:24:36 | Re: Optionally using a better backtrace library? |
| Previous Message | David Rowley | 2023-07-03 10:14:50 | Re: Todo: Teach planner to evaluate multiple windows in the optimal order |