This post originated from an RSS feed registered with Java Buzz by Russell Beattie. Original Post: MySQL Conference Wrapup Feed Title: Russell Beattie Notebook Feed URL: http://www.russellbeattie.com/notebook/rss.jsp?q=java,code,mobile Feed Description: My online notebook with thoughts, comments, links and more. Latest Java Buzz Posts Latest Java Buzz Posts by Russell Beattie Latest Posts From Russell Beattie Notebook

First, Jeremy Zawodney's new book High Performance MySQL has been published and is on Safari (if you have a subscription). Right off the bat it's very informative:

Many binary distributors of MySQL mold it to fit "their" layout. For example, the Debian distribution places the config files in /etc/mysql/, some language-specific files in /usr/share/mysql/, the executables directly into /usr/bin/, etc. It's not "the Debian way" to segregate an application's binaries; it incorporates them into the system as a whole. Likewise, in those places it does incorporate them, it does so in what may seem like an odd manner. For instance, you might expect config files to go directly into /etc/, but instead they get put in /etc/mysql/. It can be confusing if you're trying to find everything you need to modify, or if you're trying to later convert from one type of installation to the other.

The MySQL.com-supplied tarball binary packages, however, behave more like the source-compilation process. All the files - configuration files, libraries, executables, and the database files themselves - end up in a single directory tree, created specifically for the MySQL install. This is typically /usr/local/mysql, but it can be altered as needed at installation time. Because this behavior is much the same as a source-compiled installation, the available support from the MySQL community is much greater. It also makes things easier if you decide later to instead use a MySQL installation you compile from source.

I was actually disappointed to hear that 4.1 won't be going beta until next month and won't be in production until Q4!!! I was told it was going to be production *a lot* sooner (as in this week). Urgh. As I'm using the spatial indexing stuff, and it'd be nice if it was more solid. And what about 5.0? I thought 4.1 was going to become 5.0 when launched? I'm confused.

Anyways, here's some great weblog posts from the conference that I thought were interesting.

• MySQL State of the Dolphin
• MySQL at Sabre
• LiveJournal's MySQL Backend
• Introduction to MySQL Cluster
• MySQL Replication and Clustering
• The Evolution of MySQL at Yahoo
• MySQL/Innodb Performance
• MySQL and PHP Best Practices
• Stored Procedures in MySQL
• MySQL Query Browser
• Database Design Workshop

Thanks to Anthony, Mike, Jeremy and others who took the time to go to the conference and write up such detailed reports!

-Russ