From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Celia McInnis" <celia(at)drmath(dot)ca> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: timestamp group by bug??? |
Date: | 2005-03-22 18:53:59 |
Message-ID: | 10909.1111517639@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
"Celia McInnis" <celia(at)drmath(dot)ca> writes:
> By the way, as a novice, I am/was a little surprised at HAVING to do this,
> since both things in the grouping are just simple functions of the same
> underlying table variable mytimestamp.
The parser cannot be expected to understand that they are equivalent
functions though. As a counterexample imagine that one extracts the
month and the other the day-of-week; grouping by those two cases would
not yield equivalent results. When they are equivalent, the extra
GROUP BY clause is redundant, but still needed to make the query pass
the parser's spec-driven sanity checking.
> notably, the following works in mysql:
MySQL is hardly a reliable reference for correct SQL behavior ;-).
My guess is that they are simply failing to test that the query has
well-defined grouping behavior at all.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-03-22 19:17:39 | Re: dump & create with a cron job |
Previous Message | Jack Miller | 2005-03-22 18:48:10 | dump & create with a cron job |