From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | Wenjin Zheng <wenjin(dot)zheng(at)lsbc(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Problem with view |
Date: | 2000-04-03 21:10:36 |
Message-ID: | m12cE7I-0003kGC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I have got another problem. I have a table(table tempOne) that has two
> fields, seqid(int) and phredscore(int). They are one to many relationship,
> e.g. one seqid has many phredscore. I would like to get the row that has
> the max(phredscore). So I first created a view as follow:
> "create view maxphred as select seqid, max(phredscore) as phredscore from
> tempOne group by seqid;"
Views are known to have severe problems with aggregates and
grouping. And once again these are problems we want to
tackle with the parse-/querytree overhaul.
Oh man - this is one of the most important things I see.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-04-03 21:42:44 | Re: Problem with view |
Previous Message | Jan Wieck | 2000-04-03 21:07:53 | Re: procedure returns a tuple |