Re: Function Parameters in GROUP BY clause cause errors - Mailing list pgsql-sql

From Tom Lane
Subject Re: Function Parameters in GROUP BY clause cause errors
Date
Msg-id 20117.1143064428@sss.pgh.pa.us
Whole thread Raw
In response to Function Parameters in GROUP BY clause cause errors  ("Davidson, Robert" <robdavid@amazon.com>)
Responses Re: Function Parameters in GROUP BY clause cause errors
List pgsql-sql
"Davidson, Robert" <robdavid@amazon.com> writes:
> ERROR:  column "em.email_creation_datetime" must appear in the GROUP BY =
> clause or be used in an aggregate function
> CONTEXT:  SQL statement " select to_char(to_timestamp(EXTRACT(HOUR FROM =
> em.email_creation_datetime) || ':' || (EXTRACT(MINUTE FROM =
> em.email_creation_datetime)::integer/ $1 ) *  $2 , 'HH24:MI'), =
> 'HH24:MI') as TheInterval from test em group by =
> to_char(to_timestamp(EXTRACT(HOUR FROM em.email_creation_datetime) || =
> ':' || (EXTRACT(MINUTE FROM em.email_creation_datetime)::integer/ $3 ) * =
>  $4 , 'HH24:MI') , 'HH24:MI')"
> PL/pgSQL function "emailbyinterval" line 3 at for over select rows

Hmm, this seems like a plpgsql deficiency.  It feels it can generate a
separate parameter symbol ($n) for each occurrence of each variable it
passes into a SQL query.  But for this query to be legal, the two
instances of IntervalMinutes have to be represented by the *same*
parameter symbol (notice they are not in the regurgitated query).

It would be more efficient anyway to not generate multiple parameters
for the same value, so we oughta fix this.

In the short run, the only workaround I can think of for you is to run
the query using EXECUTE.
        regards, tom lane


pgsql-sql by date:

Previous
From: "Daniel Caune"
Date:
Subject: Re: Custom type
Next
From: "Daniel Caune"
Date:
Subject: OUT parameter