| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Moshe Jacobson <moshe(at)neadwerx(dot)com> |
| Cc: | 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:06:39 |
| Message-ID: | 20130528200639.GI8597@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
* 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.
My general feeling is that we should either document it *as* legacy
or add it to the "list-of-things-to-break-in-10.0". :)
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2013-05-28 20:11:11 | Re: Strange behavior of "=" as assignment operator |
| Previous Message | Moshe Jacobson | 2013-05-28 19:53:15 | Strange behavior of "=" as assignment operator |