| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: deprecating =>, take two |
| Date: | 2010-06-21 17:03:19 |
| Message-ID: | AANLkTimH2iEJW6xqhlhKJrdN_wSQMermspdIjifPBVmx@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 21, 2010 at 12:40 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Robert Haas's message of lun jun 21 12:20:59 -0400 2010:
>
>> Barring vigorous objections, I will apply these tomorrow so that we
>> can consider deprecating => as an operator name in 9.1, for better
>> compliance with the SQL standard.
>
> Maybe this is just a matter of semantics, but I thought we were going to
> deprecate => in 9.0 so that people started to avoid its use altogether.
> Why wait till 9.1 to recommend avoidance?
>
> I had imagined that 9.1 was going to ban => altogether.
Sorry, bad phrasing on my part. Your understanding matches mine.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-06-21 17:04:17 | Re: deprecating =>, take two |
| Previous Message | Guillaume Lelarge | 2010-06-21 16:46:36 | Cannot cancel the change of a tablespace |