| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | michael(at)aplaypowered(dot)com, pgsql-bugs(at)postgresql(dot)org, pgsql-docs <pgsql-docs(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #11661: CASE ELSE is evaluated although condition is true |
| Date: | 2014-11-11 08:26:02 |
| Message-ID: | CABRT9RAdLMs2J-Q-39wOXcaO_KTFuc2VqhXsZGArG_-F0RXFsQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-docs |
On Tue, Nov 11, 2014 at 9:52 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> 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.
Agreed.
Actually now that I read it...
+ values. All aggregate functions and their argument expressions
+ in the <command>SELECT</> and <literal>HAVING</> are evaluated.
Perhaps should be:
<command>SELECT</> and <literal>HAVING</> clauses are evaluated.
Other than that, looks good to me.
Regards,
Marti
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-11-11 08:26:55 | Re: Build broken on mips |
| Previous Message | Michael Paquier | 2014-11-11 07:52:42 | Re: [BUGS] BUG #11661: CASE ELSE is evaluated although condition is true |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-11-11 13:20:13 | Re: [DOCS] BUG #11661: CASE ELSE is evaluated although condition is true |
| Previous Message | Michael Paquier | 2014-11-11 07:52:42 | Re: [BUGS] BUG #11661: CASE ELSE is evaluated although condition is true |