14

With the recent release of MySQL 8, I can't seem to find any information about why version numbers 6 and 7 were skipped. Anyone know?

14

According to Dave Stockes, a MySQL Community Manager for Oracle:
(from his blog post: MySQL 8 is coming)

Years ago, before the Sun Microsystems purchase of MySQL AB, there was a version of MySQL with the number 6. Sadly, it was a bit ambitious and the change of ownership left it to wither. The MySQL Cluster product has been using the 7 series for years. With the new changes for MySQL 8, developers feel they have modified it enough to bump the big number.

Wikipedia article about MySQL also has these events:

  • Sun Microsystems acquired MySQL AB in 2008.
  • Version 5.1: production release 27 November 2008 (event scheduler, partitioning, plugin API, row-based replication, server log tables)
    MySQL 5.1 and 6.0-alpha showed poor performance when used for data warehousing – partly due to its inability to utilize multiple CPU cores for processing a single query.
  • MySQL Server 6.0.11-alpha was announced on 22 May 2009 as the last release of the 6.0 line. Future MySQL Server development uses a New Release Model. Features developed for 6.0 are being incorporated into future releases.
  • Oracle acquired Sun Microsystems on 27 January 2010.
  • Work on version 6 stopped after the Sun Microsystems acquisition. The MySQL Cluster product uses version 7. The decision was made to jump to version 8 as the next major version number.

And for anyone who wants to see the code, here is a repository: MySQL 6.0 binaries and source code (6.0.11-alpha).

  • 4
    I'll add source: opensource.com/article/17/2/mysql-8-coming – Talk Nerdy To Me May 22 '18 at 16:36
  • 2
    No. 6 was meant to have a next-generation storage engine (Falcon) written by Jim Starkey who jumped ship from MySQL just after they were bought by Sun. Falcon died and (I never knew this (from above) there was a sort of a 7, and now there's 8. – Vérace May 22 '18 at 16:40
  • Meanwhile, MariaDB delivered 5.2, 5.3, 5.4. Then they got back together with 5.5. But at 5.6, MariaDB was diverging enough to avoid the same numbering; so it leaped to 10.0. – Rick James Jun 1 '18 at 22:48
  • So, why 8.0 instead of 5.8? After all, Oracle's predecessor is 5.7. 8.0 has a number of major upheavals in the core code, so it deserves being considered a "major" release. – Rick James Jun 1 '18 at 22:50
  • So MySQL skipped 6 for much the same reason PHP did. – Damian Yerrick Oct 16 '18 at 19:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.