From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
Cc: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: functional call named notation clashes with SQL feature |
Date: | 2010-06-03 16:13:34 |
Message-ID: | 201006031613.o53GDY409304@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David E. Wheeler wrote:
> On Jun 3, 2010, at 8:53 AM, Dimitri Fontaine wrote:
>
> > Now that it's pretty clear from Peter that the standard is not going to
> > change its choice here, I'll vote adding a WARNING each time an operator
> > called => is created, so that we get a chance to move later on.
>
> Should support for ==> be added to hstore for 9.0? So both => and ==> will work?
I have added the idea to the 9.0 open items wiki:
http://wiki.postgresql.org/wiki/PostgreSQL_9.0_Open_Items#Code
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-03 16:16:17 | Re: Did we really want to force an initdb in beta2? |
Previous Message | David E. Wheeler | 2010-06-03 16:05:09 | Re: functional call named notation clashes with SQL feature |