| From: | Vortex <vortex25(at)gmx(dot)de> | 
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org | 
| Subject: | Re: select within aggregate? | 
| Date: | 2005-05-06 08:40:30 | 
| Message-ID: | 20050506104030.3e725437.vortex25@gmx.de | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-sql | 
On Fri, 6 May 2005 13:34:26 +0530
"Ramakrishnan Muralidharan" <ramakrishnanm(at)pervasive-postgres(dot)com> wrote:
> SELECT abc.remote_host ,  c , abc.request_uri , a.t FROM abc , ( select remote_host , count(*) as c , max( ts ) as t from abc group by remote_host ) as a 
> where a.remote_host = abc.remote_host and abc.ts = a.t
I thought about this too. But what happens if there are accidentally two
sets with same timestamp in the table? I suppose the outer select would
match both of them. But a DISTINCT should help to avoid this.
Ok, if you think this is the propper way to meet the
requirement i will do so.
Thank you for your answer!
Klaus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Gonsalves | 2005-05-06 09:14:29 | pg_dump without data | 
| Previous Message | Ramakrishnan Muralidharan | 2005-05-06 08:04:26 | Re: select within aggregate? |