Re: help with pagila - Mailing list pgsql-sql

From Walter Cruz
Subject Re: help with pagila
Date
Msg-id 32cabba0609011026r6616a73bhe80b336f18aa84ac@mail.gmail.com
Whole thread Raw
In response to Re: help with pagila  (Andrew Sullivan <ajs@crankycanuck.ca>)
Responses Re: help with pagila
Re: help with pagila
Re: help with pagila
List pgsql-sql
So I can assume that the MySQL implementation is strange? (It accepts that kind of query)

[]'s
- Walter

On 9/1/06, Andrew Sullivan < ajs@crankycanuck.ca> wrote:
On Fri, Sep 01, 2006 at 10:31:48AM -0300, Walter Cruz wrote:
> "ERROR:  column "film.description" must appear in the GROUP BY clause or be
> used in an aggregate function"
>
> If I put that column on GROUP BY everything works ok. But I want understant
> why do I need to do that. Can someone teach me, please?

You need to because everything else is being grouped or aggregated.
Otherwise, you should get one row for every match of
film.description, and that's not what you want.  (More precisely and
yet still completely imprecise, that's not even something you can
have, because of the way sets work.)

A

--
Andrew Sullivan  | ajs@crankycanuck.ca
In the future this spectacle of the middle classes shocking the avant-
garde will probably become the textbook definition of Postmodernism.
                --Brad Holland

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match

pgsql-sql by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: help with pagila
Next
From: Andrew Sullivan
Date:
Subject: Re: help with pagila