Blog

Many of you have probably already heard about the new vulnerability affecting most existing MySQL forks and versions. The bug has been patched in some of the most recent MySQL and Percona Server releases and so, at least in theory, all it takes to apply a fix is to update the MySQL or Percona Server packages to their latest versions. However, it would likely require a database restart and restarts are never particularly convenient, especially when done in a rush. But this time it is actually possible to fix the vulnerability without having to upgrade and restart your MySQL instances immediately.

Recently we got request from our customer that something is going wrong with their database and they're are getting strange errors after each insert or update to specific table. The strangeness caused by "Unknown column 'column-name' in 'field list'" message while this column was existing in this table. Our investigation shown that this was caused by trigger on the table they were trying to do the insert/update. This trigger did the insert to another table where the mentioned column didn't exist. Let me show you example:

After many months of heavy development and testing, Debian 8 (Jesse) and Ubuntu 15.04 (Vivid Vervet) were released recently. For those who already upgraded their systems and/or plan do do it in close future, we prepared builds of WebScaleSQL :-) http://repo.psce.com/download/webscalesql/deb/x86_64/vivid/ http://repo.psce.com/download/webscalesql/deb/x86_64/jessie/ You can also install it using PSCE repository.

On Tuesday  Steaphan Greene  announced that all currently-pushed changes have now been rebased onto the newly-released upstream MySQL-5.6.24.

From time to time we detect query patterns that are not well fitted to the BTree+ structures provided by InnoDB. One such situation is when you need to traverse a hierarchy (tree) or graph structure with many nodes. Specialist databases exist for this such as Neo4J. However there exists a simple solution in the form of  OQGraph which is distributed with MariaDB and is documented here.