Forgot your password?
typodupeerror
Databases Oracle Software IT

MySQL 5.6 Reaches General Availability 47

Posted by timothy
from the magic-8-ball-says dept.
First time accepted submitter jsmyth writes "MySQL 5.6.10 has been released, marking the General Availability of version 5.6 for production." Here's more on the features of 5.6. Of possible interest to MySQL users, too, is this look at how MySQL spinoff MariaDB (from Monty, one of the three creators of MySQL) is making inroads into the MySQL market, including (as we've mentioned before) as default database system in some Linux distributions.
This discussion has been archived. No new comments can be posted.

MySQL 5.6 Reaches General Availability

Comments Filter:
  • Can anyone explain how to get mysqldump to extract & store the storage engine of the tables?

    If dumping in XML format, that info is preserved, otherwise it seems to be discarded. If a DB has a combo of MyISAM and InnoDB tables and you're backing up / replicating with mysqldump, that info is... lost. As far as I can tell. Unless I'm doing something wrong.

    If one does dump to XML, what's the best way to load that into a new slave or do a restore from it?

    Using 5.5.28 here...

    Seriously has me considering ma

    • I checked just now and the storage engine is definitely in my mysqldump script output. I am using an older version, 5.1.66.

      mysqldump --all-databases --no-data=true --routines --lock-tables=0

      Output includes a line per table that includes "ENGINE=InnoDB" or whatever storage engine I'm using.
    • If dumping in XML format, that info is preserved, otherwise it seems to be discarded. If a DB has a combo of MyISAM and InnoDB tables and you're backing up / replicating with mysqldump, that info is... lost. As far as I can tell. Unless I'm doing something wrong.

      Dunno, I never had any problems with this (5.5.x). Doing a standard mysqldump in SQL format adds the storage engine to the end of each table create statement.

    • If one does dump to XML, what's the best way to load that into a new slave or do a restore from it?

      Using 5.5.28 here...

      LOAD XML INFILE [mysql.com] might be what you're looking for.

    • by F.Ultra (1673484)
      I run 5.5.29 (the version in Ubuntu 12.04 LTS) and "mysqldump -p db table" dumps the storage engine of all my tables just fine.
  • by schneidafunk (795759) on Tuesday February 05, 2013 @11:43AM (#42797073)
    If you check out the charts, the transactions per second are tripled from 5.5, when the threads approach 60.
    • by fatp (1171151)
      More impressive is that when the threads approach 600, it will drop below 5.5.
  • Who cares? (Score:3, Insightful)

    by h8sg8s (559966) on Tuesday February 05, 2013 @11:48AM (#42797123)

    MySQL is rapidly approaching "who cares?" status. Oracle kills another one.

    • MySQL is rapidly approaching "who cares?" status. Oracle kills another one.

      This is the highest-modded post in the thread? A wholly devoid-of-information nihilistic scoff? MySQL 5.6.10 brings a ton of nice features, like online ALTER TABLE. [oracle.com] Wouldn't it be nice if there were some actual informative posts on the new MySQL release?

      By the way, even as a scoff, your post is pretty weak.

    • by Kozz (7764)

      I was pretty sure what I'd find in the comments here, and I wasn't disappointed.

      Haters gonna hate....

      • "Haters gonna hate...."

        There is very GOOD reason to distrust Oracle in this case.

        Oracle actually has a history of acquiring open source projects and then killing them off. Maybe intentionally, maybe not. But a history nonetheless. It is no wonder people are concerned.

        But they need not be. MariaDB is feature-compatible with MySQL, up to and including using the same commands to operate it, right down to the "mysql" and "mysqld" commands.

        AND it remains open source. Plus, there have been a number of performance enhancements

  • MariaDB (Score:5, Interesting)

    by eksith (2776419) on Tuesday February 05, 2013 @11:54AM (#42797173) Homepage

    Ironically is the direction MySQL should have gone after the 4.x branch. There's a whole heap of legacy baggage in the code base and Oracle -- since we know how good they're with legacy baggage -- decided to keep doing incremental changes to it (ever try putting CURRENT_TIMESTAMP as default on two fields with the second being ON UPDATE?)

    The 5.6 line is actually using a lot of improvements handed back by companies like Google, which I think initally used it for AdWords and may still be using in some capacity.

    • by robmv (855035)

      Google App Engine SQL feature is based on MySQL, I was hoping it to be based on PostgreSQL :(

    • Ironically is the direction MySQL should have gone after the 4.x branch.

      What does an ironic database do that the others don't?

      • by eksith (2776419)
        The child tables ignore parent tables on every UPDATE and return rowsAffected 0... A few years later, child tables return Foreign Key Error 1005 errno 150 on INSERT, but it's too late to because the parent tables are no more, but those ear plugs and tatoos are there forever.
  • What matters more is what db cheap hosting providers have. If they all start running MariaDB we'll see a big shift. As a distro default I'm not sure if it matters so much. I guess the other side of that coin would be WordPress, Drupal, Joomla!, and so on.

    • by wmac1 (2478314)

      They will possibly not risk. There are tens of customers with hundreds of websites and possibly thousands of applications. They will possibly be worried that changing to something else might break customer software and create a support nightmare for them.

      Their policy would be: "Why change something that works!"

  • I think you'll find that we're all moving to MariaDB these days. Thanks Oracle, everything you touch turns to shit.

  • MariaDB (Score:2, Interesting)

    by greg1104 (461138)

    Let me see if I have this right. Monty builds up MySQL AB into a functional project that a lot of people depend on. Then he sells it, cashes out big, and abandons it. And now people are falling for this again? Fool me twice, shame on me.

    • by Anonymous Coward

      Then he sells it, cashes out big, and abandons it.

      To be fair: Monty wasn't the one who sold MySQL AB. When MySQL Ab was sold, original founders didn't have a deciding vote anymore. MySQL grew because there were investments in its development.

      And now people are falling for this again? Fool me twice, shame on me.

      What exactly have you "felt for"? You have a product (MySQL, and then MariaDB) available for you under GPL licence, at no cost. Support is available, in recent years from multiple vendors (Percona

    • by gmuslera (3436)
      You have problem with the person or with the platform? No matter if Monty left MySQL AB or will abandon MariaDB in a future, both codes are GPL and you or someone else could fork or maintain it. In fact what MariaDB is doing with MySql is a good example of what can be done if Oracle becomes too greedy.
    • Not quite right...

      The timeline is more like MySQL AB sells out to Sun Microsystems who generally were not bad as stewards for open source products under their name.

      Later on Sun hits major financial trouble and Oracle gobbles them up.

      Following some appalling stewardship (hudson, openoffice, opensolaris) MariaDB took the GPL MySQL code and started work on it.

      The community moves to MariaDB for the large part and MySQL is sidelined ;)

  • by Anonymous Coward

    ..PHP. Two semi-pro tools for those Who Do Not Know Better.

    Meanwhile, professionals use Perl, Postgresql, Python and the like.

Aren't you glad you're not getting all the government you pay for now?

Working...