| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Arbitrary whitespace restrictions on range types |
| Date: | 2012-12-19 01:42:35 |
| Message-ID: | 1355881355.24766.203.camel@sussancws0025 |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, 2012-12-19 at 00:06 +0000, Peter Geoghegan wrote:
> On 18 December 2012 23:31, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> > Jeff, Hackers:
> >
> > Is there a strong reason why this has to error?
>
> Having taken a look at the range I/O routines, I surmise that it was
> just easier to write range_parse() such that whitespace is included
> within <string> tokens:
There was some discussion about it, and the decision was made to match
record literal parsing for the sake of consistency. In a record literal,
spaces are considered to be a part of the value, so they are for range
types, as well.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dmigowski | 2012-12-19 10:31:59 | BUG #7758: pg_dump does not correctly dump operators. |
| Previous Message | Peter Geoghegan | 2012-12-19 00:06:29 | Re: Arbitrary whitespace restrictions on range types |