From: | "Robert Hostetter" <robert(at)newcovsoft(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #2203: Group by, suggested "feature" |
Date: | 2006-01-23 14:56:52 |
Message-ID: | 20060123145652.C7D2DF0A2F@svr2.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 2203
Logged by: Robert Hostetter
Email address: robert(at)newcovsoft(dot)com
PostgreSQL version: 8.1
Operating system: CentOS 4.1
Description: Group by, suggested "feature"
Details:
I'm sure this will be considered a missing feature and not a bug, I know I
would. We are converting from MySQL to PostgreSQL, which is a huge project.
But one minor irritation we've noticed is the group by handling in
PostgreSQL. If you group by a primary key for a table, you still have to
include all the other columns you SELECT from that row, even though its
guaranteed uniuqe because its a primary key. I understand requiring the
other columns when you aren't guaranteed uniqueness, but in cases of a group
by on a unique column you shouldn't need to include the rows, its
repetitive, and makes porting harder for no reason. Also on a similar note,
you can't group by any column you don't select.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-01-23 17:26:04 | Re: BUG #2196: Useless RECHECK on RTREE index |
Previous Message | Jacques Gollion | 2006-01-23 11:40:43 | BUG #2198: Now returns always same date and time during a session |