Congratulations to the openSUSE community on a successful release of openSUSE 12.3. A highlight worth mentioning is that MariaDB is now the default as opposed to MySQL. What are you waiting for, download it!

From the features list, here’s an excerpt focusing on MariaDB & MySQL:

openSUSE has moved from MySQL to MariaDB as default. MariaDB was first shipped with openSUSE 11.3 back in 2010. Over the years it proved itself and starting with 12.3 openSUSE is replacing default MySQL implementation with MariaDB. This means that whole distribution is compiled against MariaDB and in ‘M’ in LAMP means MariaDB from now. As MariaDB is a drop-in …

This is just for testing purposes, but you might want to play around with MariaDB 5.5.29 coming via the CentOS 6 repositories as mentioned in this post. Please test it out and report bugs if required. The process was simple on a fresh install:

yum update
cd /etc/yum.repos.d/
wget http://dev.centos.org/centos/6/mariadb/mariadb.repo
yum list mariadb\*
yum install mariadb-server mariadb
/etc/init.d/mysqld start

That’s it, it just works. It comes with MEMORY, CSV, MRG_MYISAM, BLACKHOLE, MyISAM, PERFORMANCE_SCHEMA, ARCHIVE, FEDERATED, InnoDB (XtraDB) and Aria.

Remember this replaces mysql-libs, and is set to replace MySQL in your install. Here’s hoping it hits mainline CentOS soon.

Related posts:

1. …

Have a look at some MySQL reference architectures

Percona’s Kenny Gryp leads a recent MySQL workshop

Percona will be in Chicago and London the week of April 8th delivering two 2-day MySQL workshops. For our MPB readers, we are offering a 15% discount. Just use MPB15A when purchasing your tickets to one or both MySQL workshops.

• Scaling and Optimization for MySQL on Monday & Tuesday, April 8 & 9
  • This MySQL workshop will cover:
    • Apply architecture scaling strategies that make the most sense, including caching, …

I will be speaking Sunday morning at the Northeast Gnu/Linuxfest in Cambridge, MA. And this year the OpenDB Camp is being held in conjunction. Plus it is a chance to meet those in the MySQL Marinate virtual class.

In MySQL 5.6 we have two new INFORMATION_SCHEMA tables for InnoDB that are likely going to cause confusion: INNODB_SYS_FIELDS and INNODB_SYS_COLUMNS. You may think these are likely to just be aliases of each other in order to make your life easier. However…

These are not the same thing. The INNODB_SYS_FIELDS table is all about key columns (fields) of InnoDB indexes, while INNODB_SYS_COLUMNS is about actual columns. This is even more confusing as within the MySQL source code, there is the Field set of objects that manipulate fields (columns) in a row.

Blegh. I’m glad it’s Friday.

Percona Server for MySQL version 5.6.10-60.2

Percona is glad to announce the release of Percona Server for MySQL 5.6.10-60.2 on March 14, 2013.  (Downloads are available here and from the experimental Percona Software Repositories). Based on MySQL 5.6.10, including all the bug fixes in it, Percona Server 5.6.10-60.2 is the third ALPHA release in the Percona Server 5.6 series. All of Percona‘s …

This week we discuss changed behavior of variables in MySQL 5.6. In ear candy we talk about a cloud-based service to play with SQL on different databases, and At the Movies is Stewart Smith of Percona talking about MySQL in the Cloud as a Service during Linux Conf Australia in Canberra.

Changed behavior of variables in 5.6
boolean variables can be set to ON/OFF 1/0 TRUE/FALSE

Variables with changes:
log_slave_updates

read more

Download PDF Presentation

There is a long list of new replication features in the latest MySQL 5.6 release including:

• Binary log group commit
• Multi-threaded slaves
• Crash-save slaves
• Global Transaction Identifier (GTID)
• Replication checksums
• Optimized row-based replication
• Time-delayed replication
• Remote binary log backup
• UUID

This presentation from the MySQL Tech Tour events in New York and Boston provides an overview and syntax examples of many of these features. The Effective MySQL: Replication Techniques in Depth also discusses many of these features in detail. Chapter 3 is …

I really don’t like running my database in “I Love Garbage” mode, so I set the following SQL_MODE: STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO, NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO, NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE, NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY Guess what WordPress does with that? It doesn’t install. If you set the SQL_MODE to empty and install WordPress, then restore the SQL_MODE, WordPress will run, but if you try to create a post you’ll see an error page that says “You are not allowed to edit this post.