Re: functional call named notation clashes with SQL feature

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: functional call named notation clashes with SQL feature
Date: 2010-06-04 03:09:12
Message-ID: 4C086E58.9020909@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jan Wieck wrote:
>>
>> That is a sad wart that we should never have done, IMNSHO (it was
>> before my time or I would have objected ;-) ). But beyond that, = is
>> an operator in SQL and := is never an operator, IIRC.
>
> As far as I can tell, this was already in the code when Bruce moved it
> into core as -r1.1 on my behalf (before I had commit privileges). I do
> not recall if the = as alternative to := was my idea or not. But I'm
> willing to take the blame for it because it dates back to a time where
> convenience seemed important.
>

I forgive you ;=) If my worst sin were only this bad I'd be truly happy.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2010-06-04 03:15:08 hot_standby = on
Previous Message Robert Haas 2010-06-04 02:57:05 Re: Synchronization levels in SR