The latest from the MySQL community

So now that you have posted some clarifications on what is going on exactly, it seems like there is less of a problem as original thought. However I must say that the the replies you posted on Jeremy's blog (and later mine as well), you let me to believe that things are quite bad indeed. Only now that I see your two posts on /, I can relax a bit again. Matthew has written a very good …

So, exactly how does one breathe life into a technical blog? My instinctive approach to such tasks—and this is a personal failing to which I freely confess—is to overthink every element of the thing: tone, style, content, title, domain name, what have you.

After a month of dithering, I was struck by the simple fact that a blog is not an astronavigation exam, so all I really need to do is to stop thinking and just...start...writing.

"But about what?"

"Whatever. You'll figure it out. Just start typing. Now."

"But what if someone thinks it sucks?"

"Someone already does. Now get to it."

"But what about my voice? I need a voice. A writer needs a voice."

[cold stare]

Anyway, after a quick survey of the more active MySQL blogs, I developed a sense of what to avoid, what to emulate and perhaps what I might add to the scene.
…

I'm pleased to announce the release of FederatedX Storage Engine 0.4! This release has transactional support as well as a wonderful new connection pool. This release is due to the efforts of Antony T. Curtis (Thank you so much Antony!). It is a patch he made over a year ago . By transactional support, this means that if your remote table type is transactional, transactions will now occur correctly since a constant connection is maintained for the duration of that transaction.

It is downloadable at http://www.patg.net/downloads/federatedx_engine-0.4.tar.gz


The patch changes:


Bug#25513
"Federated transaction failure"

Experimental and fully functional patch for review/comments.

What this patch …

Hi! So this is completely my notes taken from the conference, without my thoughts attached to it. I should definitely post a lot more about this, and how the community can “improve” in time. Just not today. Believe me, sitting in the talk, was highly painful, and I’m wondering where my aspirin stash might be. The slides will be available soon, and lets just consider this a learning experience. It reminded me of the time Eric Raymond came to the Fedora Project’s very first FUDCon in Boston 2005 (probably the only session without available video :P).

What MySQL can learn from PostgreSQL
Joshua Drake

Compared us at OSCON 2007. MySQL lacked technical meat, compared to PostgreSQL. Since 2005, PostgreSQL booth had most visitors besides Mozilla.

MySQL Community is a second class citizen. MySQL AB does not advocate. They promote, they …

The team just finished our second successful MySQL Con. Many thanks to Marten & Zack and all the folks at O’Reilly that put on such a great conference.

This year definitely had a different feel, and of course that had a lot to do with Sun’s influence. It felt like it was almost a new event, a chapter 2 for MySQL, and its ecosystem of vendors and customers. There were more people - I don’t know exact numbers, but it felt appeared to be twice as packed. The exhibit hall was the same, but we took up a bit more space than last year and certainly there were much fancier booths - ours included! We even gave away multiple prizes this year - our fun 8-ball tshirts, and a couple remote control helicopters. Scott Baird and Mike Hogan were the lucky winners this year.

The one thing that hasn’t changed is our fit with the MySQL customers. This year we met several of our own customers and users face-to-face - including an entire …

A

I was curious about some of the databases I get to work with. “How do my clients store their data? What data types are most prevalent?” Well, a few keystrokes later, I had my answers:

SELECT c.data_type, count(c.data_type) AS frequency
FROM information_schema.columns AS c
INNER JOIN information_schema.tables AS t
ON c.table_schema = t.table_schema AND
c.table_name = t.table_name
WHERE c.table_schema NOT IN ('information_schema','mysql') AND
t.table_type = 'base table'
GROUP BY data_type;

Which gave me a nice “data type distribution” table:

Yum is an extremely popular system to download, install, and update RPM-based packages from multiple repositories. Proven Scaling has launched a set of repositories to augment the existing central distributions’ repositories with packages our customers need for deploying MySQL-based systems. We’ve been working on it for a while, and have had many people making use of it. We are providing:

• RPMs of community and enterprise releases of MySQL for RHEL/CentOS, as built by MySQL and distributed on MySQL.com
• RPMs of community tools such as maatkit and innotop and their dependencies. …

A

The slides from my 2008 MySQL Conference Presentation can be downloaded from here .