Skip to content

Tags: lakmalv91git/mysql-server

Tags

mysql-cluster-8.0.26

Toggle mysql-cluster-8.0.26's commit message

mysql-8.0.26

Toggle mysql-8.0.26's commit message

mysql-cluster-7.6.19

Toggle mysql-cluster-7.6.19's commit message
Update License Book

Approved-by: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com>

mysql-cluster-7.5.23

Toggle mysql-cluster-7.5.23's commit message
Update License Book

Approved-by: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com>

mysql-cluster-7.4.33

Toggle mysql-cluster-7.4.33's commit message
Update License Book

Approved-by: Balasubramanian Kandasamy <balasubramanian.kandasamy@oracle.com>

mysql-5.7.35

Toggle mysql-5.7.35's commit message
Update License Book

Approved-by: Bjorn Munch <bjorn.munch@oracle.com>

mysql-cluster-8.0.25

Toggle mysql-cluster-8.0.25's commit message
Bug#32717969: Wrong result of execute prepare on 'smallint'

This problem may occur with prepared implicitly grouped SELECT
statements. When the WHERE clause is determined to be always false,
e.g. due to the actual parameter values, the result of some aggregate
functions may be picked up from the previous execution.

The reason for this is that the aggregator object for such functions
is not set up, instead the no_rows_in_result() function should be
called and set the null_value flag (at least when the aggregate function
is nullable). After inspection, it was observed that the SUM and the
GROUP_CONCAT functions missed the necessary no_rows_in_result()
implementations. These have now been implemented to call the clear()
function, which will set the null_value for the function result.

It was also detected that the NTILE function was always made nullable,
even though it can never return NULL unless the argument is NULL.
This problem was also fixed.

Reviewed by: Chaithra Gopala Reddy <chaithra.gopalareddy@oracle.com>

Change-Id: Ied8ab405a3afa520a23dd95d106f4ba7312a6f02

mysql-8.0.25

Toggle mysql-8.0.25's commit message
Bug#32717969: Wrong result of execute prepare on 'smallint'

This problem may occur with prepared implicitly grouped SELECT
statements. When the WHERE clause is determined to be always false,
e.g. due to the actual parameter values, the result of some aggregate
functions may be picked up from the previous execution.

The reason for this is that the aggregator object for such functions
is not set up, instead the no_rows_in_result() function should be
called and set the null_value flag (at least when the aggregate function
is nullable). After inspection, it was observed that the SUM and the
GROUP_CONCAT functions missed the necessary no_rows_in_result()
implementations. These have now been implemented to call the clear()
function, which will set the null_value for the function result.

It was also detected that the NTILE function was always made nullable,
even though it can never return NULL unless the argument is NULL.
This problem was also fixed.

Reviewed by: Chaithra Gopala Reddy <chaithra.gopalareddy@oracle.com>

Change-Id: Ied8ab405a3afa520a23dd95d106f4ba7312a6f02

mysql-cluster-7.6.18

Toggle mysql-cluster-7.6.18's commit message
Bug #32287863 BACKPORT THE PATCH FOR BUG #27874068 ADD SUPPORT FOR -D…

…CMAKE_BUILD_TYPE=RELEASE

Follow-up patch:
re-enable -O3 by default for RelWithDebInfo (and Release) builds on Linux.

Change-Id: Ica5190aa1d6f6539ad629d93c10e4a0fd0bcdd2d

mysql-cluster-7.5.22

Toggle mysql-cluster-7.5.22's commit message
Bug #32287863 BACKPORT THE PATCH FOR BUG #27874068 ADD SUPPORT FOR -D…

…CMAKE_BUILD_TYPE=RELEASE

Follow-up patch:
re-enable -O3 by default for RelWithDebInfo (and Release) builds on Linux.

Change-Id: Ica5190aa1d6f6539ad629d93c10e4a0fd0bcdd2d
(cherry picked from commit 6cde07847a05e12640806f005d9eb7d120440b89)