Re: PL/pgSQL proposal: using list of scalars in assign stmts, fore and fors stmts - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PL/pgSQL proposal: using list of scalars in assign stmts, fore and fors stmts
Date
Msg-id 1623.1135294169@sss.pgh.pa.us
Whole thread Raw
In response to Re: PL/pgSQL proposal: using list of scalars in assign stmts, fore and fors stmts  (David Fetter <david@fetter.org>)
Responses Re: PL/pgSQL proposal: using list of scalars in assign  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
David Fetter <david@fetter.org> 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 are allowed to start
a statement with just "(x, ..." then there will be way too many
situations where the parser gets confused by slightly bad input,
resulting in way-off-base syntax error reports.  Or worse, no syntax
error, but a function that does something else than you expected.

I know that ROW is optional in the bit of SQL syntax that this proposal
is based on, but that's only because the SQL spec says we have to, not
because it's a good idea.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Oracle PL/SQL Anonymous block equivalent in postgres
Next
From: Hannu Krosing
Date:
Subject: what is the smallest working page size for postgresql