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.
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.
Percona was pleased to provide an engaging event for MySQL community members that featured engaging tutorials, highly rated breakout sessions, a very well-attended Tuesday community networking reception sponsored by Clustrix, and keynotes from a variety of industry experts:
Oracle have just announced that MySQL Cluster Manager 1.2 is Generally Available. For anyone not familiar with MySQL Cluster Manager – it’s a command-line management tool that makes it simpler and safer to manage your MySQL Cluster deployment – use it to create, configure, start, stop, upgrade…. your cluster.
So what has changed since MCM 1.1 was released?
If you are familiar with both openark kit and common_schema, you'll notice I've incorporated some functionality already working in openark kit into common_schema, essentially rewriting what used to be a Python script into SQL/QueryScript.
What was my reasoning for rewriting good code? I wish to explain that, and provide with a couple examples.