| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Dan S <strd911(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: counterintuitive behaviour in pl/pgsql |
| Date: | 2011-05-22 04:25:34 |
| Message-ID: | 52D6BAD5-5A1C-4009-82DE-A9FFDD35E2EC@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On May 21, 2011, at 13:44, Pavel Stehule wrote:
> 2011/5/21 Michael Glaesemann <grzm(at)seespotcode(dot)net>:
>>
>> It looks like it's just column names stomping on variable names, which is a known issue. This is why a lot of developers (including myself) have conventions of prefixing parameters and variable names (I use in_ for input parameters, v_ for internally defined variables).
>>
>
> It is not this case. There is two plpgsql variables with same name in
> one namespace - the last OUT variable has higher priority.
Yeah, I see that now (after seeing Tom's post). Thanks for the confirmation.
Michael Glaesemann
grzm seespotcode net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jun yang | 2011-05-22 04:57:34 | how to start a procedure after postgresql started. |
| Previous Message | Wei | 2011-05-21 22:08:33 | Re: Fwd: Unable to Install - "unable to write inside TEMP environment variable path" |