Skip site navigation (1) Skip section navigation (2)

Re: json api WIP patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: json api WIP patch
Date: 2013-02-01 00:12:03
Message-ID: 8716.1359677523@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Thu, Jan 31, 2013 at 4:20 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>> On 01/31/2013 05:06 PM, Peter Eisentraut wrote:
>>> I would like to not create any -> operators, so that that syntax could
>>> be used in the future for method invocation or something similar (it's
>>> in the SQL standard).

>> This is the first time I have heard that we should stay away from this. We
>> have operators with this name in hstore, which is why I chose it.

I'm not happy about this either.  It's bad enough that we're thinking
about taking away =>, but to disallow -> as well?  My inclination is to
just say no, we're not implementing that.  Even if we remove the contrib
operators named that way, it's insane to suppose that nobody has chosen
these names for user-defined operators in their applications.

> quick off-topic aside: is colon (:) reserved for any purpose as an
> operator in SQL?

We disallow it as an operator character, because of the conflict with
parameter/variable syntax in ecpg and psql.  It was allowed before
PG 7.0, IIRC.

			regards, tom lane


In response to

Responses

pgsql-hackers by date

Next:From: David E. WheelerDate: 2013-02-01 00:16:12
Subject: Re: json api WIP patch
Previous:From: Merlin MoncureDate: 2013-01-31 23:35:47
Subject: Re: json api WIP patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group