| From: | Darren Duncan <darren(at)darrenduncan(dot)net> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Range Types and extensions |
| Date: | 2011-06-07 18:40:02 |
| Message-ID: | 4DEE7082.6070102@darrenduncan.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jeff Davis wrote:
> On Mon, 2011-06-06 at 14:42 -0700, Darren Duncan wrote:
>> Can Pg be changed to support "." in operator names as long as they don't just
>> appear by themselves? What would this break to do so?
>
> Someone else would have to comment on that. My feeling is that it might
> create problems with qualified names, and also with PG's "arg.function"
> call syntax.
With respect to qualified names or "arg.function", then unless the "function"
can be symbolic, I considered your examples to be the "appear by themselves",
hence "." by itself wouldn't be a new operator, and I generally assumed here
that any multi-character operators with "." to be symbolic.
In any event, I also saw Tom's reply about DOT_DOT being a token already.
-- Darren Duncan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-06-07 18:40:44 | Re: reducing the overhead of frequent table locks - now, with WIP patch |
| Previous Message | Heikki Linnakangas | 2011-06-07 18:38:56 | Re: SIREAD lock versus ACCESS EXCLUSIVE lock |