Gagan Goel 7c8b502dc2 Fix regression in a query involving an aggregate function on a ...

non-wide decimal column in the HAVING clause.

In buildAggregateColumn(), if an aggregate function (such as avg)
is applied on a non-wide decimal column, we were setting the precision
of the resulting column as -1. This later down in the execution got
converted to 255 as in some cases, precision is stored as uint8_t.
The predicate operations on a DECIMAL column has logic that uses
the wide Decimal::s128value field if precision > 18. This logic incorrectly
used the Decimal::s128value instead of the correct value stored in the
narrow Decimal::value field, since precision of the Decimal column
was 255. The fix is to set the aggregate column precision to
datatypes::INT64MAXPRECISION (18) in buildAggregateColumn() when the
aggregate is applied on a non-wide decimal column.

This commit also partially fixes -Wstrict-aliasing GCC warnings.

2021-06-22 11:11:34 +00:00

..

CMakeLists.txt

MCOL-641 Initial support for ORDER BY on wide DECIMALs.

2020-11-18 13:51:26 +00:00

dataconvert.cpp

Fix regression in a query involving an aggregate function on a

2021-06-22 11:11:34 +00:00

dataconvert.h

MCOL-4498 LIKE is not collation aware

2021-03-22 20:42:01 +04:00

tdriver.cpp

Reformat all code to coding standard

2017-10-26 17:18:17 +01:00