| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Florian Pflug <fgp(at)phlo(dot)org> |
| Cc: | 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:21:03 |
| Message-ID: | 19558.1297365663@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Florian Pflug <fgp(at)phlo(dot)org> writes:
>> This might solve the constructor problem nicely if we could do things
>> like:
>> RANGE[10,20)
>> But I have a feeling that will either cause a bizarre problem with the
>> grammar, or someone will think it's not very SQL-like.
> 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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2011-02-10 19:24:16 | Re: pl/python custom exceptions for SPI |
| Previous Message | Peter Eisentraut | 2011-02-10 19:16:09 | Re: [COMMITTERS] pgsql: Remove more SGML tabs. |