Skip to content

Tags: wydpp/mysql-server

Tags

mysql-cluster-7.6.12

Toggle mysql-cluster-7.6.12's commit message
Update license book for cluster 7.6.12

Reviewed by: Lars Tangvald <[email protected]>

Change-Id: Ia4b8a4d7d51ee30e10e05310d5eb4a0b08b83ff9
(cherry picked from commit 38d13a0ee626e1ec82c559a55754fa9911d47db4)

mysql-cluster-7.5.16

Toggle mysql-cluster-7.5.16's commit message
Update license book for cluster 7.5.16

Reviewed by: Lars Tangvald <[email protected]>

Change-Id: Ie7660e57bfbe061b8bd7f7792b675307468143c2
(cherry picked from commit cdca00ee9805d9358368d47db11ecc094f039cda)

mysql-5.7.28

Toggle mysql-5.7.28's commit message
Updated LIUM for 5.7.28

mysql-5.6.46

Toggle mysql-5.6.46's commit message
Updated the GPL LIUMs for 5.6

mysql-cluster-7.3.27

Toggle mysql-cluster-7.3.27's commit message
Update License Book for Cluster 7.3.27

mysql-cluster-8.0.18

Toggle mysql-cluster-8.0.18's commit message

mysql-8.0.18

Toggle mysql-8.0.18's commit message

mysql-cluster-7.2.39

Toggle mysql-cluster-7.2.39's commit message
Merge tag 'clone-5.5.66-build' into mysql-5.5-cluster-7.2

Change-Id: I7028f070a11184bc63cbe18e231d4c575796d26d

mysql-cluster-8.0.17

Toggle mysql-cluster-8.0.17's commit message
Bug#30031130: MYSQL SERVER SEGFAULTS AT

STD::CONDITION_VARIABLE::WAIT_FOR IN SOLARIS/X86

When a MySQL Server built with ndbcluster engine is run in a
Solaris/x86 platform, it crashes everytime when
NDB_SCHEMA_OBJECT::client_wait_completed() method is called. The
segfault happens when this method calls the
std::condition_variable::wait_for() method. This particular crash
happens only in the release builds. The reason seems to be an issue with
the compiler used in Solaris. When the optimization level -xO2 is used,
it fills the wait_for() call with a bogus code that triggers this
segfault during runtime.

Fixed the issue by making the release builds use optimization
level -xO1 for ndbcluster instead.

Change-Id: I8471970169cd971958ac2f5aa6dcb0ccd8d083a3

mysql-8.0.17

Toggle mysql-8.0.17's commit message
Bug#29904751: LIKE CONDITION FOR DATE COLUMN RETURNS ERROR

Item_func_like inherits resolve_type from Item_bool_func2 but does not
have much in common with it's parent since every comparison must be done
as strings. Also the call to set_cmp_func() is unnecesary and results in
an error when comparing temporal types with strings.
This patch fixes this error by overriding resolve_type in
Item_func_like, and by omitting the call to set_cmp_func.

Change-Id: I1cea9d5fcf54f3539016aed4cdb77501a547a5ed