As an update to the previous announcement from Mar 25, 2014 please find below the updated list of events where MySQL Community team is attending and/or supporting. This time you can find not only EMEA & APAC ones but also conferences & events we are covering in the US & Canada. You are invited to meet our engineers at the events below.  

EMEA 

• NEW!! BGOUG, Sandanski, Bulgaria, June 13, 2014
  •  Georgi Kodinov will attend and speak at this local Oracle User Group event. Feel free to come.
• PHP Tour Lyon, Lyon, France, June 23-24, 2014
  • MySQL …

Thank you to the MySQL Community, on behalf of the MySQL team @ Oracle. Your bug reports, testcases and patches have helped create a better MySQL 5.6.19.

In particular:

• Thank you to Daniël van Eeden for reporting that the utility charset2html was unmaintained and obsolete. We followed Daniël's suggestion and removed it from MySQL distributions. Bug #71897.
• Thank you to Dario Kampkaspar for reporting that upgrading from 5.6.10 to a more recent 5.6 release would fail. Bug #72079.
• Thank you to Fangxin Flou for reporting that InnoDB would call memset too often. Fangxin also provided a suggested patch to fix the issue. Bug #71014.
• Thank you to Daniël van Eeden for reporting an assertion …

There will be 2 community meetups in Tokyo in Japan scheduled for June 2014. Please check and join following: 

• MySQL Casual Talks vol.6
  • Date: June 11th, 2014
  • Time: 19:00
  • Place: Oracle office, Oracle Aoyama Center, 2-5-8 Kita-Aoyama, Minato-ku, Tokyo, Japan
  • More info & Registration
• MySQL Cluster Casual Talk #2
  • Date: June 25th, 2014
  • Time: 19:00
  • Place: GMO Yours, …

We are pleased to announce another MySQL User Group meeting scheduled for June 5 in Madrid, Spain. Keith Hollman, the MySQL Principal Sales Consultant will be talking about MySQL & Oracle strategy and MySQL Cluster. A small demo of MySQL Cluster will be part of the presentation. 

Details about the event: Date: June 5, 2014 Time: 7:00 pm-8:30 pm Place: Edificio Telefonica, Gran via 28, Madrid, Entrada por C/ Valverde 2
We are looking forward to seeing you in Madrid!
See more information & registration.

Today marks a milestone in terms of the MariaDB project – going forward, the MariaDB project plans to use Github and git for source code management. The migration happens from Launchpad and the bzr tool.

The 10.1 server development (under heavy development now) will happen on Github. You can check it out here: https://github.com/MariaDB/server. Feel free to watch, star or even fork the code, and send us contributions!

Previous maria-captains should now provide their Github IDs so that they can be accorded similar status. Send the IDs to the maria-developers mailing list.

The project eventually wants to move the 10.0, 5.5, 5.3, …

Today while browsing through my emails I was very happy to read this email from Sergei Golubchik :

Hi! I'm happy to announce that MariaDB-10.1 tree has been completely migrated to github. Since now on we'll use github for the new development in MariaDB. It's https://github.com/MariaDB/server, go on, fork it, hack around, submit pull requests. [...]

In the MySQL team, we are changing the system tables currently located in the mysql schema from MyISAM to InnoDB.

Looking at this historically:

• MyISAM was the default storage engine up until MySQL 5.5.
• In 5.5 almost 4 years ago, the default storage engine changed to InnoDB, however system tables used for features such as storing privileges and timezones remained as MyISAM.

Unlike MyISAM, InnoDB is an ACID compliant storage engine, with the behaviour that once a transaction commits, modifications are able to survive power-loss or other failures. This is a solid foundation to build applications on, since developers will need to handle fewer failures. To use an example:

1. Customer places an order
2. A confirmation email is sent
3. Power is lost

Without durability, (2) could occur with no record of (1) occurring! …

If you couldn’t attend the MariaDB & MySQL Community Event in April 2014, held at the Hilton Santa Clara, fret not as there are slides and videos uploaded for you to watch at your leisure. There is likely to be at least one more community event later this year, so watch the space.

Currently on the page, you’ll find most of the talks with slides and the videos are professionally done – with slide overlays. The audio could be better on some, but for an event that was pulled together by Monty in less than 3 weeks, it’s not too shabby. You can learn What’s new in MariaDB 10, a little more about the SPIDER storage engine, more about …

In the MySQL team we are proposing to deprecate the COM_REFRESH packet in favor of specific queries to execute FLUSH commands. To provide a bit of context:

• The MySQL server protocol allows for clients to speak API commands via both a query and binary protocol interface. The set of the API commands can be seen in the MySQL Client/Server Protocol internals documentation, or very simply as they appear in a single switch statement:

  # ./sql/sql_parse.cc:1009 (simplified view)
  
    switch (command) {
  
    case COM_REGISTER_SLAVE:
    {
      /* do stuff */
      break;
    }
    case COM_QUERY:
    {
      /* parse query, do stuff */
      break;
    }
    case COM_REFRESH:
    {
     /* equivalent to running a FLUSH command */
      break;
    }
    case COM_SHUTDOWN:
    {
      kill_mysql();
      break;
    }
  }
  

• The historical advantage of having a binary …

Improving security has been a high priority for MySQL 5.7. To give you an idea of some of the changes to date, I recommend reading Todd Farmer's blog: Redefining --ssl option, Password expiration policy, AES256 encryption.

In MySQL 5.7, we are also proposing to remove the 'old' format for saving passwords. To provide some historical context:

• The old password format is a 16-byte hash and considered to be cryptographically weak. Code appears online (I won't link to it) which allows the hash to be brute-forced in …