aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/analyze.c
diff options
context:
space:
mode:
authorMarc G. Fournier <scrappy@hub.org>1996-08-06 16:27:59 +0000
committerMarc G. Fournier <scrappy@hub.org>1996-08-06 16:27:59 +0000
commitab22b34891b9b9002f302710facd110ac4af7657 (patch)
tree831f9a04dd467c77bcdc1ed10e703d40a8b5f580 /src/backend/parser/analyze.c
parentc4e53a14110816d0d495bb7f00cb4e3bdee3f123 (diff)
downloadpostgresql-ab22b34891b9b9002f302710facd110ac4af7657.tar.gz
postgresql-ab22b34891b9b9002f302710facd110ac4af7657.zip
Fixes:
While a normal SELECT statement can contain a GROUP BY clause, a cursor declaration cannot. This was not the case in PG-1.0. Was there a good reason why this was changed? Are cursors being phased out? Is there any way to get data with just a SELECT (and without a DECLARE CURSOR ...)? The patch below seems to fix things. If anyone can see a problem with it, please let me know. Thanks. Submitted by: David Smith <dasmith@perseus.tufts.edu>
Diffstat (limited to 'src/backend/parser/analyze.c')
-rw-r--r--src/backend/parser/analyze.c6
1 files changed, 5 insertions, 1 deletions
diff --git a/src/backend/parser/analyze.c b/src/backend/parser/analyze.c
index cba2e211994..a99bd780fa6 100644
--- a/src/backend/parser/analyze.c
+++ b/src/backend/parser/analyze.c
@@ -7,7 +7,7 @@
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/parser/analyze.c,v 1.3 1996/07/20 07:58:04 scrappy Exp $
+ * $Header: /cvsroot/pgsql/src/backend/parser/analyze.c,v 1.4 1996/08/06 16:27:56 scrappy Exp $
*
*-------------------------------------------------------------------------
*/
@@ -509,6 +509,10 @@ transformCursorStmt(ParseState *pstate, CursorStmt *stmt)
qry->sortClause = transformSortClause(stmt->orderClause,
qry->targetList,
qry->uniqueFlag);
+ /* fix group by clause */
+ qry->groupClause = transformGroupClause(pstate,
+ stmt->groupClause);
+
qry->rtable = pstate->p_rtable;
if (pstate->p_numAgg > 0)