Re: functional call named notation clashes with SQL feature

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(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:04:26
Message-ID: FD04E171-75A6-457A-9599-4EA128B6552A@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jun 3, 2010, at 8:54 AM, Tom Lane wrote:

>> Thinking some more, what is the value of keeping => in hstore for 9.0?
>
> Backwards compatibility. You have not made any argument today that we
> have not been over many times before. I do not have time to argue
> about this today --- I have to go fix max_standby_delay.

I'm sure there's a lot of code using => in the wild. We can't just drop them without a deprecation cycle.

Best,

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2010-06-03 16:05:09 Re: functional call named notation clashes with SQL feature
Previous Message Bruce Momjian 2010-06-03 16:00:37 Re: functional call named notation clashes with SQL feature