This week we discuss deprecated, removed and ignored variables in MySQL 5.6. Ear Candy is about innodb_file_per_table enabled by default, and At the Movies is "Different MySQL Forks for Different MySQL Folks".
Open Database Camp will be part of the Northeast LinuxFest at Harvard University, Cambridge MA Saturday March 16th and Sunday March 17th, 2013. You can register and submit presentations on the opensqlcamp.org website.
Percona Live: MySQL Conference and Expo 2013 is being held at the Santa Clara Convention Center Monday April 22nd - Thursday April 25th.
LinuxFest Northwest will take place in Bellingham, Washington on Sat Apr 27th and Sun Apr 28th.
April 22 & 29 in Zurich
Deprecated variables in MySQL 5.6
NOTE - When we say "use X instead", these are the recommendations we could find in the MySQL manual. We have not necessarily verified if it's a valid workaround or not.
Deprecated because they are unused:
innodb_version - innodb versions are not going to have separate version numbers from MySQL, so this variable isn't needed.
- query INFORMATION_SCHEMA.ENGINES or use SHOW ENGINES INSTEAD
engine_condition_pushdown use the engine_condition_pushdown flag to optimizer_switch variable instead.
thread_concurrency - only used on Solaris. Use InnoDB variables to control how many read and write threads.
INSERT DELAYED is deprecated in MySQL 5.6, as are all of its variables and corresponding commands.
master_retry_count, use CHANGE MASTER TO ... MASTER_RETRY_COUNT instead.
innodb_additional_mem_pool_size - there are multiple innodb buffer pools, so this is no longer needed.
innodb_locks_unsafe_for_binlog - use READ COMMITTED instead, it is more flexible.
Automatic DEFAULT CURRENT_TIMESTAMP and ON UPDATE CURRENT_TIMESTAMP assignations are deprecated. See the details of the new variable to control this, explicit_defaults_for_timestamp
ignore_builtin_innodb - MySQL 5.6 does not have a plugin for InnoDB, it always uses the default, so this variable is ignored.
Other deprecated variables:
innodb_file_per_table enabled by default
Episode 36, which we talked about automatically putting innodb_file_per_table ON as the default
At the Movies
This week in At the Movies, we present the talk Sheeri did last week at Confoo entitled "Different MySQL Forks for Different Folks". There's a corresponding blog post with links"> to the websites mentioned in the talk, the PDF slides and the video itself. She explored why you'd use the different forks of MySQL and why you would not want to use them, including Drizzle, Oracle's MySQL, Percona's patch set, and MariaDB.
Where you can see us
Sheeri will present "MySQL backups" at Northeast LinuxFest in Cambridge, MA from March 16-17th. She will also be organizing Open Database Camp at the same time.
Gerry will be at the Seattle's April MySQL Meetup April Seattle MySQL Meetup We are going to have a workshop session during which one of our members is going to do a live howto. We're deciding on which tools to use for April and which ones in May. If you're in the Seattle area, we encourage you to volunteer to talk about how your company uses MySQL or propose a workshop topic that we will talk about during the meetup.
Sheeri will be at the Boston April MySQL Meetup group featuring John Zablocki, developer advocate, giving an "Intro to Couchbase: NoSQL Document Database for Interactive Applications".
Gerry will present a tutorial during the Percona Live: MySQL Conference and Expo from Monday, April 22 through Thursday April 25th. The tutorial is on Using TokuDB: A Guided Walk Through TokuDB Implementation. Many of the concepts apply to custom MySQL / MariaDB installations as well.
Gerry will also be attending LinuxFest Northwest in Bellingham, Washington Saturday April 26th and Sunday April 27th.