]> granicus.if.org Git - postgresql/commit
Okay, I've had it with answering newbie questions about why plpgsql
authorTom Lane <tgl@sss.pgh.pa.us>
Sun, 4 Jul 2004 02:49:04 +0000 (02:49 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Sun, 4 Jul 2004 02:49:04 +0000 (02:49 +0000)
commita72dd7a9e4ddf8a9bc3443b4d10d6fef767ad066
treeaeaa150286fa760b7c85368e67ab2e6ed24f832d
parentf5c798ee826e4a62799e17423e4f57fcd13f112c
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.
doc/src/sgml/plpgsql.sgml
src/pl/plpgsql/src/gram.y