![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
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 |
#2
| |||
| |||
|
|
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. |
#3
| |||
| |||
|
|
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. |
![]() |
| Thread Tools | |
| Display Modes | |
| |