Re: Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys. - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys.
Date
Msg-id 201008141302.o7ED2M506714@momjian.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys.  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Recognize functional dependency on primary keys.
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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.

OK, I put it back, but I still feel we might not need it anymore.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: Proposal / proof of concept: Triggers on VIEWs
Next
From: Tom Lane
Date:
Subject: Re: WIP partial replication patch