On MySQL5.7.3, we released a new semi-synchronous feature which brings the advantage of stronger data integrity and durability. Please allow me to introduce you the feature.

I suppose you already know what semi-synchronous replication is. If that is not true, you can check Seim-Synchronous Replication chapter on MySQL reference manual. It describes semi-synchronous replication clearly, so I don't repeat it here again. Make Data Durable on More Than One Slaves The new feature allows users to set how many slaves the transaction(its binary events) should be replicated to before externalizing it to users. In other words, semisync master makes the transaction to wait until receiving acknowledgements from those many slaves. The simple process is demonstrated below. …

We are pleased to announce that MySQL Enterprise Monitor 3.0.4 is now available for download on the My Oracle Support (MOS) web site. It will also be available via the Oracle Software Delivery Cloud with the December update in about 1 week. This is a maintenance release that adds a few features and fixes a number of bugs. You can find more information on the contents of this release in the change log.

You will find binaries for the new release on My Oracle Support. Choose the "Patches & Updates" tab, and then use the "Product or Family (Advanced Search)" feature.

You will also find the binaries on the Oracle Software Delivery Cloud in approximately 1 week. Choose "MySQL Database" as the Product Pack and you will find the …

Hi Gavin,

I have edited the script and added command to stop mysql server to get the clean backup. Thank you very much for correcting me.

Thanks,
Ramesh

December 5, 2013 By Severalnines

Thanks to everyone who attended yesterday’s webinar; if you missed the sessions or would like to watch the webinar again & browse through the slides, they are now available online.

Thanks again to our speaker, Seppo Jaakola from Codership, the creators of Galera Cluster, for this in-depth talk on Galera Cluster Best Practices - Zero Downtime Schema Changes.

Webinar topics covered

• How to perform Zero Downtime Schema Changes
• 2 main methods: TOI and RSU
• Total Order Isolation: predictability and consistency
• Rolling Schema Upgrades
• pt-online-schema-change
…

In MySQL Replication, users can filter statements either at master (using --binlog-* startup options) or at the slave (using --replicate-* startup options). Prior to MySQL-5.7.3, users could set these filtering rules either through command line parameters or by using my.cnf file. In either case MySQL server must be restarted in order to change the filtering rules. It is not easy to restart MySQL server in real time scenarios (because of downtime issues and also loss of buffer cache resulting in performance problems). It is always helpful having a way to dynamically configure these filtering rules. Particularly in environments where slaves are configured dynamically to replicate certain databases or tables based on load and usage.

In MySQL-5.7.3, a new command "CHANGE REPLICATION FILTER" has been introduced through which users can change the *slave* side replication filters dynamically without the need for restarting the …

I recently updated my workstation to run MySQL 5.6.13. It didn't take very long for things to start breaking, and since I couldn't find any other information about this on the web, I figured this may be useful to someone else.

The main error that started popping up was:

Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'my_bool' at row 1' in test.php

This exception happens under the condition that you use PDO, prepared statements and booleans.

The easiest way to replicate this, is as follows:

<?php

$pdo = new PDO('mysql:host=localhost;dbname=test','root');
$pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);

$pdo->exec(<<<SQL
CREATE TEMPORARY TABLE foo (
   my_bool BOOLEAN
)
SQL
);

$stmt = $pdo->prepare('INSERT …

I recently updated my workstation to run MySQL 5.6.13. It didn't take very long for things to start breaking, and since I couldn't find any other information about this on the web, I figured this may be useful to someone else.

The main error that started popping up was:

Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[HY000]: General error: 1366 Incorrect integer value: '' for column 'my_bool' at row 1' in test.php

This exception happens under the condition that you use PDO, prepared statements and booleans.

The easiest way to replicate this, is as follows:

<?php

$pdo = new PDO('mysql:host=localhost;dbname=test','root');
$pdo->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);

$pdo->exec(<<<SQL
CREATE TEMPORARY TABLE foo (
   my_bool BOOLEAN
)
SQL
);

$stmt = $pdo->prepare('INSERT …

I was intrigued by a post from David Stokes entitled MySQL and Password Security.  It discusses some new options for command line password security in MySQL 5.6.  First, I want to establish that it doesn’t really provide “security”, but then I’ll explain why that doesn’t matter. MySQL 5.6 appears to encrypt the password in a [...]

After I released maintenance release of JSON UDFs last week it is time to think about which features I should implement in upcoming major version.

Many users asked me about the possibility to explicitly specify if they want to append last element to a JSON array. This feature can be made for two functions: json_append and json_set.

I have four ideas of how to implement this. All have pros and contras.

1. 
   
2. Create new function called json_append_last which will work exactly like json_append, but it will add the element to the end of array. I.e., for JSON document {"colors": ["red", "green", "blue"]} json_append_last(doc, 'colors', 'orange') returns {"colors": ["red", "green", "blue", "orange"]}
   
   …

I’m looking forward to next week’s MySQL webinar with Robert Hodges, CEO of Continuent. We’ll be speaking on the topic “Multi-Data Center MySQL with Continuent Tungsten.”

You’re not alone if you’ve been vexed when trying to assemble multi-master, multi-site MySQL clusters. Whether that was a move from a single database server to a scalable cluster, or from a brittle MySQL replication system to a transparent, manageable database cluster.

We’ve all been there at one point or another in our careers. So learn from our experience. In our joint webinar next week (Dec. 11), Robert and I will …