| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys. |
| Date: | 2010-08-14 03:37:56 |
| Message-ID: | 29130.1281757076@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> I'm not sure whether there is any clear rule for what rows you get when
>> grouping by a non-PK column in mysql, but it'll let you do it.
> I understand this. The issue is how many people who complained about
> our GROUP BY behavior were grouping by something that was a primary key,
> and how many were not using a primary key? The former will no longer
> complain.
No doubt, but the TODO entry you removed is still 100% accurately
worded, and what's more the archive entry it links to clearly describes
exactly the point at issue, namely that grouping by a PK *isn't*
indeterminate. You were wrong to remove it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Doudou586 | 2010-08-14 09:31:55 | press - pr: New Directory |
| Previous Message | Bruce Momjian | 2010-08-14 03:29:44 | Re: Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hitoshi Harada | 2010-08-14 04:50:58 | Re: BUG #5608: array_agg() consumes too much memory |
| Previous Message | Bruce Momjian | 2010-08-14 03:29:44 | Re: Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys. |