From: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Need help with INOUT mis-understanding |
Date: | 2005-10-26 21:35:15 |
Message-ID: | 435FF693.6040309@amsoftwaredesign.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
>Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> writes:
>
>
>>I have noticed this as well, if I declare OUT params I can modify them
>>to my hearts content before they go out,
>>however if you declare it as a INOUT you can't modify it because it is
>>declared as a constant.
>>
>>
>
>Uh, I don't think so.
>
> /* input argument vars are forced to be CONSTANT */
> if (argmode == PROARGMODE_IN)
> ((PLpgSQL_var *) argvariable)->isconst = true;
>
>Can you provide a test case that misbehaves that way?
>
> regards, tom lane
>
>
>
Tom,
Maybe we are mis-communicating here.
So what you are saying is INOUT params are NOT constants and you can
modify them in the function body?
I could have sworn that did not work for me in beta1, I will try it
again in beta 4 and see if things have changed.
Thanks,
Tony Caduto
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-10-26 21:46:02 | Re: Need help with INOUT mis-understanding |
Previous Message | Tom Lane | 2005-10-26 21:23:41 | Re: Error Message |