Continuing the announcement of MySQL 6 alpha availability, here are some interesting articles on the upcoming version of MySQL.
To be really successful at working with databases, there are many different disciplines to become proficient in – things like disaster recovery, security management, data integration, and more. But there are less than a handful of things you want to be really good at; becoming super-skilled in them will help you enormously in your database career. And believe it or not, one of these key areas is data modeling and its kissing cousin, physical database design.
In this article, we discuss the XML functionality available in MySQL, with an emphasis on new features coming online in MySQL 5.1 and MySQL 6.0. We assume that you already have a working knowledge of XML, and that you know what the terms “valid” and “well-formed” mean. We also assume that you have some knowledge of XPath.
Using XML in MySQL 5.1 and 6.0
Last week Vadim from MySQL Performance Blog played with queries from TPC-H benchmarks, particularly comparing MySQL 6.0.4-alpha with 5.1. MySQL 6.0 is interesting here, as there is a lot of new changes in optimizer, which should affect execution plan of TPC-H queries. In reality only two queries (from 22) have significantly better execution time (about them in next posts), but he wants to write about the queries that execute slower in new MySQL 6.0 version.
If you had issues with subqueries in MySQL 4.1 or 5.0 and pulled away from using them I’d encourage you to try MySQL 6.0 and see if your issues are fixed or described in the documentation published.
And for the end, here are some slides on the new subquery optimizations in MySQL 6:
Once a week or so we send an email with our best content. We never bug you, we just send you our latest piece of content.
If you found any value in this post, agree, disagree, or have anything to add - please do. I use comments as my #1 signal for what to write about. Read our comment policy before commenting! Comments such as "Thank you!", "Awesome!", "You're the man!" are either marked as spam or stripped from URL.