MySQL Cluster 7.4.24 has been released

2019-04-26 Thread Hery Ramilison 

Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.  This
storage engine provides:

  - In-Memory storage - Real-time performance
  - Transparent Auto-Sharding - Read & write scalability
  - Active-Active/Multi-Master geographic replication
  - 99.999% High Availability with no single point of failure
and on-line maintenance
  - NoSQL and SQL APIs (including C++, Java, http, Memcached
and JavaScript/Node.js)

MySQL Cluster 7.4 makes significant advances in performance; operational
efficiency (such as enhanced reporting and faster restarts and upgrades)
and conflict detection and resolution for active-active replication
between MySQL Clusters.

MySQL Cluster 7.4.24 has been released and can be downloaded from

  http://www.mysql.com/downloads/cluster/

where you will also find Quick Start guides to help you get your first
MySQL Cluster database up and running.

The release notes are available from

  http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

  http://www.mysql.com/products/cluster/

Enjoy !

==
Changes in MySQL NDB Cluster 7.4.24 (5.6.44-ndb-7.4.24) (2019-04-26, 
General Availability)


   MySQL NDB Cluster 7.4.24 is a new release of MySQL NDB
   Cluster 7.4, based on MySQL Server 5.6 and including features
   in version 7.4 of the NDB storage engine, as well as fixing
   recently discovered bugs in previous NDB Cluster releases.

   Obtaining MySQL NDB Cluster 7.4.  MySQL NDB Cluster 7.4
   source code and binaries can be obtained from
   https://dev.mysql.com/downloads/cluster/.

   For an overview of changes made in MySQL NDB Cluster 7.4, see
   What is New in NDB Cluster 7.4
(http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is-new-7-4.html).

   This release also incorporates all bug fixes and changes made
   in previous NDB Cluster releases, as well as all bug fixes
   and feature changes which were added in mainline MySQL 5.6
   through MySQL 5.6.44 (see Changes in MySQL 5.6.44 (2019-04-25,
   General Availability)
   (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-44.html)).


Functionality Added or Changed


 * Building with CMake3 is now supported by the
   compile-cluster script included in the NDB source
   distribution.

Bugs Fixed


 * When a pushed join executing in the DBSPJ block had to
   store correlation IDs during query execution, memory for
   these was allocated for the lifetime of the entire query
   execution, even though these specific correlation IDs are
   required only when producing the most recent batch in the
   result set. Subsequent batches require additional
   correlation IDs to be stored and allocated; thus, if the
   query took sufficiently long to complete, this led to
   exhaustion of query memory (error 20008). Now in such
   cases, memory is allocated only for the lifetime of the
   current result batch, and is freed and made available for
   re-use following completion of the batch. (Bug #29336777)
   References: See also: Bug #26995027.

 * In some cases, one and sometimes more data nodes
   underwent an unplanned shutdown while running
   ndb_restore. This occurred most often, but was not always
   restircted to, when restoring to a cluster having a
   different number of data nodes from the cluster on which
   the original backup had been taken.
   The root cause of this issue was exhaustion of the pool
   of SafeCounter objects, used by the DBDICT kernel block
   as part of executing schema transactions, and taken from
   a per-block-instance pool shared with protocols used for
   NDB event setup and subscription processing. The
   concurrency of event setup and subscription processing is
   such that the SafeCounter pool can be exhausted; event
   and subscription processing can handle pool exhaustion,
   but schema transaction processing could not, which could
   result in the node shutdown experienced during
   restoration.
   This problem is solved by giving DBDICT schema
   transactions an isolated pool of reserved SafeCounters
   which cannot be exhausted by concurrent NDB event
   activity. (Bug #28595915)

 * ndb_restore did not restore autoincrement values
   correctly when one or more staging tables were in use. As
   part of this fix, we also in such cases block applying of
   the SYSTAB_0 backup log, whose content continued to be
   applied directly based on the table ID, which could
   ovewrite the autoincrement values stored in SYSTAB_0 for
   unrelated tables. (Bug #27917769, Bug #27831990)
   References: See

Re: Assistance with trigger

2019-04-26 Thread Machiel Richards 
Please ignore my request as I have managed to figure this out.

Thank you.

had to rewrite the insert to use Old.Column1... etc... and that works quite 
well.



From: Machiel Richards 
Sent: Friday, 26 April 2019 10:48 AM
To: mysql@lists.mysql.com
Subject: Assistance with trigger

Hi All

   I am hoping this email finds all well.

I would like to request some assistance with a MySQL trigger please.

We need to implement a trigger that will in short terms make a backup of a 
row before it gets deleted.

so we have tableA and TableB (backup table).

I added a before delete trigger to insert into TABLEB select from TABLEA... 
However upon delete it inserts the whole table instead of only the single row 
being deleted.

Here is my insert and select statement :


INSERT INTO tableB (Column1,backup_date,updated_by_user,Column4) SELECT 
Column1,NOW(),`username`,Column2 from tableA;



How can I rewrite this section to only select and insert the rows that are 
actually being deleted.

Your help would be greatly appreciated as I have not been able to find the 
answer on google as yet.

Regards

Assistance with trigger

2019-04-26 Thread Machiel Richards 
Hi All

   I am hoping this email finds all well.

I would like to request some assistance with a MySQL trigger please.

We need to implement a trigger that will in short terms make a backup of a 
row before it gets deleted.

so we have tableA and TableB (backup table).

I added a before delete trigger to insert into TABLEB select from TABLEA... 
However upon delete it inserts the whole table instead of only the single row 
being deleted.

Here is my insert and select statement :


INSERT INTO tableB (Column1,backup_date,updated_by_user,Column4) SELECT 
Column1,NOW(),`username`,Column2 from tableA;



How can I rewrite this section to only select and insert the rows that are 
actually being deleted.

Your help would be greatly appreciated as I have not been able to find the 
answer on google as yet.

Regards