diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2004-07-04 02:49:04 +0000 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2004-07-04 02:49:04 +0000 |
| commit | a72dd7a9e4ddf8a9bc3443b4d10d6fef767ad066 (patch) | |
| tree | aeaa150286fa760b7c85368e67ab2e6ed24f832d /src/backend/access/gist/gistscan.c | |
| parent | f5c798ee826e4a62799e17423e4f57fcd13f112c (diff) | |
| download | postgresql-a72dd7a9e4ddf8a9bc3443b4d10d6fef767ad066.tar.gz postgresql-a72dd7a9e4ddf8a9bc3443b4d10d6fef767ad066.zip | |
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.
Diffstat (limited to 'src/backend/access/gist/gistscan.c')
0 files changed, 0 insertions, 0 deletions