Re: functional call named notation clashes with SQL feature - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: functional call named notation clashes with SQL feature
Date
Msg-id 0FFF5551-7836-4815-965D-08E63FC53D48@kineticode.com
Whole thread Raw
In response to Re: functional call named notation clashes with SQL feature  (alvherre <alvherre@commandprompt.com>)
List pgsql-hackers
On May 26, 2010, at 4:09 PM, alvherre wrote:

> The problem with the => operator seems best resolved as not accepting
> such an operator in a function parameter, which sucks but we don't seem
> to have a choice.  Perhaps we could allow "=>" to resolve as the
> operator for the case the user really needs to use it; or a
> schema-qualified operator.

I think requiring schema-qualification is an acceptable compromise.

Best,

David


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Keepalive for max_standby_delay
Next
From: "David E. Wheeler"
Date:
Subject: Re: CIText and pattern_ops