| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Range Type constructors |
| Date: | 2011-02-10 19:45:15 |
| Message-ID: | FE845321-DAFB-4CA6-A086-20EC7025CCC3@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 10, 2011, at 11:21 AM, Tom Lane wrote:
>> It will certainly mess up syntax highlighting and matching bracket detection
>> in pretty much all text editors...
>
> Yeah. It's a cute-looking notation but surely it will cause many more
> problems than it's worth. I agree with Robert's suggestion of plain
> functions named like range_co() etc.
I could see myself using ranges in ways similar to using arrays. It should would be nice to have the equivalent of ARRAY[] and/or ARRAY() to use for ranges…
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-02-10 20:02:50 | Re: ALTER EXTENSION UPGRADE, v3 |
| Previous Message | Andrew Dunstan | 2011-02-10 19:44:09 | Re: arrays as pl/perl input arguments [PATCH] |