Re: counterintuitive behaviour in pl/pgsql - Mailing list pgsql-general

From Michael Glaesemann
Subject Re: counterintuitive behaviour in pl/pgsql
Date
Msg-id 52D6BAD5-5A1C-4009-82DE-A9FFDD35E2EC@seespotcode.net
Whole thread Raw
In response to Re: counterintuitive behaviour in pl/pgsql  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-general
On May 21, 2011, at 13:44, Pavel Stehule wrote:

> 2011/5/21 Michael Glaesemann <grzm@seespotcode.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




pgsql-general by date:

Previous
From: Ben Chobot
Date:
Subject: Re: understanding pg_locks
Next
From: jun yang
Date:
Subject: how to start a procedure after postgresql started.