From: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Need help with INOUT mis-understanding |
Date: | 2005-10-26 15:09:45 |
Message-ID: | 435F9C39.4000804@amsoftwaredesign.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
>"Troy" <troy(at)hendrix(dot)biz> writes:
>
>
>>Does PL/PGSQL handle
>>INOUTS the same as ORACLE PL/SQL?
>>
>>
>
>Probably not, if the way you seem to expect it to work is like Oracle.
>An INOUT parameter isn't some sort of modifiable by-reference variable,
>it's just a shorthand for declaring an IN parameter and an OUT
>parameter.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
>
>
Tom,
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.
I would expect the behavior of a INOUT to be ths same as OUT, not the
same as a IN.
There have been many times I really could have even used IN params that
where not declared as CONST.
How difficult would it be to have INOUT params not declared as CONST?
Thanks,
Tony Caduto
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2005-10-26 15:09:58 | Re: FoxPro in WINE to Postgresql on LINUX? |
Previous Message | Tom Lane | 2005-10-26 14:54:53 | Re: Quickly calculating row size of a table? |