| From: | deststar <deststar(at)blueyonder(dot)co(dot)uk> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)postgresql(dot)org> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: WHERE of an AGGREGATE ... |
| Date: | 2003-06-14 23:58:03 |
| Message-ID: | 1055635083.2816.6.camel@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Isn't that what the having clause is about?
- Stuart
On Sun, 2003-06-15 at 00:31, The Hermit Hacker wrote:
> I have a query that looks like:
>
> SELECT SUM(bytes) AS traffic
> FROM traffic_table
> GROUP BY ip;
>
> I want to narrow that SELECT down to a subset, like:
>
> SELECT SUM(bytes) AS traffic
> FROM traffic_table
> WHERE traffic < ( 100 * 1024 * 1024 )
> GROUP BY ip;
>
> which, of course, won't work, cause I need to do the GROUP BY before I do
> the WHERE ... but there has to be a way of coding that so that it does
> work :(
>
> I'm overlooking something obvious here ... I think?
>
> Thanks ...
>
> Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
> Systems Administrator @ hub.org
> primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2003-06-15 00:39:23 | Re: WHERE of an AGGREGATE ... |
| Previous Message | The Hermit Hacker | 2003-06-14 23:31:50 | WHERE of an AGGREGATE ... |