Tom Lane wrote:
David Fetter <[EMAIL PROTECTED]> writes:
How about:
:= {row|record|variable|'[ROW](' comma separated list of scalar vars
')'}
instead, where the ROW is optional?
If we're going to do this at all (which I'm still agin), I think the ROW
keyword is important to minimi
David Fetter <[EMAIL PROTECTED]> writes:
> How about:
> := {row|record|variable|'[ROW](' comma separated list of scalar
> vars ')'}
> instead, where the ROW is optional?
If we're going to do this at all (which I'm still agin), I think the ROW
keyword is important to minimize ambiguity. If you a
On Thu, Dec 22, 2005 at 10:18:16AM +0100, Pavel Stehule wrote:
> Hello
>
> Now, statements EXECUTE INTO and SELECT INTO allow using list of scalars.
> FORe and FORs allow only ROW o RECORD VARIABLE. I'll plan and I did it
> enhance this stmts:
>
> := FOR IN {SELECT | EXECUTE} ... LOOP
> := {
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> := FOR IN {SELECT | EXECUTE} ... LOOP
> := {row|record|comma separated list of scalar vars}
This part seems all right to me.
> := ':='
> := {row|record|variable|'ROW(' comma separated list of scalar vars
> ')'}
As I already said on -patches,
Hello
Now, statements EXECUTE INTO and SELECT INTO allow using list of scalars.
FORe and FORs allow only ROW o RECORD VARIABLE. I'll plan and I did it
enhance this stmts:
:= FOR IN {SELECT | EXECUTE} ... LOOP
:= {row|record|comma separated list of scalar vars}
:= ':='
:= {row|record|v
