The latest from the MySQL community

Testing and automation. These two are key to ensuring high quality of software releases.

Ever since I worked briefly in the team at MySQL AB that is responsible for creating the binary (and source) packages of MySQL releases, I have had the vision of a fully automated release procedure. Whenever someone pushes a new commit to the release branch revision control tree, the continuous integration test framework should kick in and do all the steps needed for producing release packages:

• Checkout the new revision.
• Build a source tarball, and save it.
• For each platform, build a binary package from the source tarball. The build should be done in a freshly installed machine without any revision control checkouts, previous build trees, or extra installed software, to ensure that no unwanted dependencies or stray …

The article was published in July but I noticed it only today. I guess I should pay more attention to my favorite topics when I travel.

Recently Mark observed that we now all need a storage engine independent test suite, Sun included! Well, as far as I know, there is such a thing at Sun, sort of. Apparently it has been used to test PBXT and other engines, but I've heard it is not in good enough shape to be released.

But my question is, why not release it anyway? We could turn it into an engine community project. I believe there are enough engine developers out there to get this moving forward.

The secret is to start small, and just get a few tests to run with all engines. Then additional tests can be added step by step. Engines need a way to specify that they want to skip a test entirely (e.g. transactional tests), and it should be easy to customize results for various engines.

An example of a simple and elegant solution can be found in Drizzle. As …

There is a detailed announcement that warns against using these binaries in production, but encourages everyone to test them. A companion tutorial explains how to use the snapshots to test the InnoDB plugin, which was released recently, and it is included in the latest MySQL …

This tool produces one binary package for each platform where the test runs, and every day there are a few dozen of such packages, waiting to be deleted and replaced by the ones created with the next build.

For long time, several people suggested publishing these binaries for the community. Each time, there was some minor or major impediment, such as getting together different teams and requesting resources from a third one. But the community …

1. Install MySQL::Sandbox

This is a …

This tool produces one binary package for each platform where the test runs, and every day there are a few dozen of such packages, waiting to be deleted and replaced by the ones created with the next build.

For long time, several people suggested publishing these binaries for the community. Each time, there was some minor or major impediment, such as getting together different teams and requesting resources from a third one. But the community …

This tool produces one binary package for each platform where the test runs, and every day there are a few dozen of such packages, waiting to be deleted and replaced by the ones created with the next build.

For long time, several people suggested publishing these binaries for the community. Each time, there was some minor or major impediment, such as getting together different teams and requesting resources from a third one. But the community …

In my last post I included some sample data which was useful for playing around with queries (once I published it, I realized it made my post look like some form of keyword stuffing, fortunately I don’t use adsense on my site so I hope I’m free of any suspicion :D). That sample data was … Continue reading Generating data with dbmonster →

Related posts:

1. Generating random salts from bash From the ‘just because it can be done’ column, here...
2. Using the ENUM data type to increase performance While going through the DATA TYPES section of the Certification...

I'm pleased to announce the release of SQL Bench, the benchmark test suite the comes standard with MySQL, now as a separate project targeted for testing any database. I have pulled it out as a separate project so I can modify and improve it faster. With this release, I have successfully used it for testing both Drizzle and MySQL. Other RDBMSs, I have yet to test.

Modifications

I modified the connection test, which part of it is to connect, run a single query for one row, disconnect, to iterate only 20,000 times vs. 100,000 times. The reason for this is to allow this test to reasonably test databases that use TCP sockets. When I added Drizzle support to SQL Bench, upon running the connect test it would fail inexplicably. After some serious testing, it was realized that since Drizzle uses TCP sockets, even when connecting to localhost, that the connect test would fail because of the result of sockets being kept around in …