Re: BUG #1188: evaluation order of select seems to be wrong
От | Tom Lane |
---|---|
Тема | Re: BUG #1188: evaluation order of select seems to be wrong |
Дата | |
Msg-id | 1823.1089426462@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #1188: evaluation order of select seems to be wrong (Stephan Szabo <sszabo@megazone.bigpanda.com>) |
Ответы |
Re: BUG #1188: evaluation order of select seems to be wrong
|
Список | pgsql-bugs |
Stephan Szabo <sszabo@megazone.bigpanda.com> writes: > On Wed, 7 Jul 2004, Peter Eisentraut wrote: >> Am Mittwoch, 7. Juli 2004 14:58 schrieb PostgreSQL Bugs List: > Description: evaluation order of select seems to be wrong >> >> Please read this: >> http://www.postgresql.org/docs/7.4/static/sql-expressions.html#SYNTAX-EXPRESS-EVAL > The issue is that from what he said the standard may mandate that HAVING > is applied before the select list is evaluated because it's part of the > table expression. I think this is indubitably a bug. We get it right in the non-aggregate case, e.g. select teamnr,win/lose from games where lose>0; does not result in any divide-by-0 error. I think (but haven't tested) that the fix just involves altering the order of operations in nodeAgg.c so that we don't ExecProject until we have checked the qual condition. What surprises me is that no one has complained of this before. The error exists at least back to 7.0, possibly forever... regards, tom lane
В списке pgsql-bugs по дате отправления: