Introduction

A question I recently saw on Stack Overflow titled Faster way to delete matching [database] rows? prompted me to organize my thoughts and observations on the subject and quickly jot them down here.

Here is the brief description of the task: say, you have 2 MySQL tables a and b. The tables contain the same type of data, for example log entries. Now you want to delete all or a subset of the entries in table a that exist in table b.

Solutions Suggested By Others

DELETE FROM a WHERE EXISTS (SELECT b.id FROM b WHERE b.id = a.id);

DELETE a FROM a INNER JOIN b on a.id=b.id;

DELETE FROM a WHERE id IN (SELECT id FROM b)

The Problem With Suggested Solutions

Solutions above are all fine if the tables are quite small and the …

On my last count, there are now 20+ Sun Contributor Agreement (SCA) signatories whose names appear on the master list and who are interested in contributing to MySQL. Only this week, three new members signed the SCA.

These 22+ signatories have all been added since mid-February when we launched the new, Sun-compliant SCA signing process. Before the end of 2009, if we proceed at this same rate, MySQL SCA signatories list should grow to about 70 to 90 contributors.

In the meantime, contributions from many of these contributors have already been accepted and integrated. (I had earlier pointed to Armin Schöffmann's contribution as a simple example of how all this works.)

Some people continue to …

On my last count, there are now 20+ Sun Contributor Agreement (SCA) signatories whose names appear on the master list and who are interested in contributing to MySQL. Only this week, three new members signed the SCA.

These 22+ signatories have all been added since mid-February when we launched the new, Sun-compliant SCA signing process. Before the end of 2009, if we proceed at this same rate, MySQL SCA signatories list should grow to about 70 to 90 contributors.

In the meantime, contributions from many of these contributors have already been accepted and integrated. (I had earlier pointed to Armin Schöffmann's contribution as a simple example of how all this works.)

Some people continue to …

On my last count, there are now 20+ Sun Contributor Agreement (SCA) signatories whose names appear on the master list and who are interested in contributing to MySQL. Only this week, three new members signed the SCA.

These 22+ signatories have all been added since mid-February when we launched the new, Sun-compliant SCA signing process. Before the end of 2009, if we proceed at this same rate, MySQL SCA signatories list should grow to about 70 to 90 contributors.

In the meantime, contributions from many of these contributors have already been accepted and integrated. (I had earlier pointed to Armin Schöffmann's contribution as a simple example of how all this works.)

Some people continue to …

I’ve just come across the following post on new 5.1 and 6.0 replication features which was quite interesting.

A few features mentioned such as:

• pluggable replication architecture
• semi-synchronous replication
• time-delayed replication
• scriptable replication

sound like things what are going the right way. For those of still using 5.0 we’ll have to wait for quite a long time before we will actually be able to use them. At least some of this gives us an incentive to upgrade.

No mention yet of N:1 replication, or making the replication process separate from the main mysqld process. The latter is much easier now and would only require minimal hooks in a plugin at each send of the replication path. However, these are things that can come in the …

MySQL has deep roots in open-source software development communities and code contributions to MySQL keep flowing in, being reviewed and integrated into the MySQL. 

During our BoF at the MySQL Conference and Expo, Lenz Grimmer talked about our work to make MySQL (even more) contributor friendly, with some more focused effort starting on February 1, 20091.

The desire to contribute code to MySQL remains as strong as ever as evidenced by this year's MySQL Conference and Expo, where I had an opportunity to speak with some contributors and partners who wish to contribute to MySQL. Of course, there are a lot of strong and varying opinions in this area.

As I said above, code has been contributed and absorbed in MySQL (according to either the MySQL …

Mosso the Rackspace Cloud now has a Drizzle developer image much like the first Drizzle AMI on EC2.

The Mosso interface is definitely different, it’s a GUI, and I definitely prefer CLI, but it’s a simpler navigation for a new user. I suspect an API may be available.

I had an issue with the backup process, more the lack of feedback. The Knowledge Base didn’t help, so both calling and Live Chat directed me ultimately to the same person. I also found a bug in the backup process, that is being able to select an incomplete backup to try and launch a new server. I talked to Support about and apparently already known.

And in true open source form, the Drizzle version is actually one point higher then yesterday’s AWS image.

MySQL has deep roots in open-source software development communities and code contributions to MySQL keep flowing in, being reviewed and integrated into the MySQL. 

During our BoF at the MySQL Conference and Expo, Lenz Grimmer talked about our work to make MySQL (even more) contributor friendly, with some more focused effort starting on February 1, 20091.

The desire to contribute code to MySQL remains as strong as ever as evidenced by this year's MySQL Conference and Expo, where I had an opportunity to speak with some contributors and partners who wish to contribute to MySQL. Of course, there are a lot of strong and varying opinions in this area.

As I said above, code has been contributed and absorbed in MySQL (according to either the MySQL …

MySQL has deep roots in open-source software development communities and code contributions to MySQL keep flowing in, being reviewed and integrated into the MySQL. 

During our BoF at the MySQL Conference and Expo, Lenz Grimmer talked about our work to make MySQL (even more) contributor friendly, with some more focused effort starting on February 1, 20091.

The desire to contribute code to MySQL remains as strong as ever as evidenced by this year's MySQL Conference and Expo, where I had an opportunity to speak with some contributors and partners who wish to contribute to MySQL. Of course, there are a lot of strong and varying opinions in this area.

As I said above, code has been contributed and absorbed in MySQL (according to either the MySQL …

This weeks’ announcement Oracle to by Sun was a major talking point at the 2009 MySQL Conference & Expo. While it is too early to even speculate what the future holds with the official MySQL product, for myself a speaker on MySQL topics, Oracle Open World is now a target market.

In addition to many years of providing MySQL for the Oracle DBA Resources I have with the recent closure of call for papers submitted two sessions for consideration.

Integrating MySQL into your Oracle DBA management processes

Most large enterprise organizations use more then one RDBMS product to service business requirements. With the increase in MySQL usage for web …