Overview

In the last few months, we have seen more and more discussion on the use of Galera solution for MySQL Clustering.

I have being one of those that had heavily test and implement Galera solution, actually with quite good results and I have also presented SOME of them at Oracle Connect.

On the other side I have be work with MySQL NDB for years (at least from 2007) at many customers site, from simple to complex setups.

So also if I cannot consider myself as mega expert, I think to have some good experience and insight on both platform.

The point here is that I was not happy in reading some articles comparing the two, not because the kind of tests, or results.

Not because I prefer this or that, but simply because, from my point of view, it does not make any sense …

I like using OS X's built-in packages where possible, but unfortunately Apple is way behind with their PHP package, having it locked on 5.3.15. In the past I've seen people use tools like Mamp, or Xampp to provide this for them, but frankly I'm not a big fan of these tools.

Homebrew provides a solution. Homebrew is OS X missing package manager, and it's an absolute great tool to work with. Getting started with it is a bit harder, as there's a few bigger dependencies you need, such as an up-to-date XCode installation. Once you've installed homebrew, it's a matter of running the following commands:

1. brew tap homebrew/dupes
2. brew tap josegonzalez/homebrew-php
3. brew install php54 --with-mysql
…

I like using OS X's built-in packages where possible, but unfortunately Apple is way behind with their PHP package, having it locked on 5.3.15. In the past I've seen people use tools like Mamp, or Xampp to provide this for them, but frankly I'm not a big fan of these tools.

Homebrew provides a solution. Homebrew is OS X missing package manager, and it's an absolute great tool to work with. Getting started with it is a bit harder, as there's a few bigger dependencies you need, such as an up-to-date XCode installation. Once you've installed homebrew, it's a matter of running the following commands:

brew tap homebrew/dupes
brew tap josegonzalez/homebrew-php
brew install php54 --with-mysql 
brew install php54-memcached
brew install …

I like using OS X's built-in packages where possible, but unfortunately Apple is way behind with their PHP package, having it locked on 5.3.15. In the past I've seen people use tools like Mamp, or Xampp to provide this for them, but frankly I'm not a big fan of these tools.

Homebrew provides a solution. Homebrew is OS X missing package manager, and it's an absolute great tool to work with. Getting started with it is a bit harder, as there's a few bigger dependencies you need, such as an up-to-date XCode installation. Once you've installed homebrew, it's a matter of running the following commands:

brew tap homebrew/dupes
brew tap josegonzalez/homebrew-php
brew install php54 --with-mysql 
brew install php54-memcached
brew install …

Ernie Souhrada has a great writeup called The Optimization That (Often) Isn’t: Index Merge Intersection. It talks about how MySQL can perform an "index merge" in order to use more than one index.

For example, if you have an OR in your WHERE clause, and each of the conditions are indexable, MySQL can perform each index lookup separately, and then do a union on the results.  Similarly, if you

Best practise to store boolean values in MySQL

The most simple and best solution is to use BIT (MySQL 5.0.3 and higher). With the Bit data type you can store M-bit values, if you just want a single boolean use a BIT(1). Otherwise, according to the MySQL manual you can use bool and boolean which are at the moment aliases of tinyint(1) and will work as good as the BIT(1).

Other options:

char(1):

A bit or a tinyint convert easily in true or false when you map the field in your program which finaly uses the data, If you use char you would have to do the mapping

Enum:

UGLY…. avoid enum from this reasons

Some links

…

In the last poll we discovered some 90% of responders run MySQL on Linux which is not totally a surprise. Number of people asked me to do the followup pool to see what specific Linux distributions are most popular in MySQL space hence this is the poll for today.

Please answer what Linux Distribution you’re using for your production environment. You can select more than one. If your Linux distribution is missing please ether select the closest in the list or add the comment so I can add it to the pool.

Note: There is a poll embedded within this post, please visit the site to participate in this post's poll.

The post What Linux Distribution do you use to …

Prior to version 5.0, MySQL could only use one index per table in a given query without any exceptions; folks that didn’t understand this limitation would often have tables with lots of single-column indexes on columns which commonly appeared in their WHERE clauses, and they’d wonder why the EXPLAIN plan for a given SELECT would show N possible index choices but only one index actually used.

To some extent, MySQL 5.0 and later changed this situation with the introduction of the “index merge” optimizer plan. The basic idea behind index merge is that for certain types of queries which contain WHERE clauses with columns that had single-column indexes on them, MySQL could sometimes make use of the multiple indexes. For instance, “SELECT foo FROM bar WHERE indexed_colA = X OR indexed_colB = Y” might use the index merge union algorithm, which would *simultaneously* (this is important, as we will see below) scan the indexes on …

Back when Sun Microsystems was setting, some of the programmers who had been involved with the popular and well-known open source MySQL database started a fork of the project called MariaDB.

read more

Thanks, awesome site.