| From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql-server: Okay, I've had it with answering newbie questions about |
| Date: | 2004-07-04 02:49:19 |
| Message-ID: | 20040704024919.52C37D1B1D5@svr1.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Okay, I've had it with answering newbie questions about why plpgsql
FOR loops are giving weird syntax errors. Restructure parsing of FOR
loops so that the integer-loop-vs-query-loop decision is driven off
the presence of '..' between IN and LOOP, rather than the presence
of a matching record/row variable name. Hopefully this will make the
behavior a bit more transparent.
Modified Files:
--------------
pgsql-server/doc/src/sgml:
plpgsql.sgml (r1.38 -> r1.39)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/doc/src/sgml/plpgsql.sgml.diff?r1=1.38&r2=1.39)
pgsql-server/src/pl/plpgsql/src:
gram.y (r1.56 -> r1.57)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/pl/plpgsql/src/gram.y.diff?r1=1.56&r2=1.57)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2004-07-04 15:02:24 | pgsql-server: Made sure SET DESCRIPTOR accepts all data types including |
| Previous Message | Tom Lane | 2004-07-03 02:56:07 | pgsql-server: Fix no-longer-correct bit-pushing in |