If interested in contributing code to MySQL, you should attend the MySQL University session on contributing code to MySQL.

(Live broadcast with Q&A will be held on Thursday, June 25, 2009. You can still have access to rebroadcasts afterwards.)

This Thursday (June 25th, 13:00 UTC), Lenz Grimmer will explain how to contribute code to MySQL, in a MySQL University session titled MySQL Code Contributions. Lenz is a member of the MySQL Community Team. His session will give an overview about how code contributions to MySQL should be handled and performed. It will cover the ideal workflow, requirements and available infrastructure and toolchain that potential contributors should be aware of.

For MySQL University sessions, point your browser to this page. You need a browser with a working Flash plugin. You may register for a Dimdim account, but you don't have to. (Dimdim is the conferencing system we're using for MySQL …

A long standing bugAmong the many outstanding bugs for MySQL, there is one that has sparked a fierce discussion, not only in the bug report itself, but also in blogs, forums, mailing lists.
Bug #19027: MySQL 5.0 starts even with Fatal InnoDB errors was neglected for long time, until finally it got fixed, and it is available in MySQL 5.1.36.
First off, what is it about?
In short, if an engine doesn't initialize correctly, the MySQL server starts anyway, without the offending engine. Depending on how you use the failing engine, this could be either a minor annoyance or a complete disaster.
Annoyance: ARCHIVE fails to initialize, and you create tables with the default engine (usually MyISAM), and after a while you realize that the disk is filling up faster than you expected. You will find out eventually.
Disaster: ARCHIVE fails to …

After a long hiatus, I am happy to announce that mylvmbackup version 0.12 has now been released. This release includes a large number of improvements, minor code cleanups, as well as some new functionality. In particular, I would like to thank Matthew Boehm, Tim Stoop, Baron Schwartz, Ville Skyttä and Ronald Bradford for their contributions.

Some notable highlights from the ChangeLog:

• Removed the absolute path names to external tools (make sure $PATH is correct)
• Added --log-err to the startup options of the recovery instance to avoid cluttering the server's error log
• Added support for hooks written as Perl Modules. (Matthew Boehm)
• Added support for date/time-formatted path names for backupdir and mountdir (Matthew Boehm)
• Backupdir and …

Today marks the official launch of Percona.tv. We'll be uploading technical screencasts, conference video, and anything else cool we can think up. If you've got ideas or requests, let us know and we'll do our best to accommodate!

Entry posted by Ryan Lowe | 7 comments

Add to: | | | …

Giuseppe stumbled over this website and recommended it to me as a potential useful service for organizing the registrations of the OpenSQL Camp: Eventbrite is a Python/MySQL-powered web site (judging from their job openings) that provides the following:

Eventbrite is the leading provider of online event management and ticketing services. Eventbrite makes it easy for anyone to hold a successful event of any type and size. Eventbrite is free if your event is free. If you sell tickets to your event, Eventbrite collects a small fee per ticket. So just like you, Eventbrite wants your event …

During one of these activities, I will give away one copy of the MySQL Administrator’s Bible. If you are a MySQL enthusiast and you are in Madrid, that's an extra reason to attend the forum. For the ones who still don't know how …

In an earlier post, the pursuit of openness, I announced that MySQL is working at a new release model.

There are still a few details to sort out, but the general plan is ready. The new release model has been approved and starts to operate immediately.

The basic principles of this model are:

• The trunk is always at least in beta quality.
• A milestone starts in beta quality ( never in alpha) with a merge between the trunk and a stage tree;
• Milestone releases, with RC quality, released every three to six months.
• Integration windows between milestones allow the insertion of new features from stage trees
• GA releases happen every 12 to 18 months;
• There are not more than two releases in active …

In an earlier post, the pursuit of openness, I announced that MySQL is working at a new release model.

There are still a few details to sort out, but the general plan is ready. The new release model has been approved and starts to operate immediately.

The basic principles of this model are:

• The trunk is always at least in beta quality.
• A milestone starts in beta quality ( never in alpha) with a merge between the trunk and a stage tree;
• Milestone releases, with RC quality, released every three to six months.
• Integration windows between milestones allow the insertion of new features from stage trees
• GA releases happen every 12 to 18 months;
• There are not more than two releases in active …

In an earlier post, the pursuit of openness, I announced that MySQL is working at a new release model.

There are still a few details to sort out, but the general plan is ready. The new release model has been approved and starts to operate immediately.

The basic principles of this model are:

• The trunk is always at least in beta quality.
• A milestone starts in beta quality ( never in alpha) with a merge between the trunk and a stage tree;
• Milestone releases, with RC quality, released every three to six months.
• Integration windows between milestones allow the insertion of new features from stage trees
• GA releases happen every 12 to 18 months;
• There are not more than two releases in active …