Re: Strange behavior of "=" as assignment operator

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Moshe Jacobson <moshe(at)neadwerx(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>, Stephen Dolan <stephen(at)neadwerx(dot)com>
Subject: Re: Strange behavior of "=" as assignment operator
Date: 2013-05-28 20:23:26
Message-ID: 51A5123E.7090202@pinpointresearch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 05/28/2013 01:06 PM, Stephen Frost wrote:
> * Moshe Jacobson (moshe(at)neadwerx(dot)com) wrote:
>> It seems that the comparison operator "=" is functioning as the assignment
>> operator ":=" in this plpgsql trigger script I wrote. I was under the
>> impression that "=" is only for comparison and not assignment. If this is
>> true, please explain the transcript below. If it's not true, where is this
>> documented? I'm using PostgreSQL 9.1.4.
> 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.
>
>

You mean legacy code as provided in the documentation examples?
http://www.postgresql.org/docs/9.3/static/plpgsql-trigger.html (see
examples 39-5 and 39-6).

Fixing the example code is probably a low-hanging-fruit place to start.
I don't have time right now or I'd submit a patch.

Cheers,
Steve

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2013-05-28 20:27:11 Re: Strange behavior of "=" as assignment operator
Previous Message Stephen Frost 2013-05-28 20:22:24 Re: Strange behavior of "=" as assignment operator