[HACKERS] PL/pgSQL proposal: using list of scalars in assign stmts, fore and fors stmts

2005-12-22 Thread Pavel Stehule
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 := FOR target IN {SELECT | EXECUTE} ... LOOP target := {row|record|comma separated list of scalar vars} assign :=

Re: [HACKERS] PL/pgSQL proposal: using list of scalars in assign stmts, fore and fors stmts

2005-12-22 Thread Tom Lane
Pavel Stehule [EMAIL PROTECTED] writes: for := FOR target IN {SELECT | EXECUTE} ... LOOP target := {row|record|comma separated list of scalar vars} This part seems all right to me. assign := target2 ':=' expression target2 := {row|record|variable|'ROW(' comma separated list of scalar vars

Re: [HACKERS] PL/pgSQL proposal: using list of scalars in assign stmts, fore and fors stmts

2005-12-22 Thread David Fetter
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 := FOR target IN {SELECT | EXECUTE} ... LOOP

Re: [HACKERS] PL/pgSQL proposal: using list of scalars in assign stmts, fore and fors stmts

2005-12-22 Thread Tom Lane
David Fetter [EMAIL PROTECTED] writes: How about: target2 := {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