Re: Strange behavior of "=" as assignment operator

Hello

2013/5/28 Moshe Jacobson <moshe(at)neadwerx(dot)com>:
> On Tue, May 28, 2013 at 4:06 PM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
>>
>> Both are supported. It's not really documented as using '=' is
>> considered 'legacy' but it's also extensively used and removing it would
>> break quite a bit of code for people.
>
>
> This is crazy! By leaving it in, they are allowing my obsolescent code to
> compile and run without warning!
> This means that one day down the road, MY code is going to break because the
> developers assumed that this obsolescent behavior was OK to turn on by
> default.
> IMO they should have disabled the default acceptance of "=" and given us an
> option to enable it if our code broke.
> Not leaving it in by default.
>

There are lot of "undocumented features", that you can use in almost
all software (MS SQL, Oracle) on own risk.

> Any PG committers who can change this in 9.3?

I hope, so we will be able to identify and raise warning in 9.4.

Regards

Pavel

>
>
> --
> Moshe Jacobson
> Nead Werx, Inc. | Manager of Systems Engineering
> 2323 Cumberland Parkway, Suite 201 | Atlanta, GA 30339
> moshe(at)neadwerx(dot)com | www.neadwerx.com
>
> "Quality is not an act, it is a habit." -- Aristotle