| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: hstore ==> and deprecate => |
| Date: | 2010-06-12 08:04:11 |
| Message-ID: | 1276329851.10097.4.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On fre, 2010-06-11 at 10:57 -0400, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> >>> Btw., the SQL standard also defines -> for something else, so if you
> >>> wanted to be really visionary, you could deprecate that one as an
> >>> operator at the same time.
> >>
> >> Ouch. What does it define it to mean?
>
> > Similar to C: Dereferencing a reference and accessing a member.
>
> But a reference would be a datatype no? So we could just regard that as
> an ordinary operator. I don't see a reason why it would conflict with
> use of the same operator name for other datatypes (unlike the situation
> with =>).
The right side of the -> would be an identifier, like
(some expr yielding a ref)->attribute
or
objref->method(args)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2010-06-12 10:57:38 | Re: pg_upgrade output directory |
| Previous Message | Peter Eisentraut | 2010-06-12 05:45:12 | Re: PG 9.1 tentative timeline |