Re: [DOCS] BUG #11661: CASE ELSE is evaluated although condition is true - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: [DOCS] BUG #11661: CASE ELSE is evaluated although condition is true
Date
Msg-id CAB7nPqT-73CCO-1WnrTa51iNpBdsUmQs_5ADmVkPBWM+oRu76A@mail.gmail.com
Whole thread Raw
In response to Re: [DOCS] BUG #11661: CASE ELSE is evaluated although condition is true  (Marti Raudsepp <marti@juffo.org>)
Responses Re: [DOCS] BUG #11661: CASE ELSE is evaluated although condition is true  (Marti Raudsepp <marti@juffo.org>)
List pgsql-bugs
On Tue, Nov 11, 2014 at 4:37 PM, Marti Raudsepp <marti@juffo.org> wrote:
> Why? This page explains in what order the expressions in a SELECT
> query are processed. Aggregates can only be found in SELECT queries
> and their semantics are non-trivial, so it seems like a big omission
> to me that their relation to other clauses is not discussed.
>
> I think that's the most appropriate place for that, because GROUP BY,
> HAVING and aggregates are closely related. And their execution occurs
> after evaluating GROUP BY keys and before HAVING predicates, where
> else would one put it?
Ah, OK. I wasn't aware of this execution order. Now we could as well
split the description flow into more tiny paragraphs but this does not
seem worth it. So what about the attached then?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Marti Raudsepp
Date:
Subject: Re: [DOCS] BUG #11661: CASE ELSE is evaluated although condition is true
Next
From: Marti Raudsepp
Date:
Subject: Re: [DOCS] BUG #11661: CASE ELSE is evaluated although condition is true