Introduction For a long time MySQL server supported only one trigger for every action (INSERT, UPDATE, DELETE) and timing (BEFORE or AFTER). In other words, there could be at most one trigger for every pair (action, timing). It means that a user couldn’t assign for example two BEFORE INSERT triggers for the same table t1. To workaround this restriction and allow several actions to fire on some table event, a user had to implement several stored procedures (one for each activity that would be implemented as independent trigger), create trigger for a table and call this stored procedures from the trigger. As of MySQL 5.7.2 this limitation has been removed. It means that starting the MySQL 5.7.2 a user can create for example, two BEFORE INSERT triggers, three AFTER INSERT triggers and four BEFORE UPDATE triggers for table t1. And this triggers will be called in the prescribed order determined (in generally) by the sequence in which triggers were …

MySQL 5.6 introduced a new feature called extended secondary keys. We get a lot of questions about it and find that most of them come from a few incorrect assumption. In this post I’ll try to get rid of the confusion once and for all. Famous last words… here goes:
Q1: Do I need to do anything to enable extended secondary keys?No, nothing at all. It’s on by default and I can’t see any sensible reason why you would want to disable it. However, it is possible to disable it by tuning the optimizer_switch: SET optimizer_switch=’use_index_extensions={on|off}’.

Q2: Does extended secondary keys only work with InnoDB?

No, it should work with any storage engine that uses the primary key columns as reference to the row, which means most storage engines with clustered primary keys. I say “should” because it requires a minimum of work from the storage engine provider; it must …

We just announced Percona Server 5.6.14 release, and I decided to make this build with the TokuDB 7.1 engine.
The build is available here in the TESTING area.

You are welcome to play with these binaries, but keep in mind:

• This is an experimental build and not supposed to be used in production environment
• The binaries built on Ubuntu 12.04 LTS server and may not work on other Linux distributions

The post Percona Server 5.6.14 with TokuDB 7.1 Experimental build appeared first on MySQL Performance …

You can keep up with the latest developments in MySQL software in a number of ways, including various blogs and other channels. However, for the most correct (if somewhat dry and factual) information, you can go directly to the source. 

Major Releases 

For every major release, the MySQL docs team creates and maintains a "nutshell" page containing the significant changes in that release. For the current GA release (whatever that is) you'll find it at this location:

https://dev.mysql.com/doc/mysql/en/mysql-nutshell.html

 At the moment, this redirects to the summary notes for MySQL 5.6. The notes for MySQL 5.7 are also available at that website, at the URL http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html, and …

You can keep up with the latest developments in MySQL software in a number of ways, including various blogs and other channels. However, for the most correct (if somewhat dry and factual) information, you can go directly to the source. 

Major Releases 

For every major release, the MySQL docs team creates and maintains a "nutshell" page containing the significant changes in that release. For the current GA release (whatever that is) you'll find it at this location:

https://dev.mysql.com/doc/mysql/en/mysql-nutshell.html

 At the moment, this redirects to the summary notes for MySQL 5.6. The notes for MySQL 5.7 are also available at that website, at the URL http://dev.mysql.com/doc/refman/5.7/en/mysql-nutshell.html, and …

Table of Content

• Introduction
• Prerequisites
  • System information
  • Installed packages
  • Required packages
• Upgrade the first node
  • …

System information before the upgrade:

1- Operating System: CentOS release 6.4 (64 bit)
2- Cluster system consists of 3 cluster nodes (192.168.1.251 "gcservera",192.168.1.252 "gcserverb" & 192.168.1.253 "gcserverc") and Galera Load Balancer (GLB) installed on another server (192.168.1.250 "control").

The following packages are installed on the 3 cluster nodes:

1- MySQL version: mysql-5.5.33_wsrep_23.7.6 (tarballs)
2- Galera provider version:galera-23.2.7 (RPM)
3- MyEnv version: 1.0

Notes:

- For more information about MyEnv myenv.
- You can use the normal mysql start and stop commands if you don't want to install MyEnv.
- For more information about GLB …

Tweet

Over on the codecentric blog I published an article about localizing iOS and OS X applications called "Pseudolocalization for Cocoa Apps". It is probably the first of a few, because it turned out rather long already.

At the first ever CodingSerbia conference in Novi Sad, Serbia, I did an introductory talk about how iOS development works in general, with a focus on Java developers who did not have any experience with either the tools, frameworks or even Objective-C as a language.

The slides can be viewed here:


A recording has been made and published on YouTube: