(Michael Rikmas) In the very early days of Percona Vadim wrote very nice post about GROUP_CONCAT.

(morgan tocker) Recently I found myself talking to a company that was a big user of MySQL, but just hadn’t followed all of the latest developments so closely. When the conversation went to availability I was actually not as prepared as I would have liked, and forgot about some of the (quite large) i

(Stephane Combaudon) We already discussed one to one relations in MongoDB, and the main conclusion was that you should design your collections according to the most frequent access pattern. With one to many relations, this is still valid, but other factors may come into play.

(Mats Kindahl) As you might have noticed, we have released a framework for managing farms (or grids, as Justin suggested) of MySQL servers called MySQL Fabric. MySQL Fabric is focused on being easy to use and extensible, and two extensions are currently part of the framework: one to manage high-avai

(morgan tocker) For those who were unaware, in MySQL the following statements are currently identical:

(Pavel Stìhule) I like a custom composite types – in PL/pgSQL. I don’t use a composite types in tables ever. There is a risk of some issues with composite types on client side – a client language drivers usually doesn’t work simply with custom composite types – so I use it only on server side.

(Ovais Tariq) Each day there is probably work done to improve performance of the InnoDB storage engine and remove bottlenecks and scalability issues. Hence there was another one I wanted to highlight:

(Sergey Petrunia) MySQL 5.6 added support for EXPLAIN INSERT/UPDATE/DELETE. MySQL 5.7 made some improvements to EXPLAIN code. Also, 5.7 added support for EXPLAIN FOR CONNECTION, which looks very similar to MariaDB’s SHOW EXPLAIN. I was working on putting EXPLAIN INSERT/UPDATE/DELETE into MariaDB 10.

(Jeremy Smyth) The SQL language is a bit like a toolkit for data. It consists of lots of little fiddly bits of syntax that, taken together, allow you to build complex edifices and return powerful results. For the uninitiated, the many tools can be quite confusing, and it’s sometimes difficult to dec

(Jay Janssen) Replication throughput is the measure of just how fast the slaves can apply replication (at least by my definition). In MySQL async replication this is important to know because the single-threaded apply nature of async replication can be a write performance bottleneck.