I had a great time speaking about partitioning at the MySQL conference this week.Special thanks go out to Mattias Jonsson as well for helping answer some of the questions afterwards. The room was packed - which makes me excited for the future of MySQL partitioning!I hope everyone got something out of the session, and I'd gladly welcome any comments (positive or constructive).I plan on doing some

The complaint is the same as last year:

MySQL's internal data structures change from version to version without notice. Everyone wants abstract APIs. But MySQL engineering management executives dont want to spend the effort to implement them.

In their defense, MySQL is already so late in delivery that it's hard to justify tasking people to work on that instead.

To demolish that argument, one of the main reasons that MySQL is so slow to ship, is BECAUSE we dont have workable abstract interfaces to our internal data structures.

It seems like Jeremy wants to be MySQL community president this week :)

The announcement of a MySQL yum repository is a good one but it's slightly confusing me .. didn't Jeremy already have this with
Dorsal, where there are also 5.1 builds. So what's the difference between Dorsal and the new yum repo anyway .

But he asks for Adittionals packages , well 5.1 to start with, apart from that the CentosPlus repo also has builds for Cluster , having a uniform place go get those to would be good.

And what about builds for CGE ?
Oh and …

Tue 22 April at 9am UK, 10am Central European time, we will present probably the most popular webinar on MySQL Performance and Tuning.

We will have some real hands on examples with several tips and tricks - all that we can cover in an hour!

This is the agenda:
- Performance and Tuning Tools
- Query performance analysis and improvements
- Modelling tips
- Engine specific recommendations

Slashdot totally misinterpreted Jeremy's post about MySQL starting to build features first for their customers. As a business model , this sounds like a good way to get revenue , customers want certain features that are valuable to them , so why not let them pay for it .

The question however is how your development cycle works. Often this method of keeping code first for your paying customers , and when "the feature has been paid for" give it to the opensource community , is the wrong one.

What it comes down to is that you neglect the release early , release often and the peer review , many eyeballs see more bugs, fundamentals that made opensource projects big and stable. You are in effect stepping back to a proprietary model where you have to rush your deadlines because you have promised …

Getting data into more accessible formats is a big part of what we do at SnapLogic, so it’s always good to see someone else promoting simple over complicated. (Zen for us Python folks. )

A couple of weeks ago, Roger Costello posted a short article on Maximally Consumable Data, which triggered a discussion on the xml dev mailing list. Roger did a good job of distilling this down a a very digestable summary. Bill de hÒra summarized the same topic in a nice one-liner back in February.

At Mashup Camp 6 in March, I led an open space session on data services, under the title …

Remember yesterday? Well, I was reading that post again and realized that it's not entirely clear what Sun is actually doing with MySQL. Here's another article about the whole thing, MySQL Not Going Closed Source? that you can check out, but the gist of it is this:

MySQL Server is still (and always was) open source. The difference is not (as I might have implied yesterday) that the Enterprise product was going to be different. What's actually happening is that if you are an Enterprise customer (meaning, you're paying the big bucks for the Enterprise license), you get some extra "add-ons".

Somehow, calling them "add-ons" made a big difference (for me, anyway) in understanding what's going on: Sun is …

Wednesday night I attended a reception hosted by Sun and managed to win myself a Sun Fire X2100 M2 server!

Swag-wise, the conference was an improvement over last year, as judged by Laura Thomson’s T-Shirt index, with around a dozen shirts to be had.

Welcome to the 93th edition of Log Buffer, the weekly review of database blogs.

Conference season is upon us, so it’s been a busy week. There was the MySQL Conference & Expo, so let’s look at that.

Arjen Lentz posts about Sunday’s community dinner, including the arrival of an unexpected guest. Two photos: one of Pythian’s Paul Vallée getting some Sun; the second from the pre-conference dinner.

Zack Urlocker has a couple pieces with both photos and links to video of the keynote addresses from Marten …

While my involvement can generously be labeled as "minimal", the second edition of High Performance MySQL is slated to hit store shelves soon.

pre-order on Amazon.com

More info is available on O'Reilly.

Thanks to Baron, Peter, Vadim, and Arjen for picking up the torch to get a greatly expanded seconded edition done and out the door. There's a heck of a lot of new material in it.

(comments)