Fixed LP bug #791761.

An aggregating query over an empty set of a join of two tables
with a rejecting HAVING clause erroneously could return a row.
It could happen in the cases when the optimizer made a conclusion
that the aggregating set was empty.
Wrong results were produced because the server missed initial
setting for aggregation functions in the mentioned cases.
      

1 files changed, 1 insertions, 0 deletions

diff --git a/sql/item_sum.h b/sql/item_sum.h
index 7b6bdbabf7f..0d557a030d8 100644
--- a/sql/item_sum.h
+++ b/sql/item_sum.h
@@ -388,6 +388,7 @@ public:
   {
     return trace_unsupported_by_check_vcol_func_processor(func_name()); 
   }
+  bool clear_sum_processor(uchar *arg) { clear(); return 0; }
 };