For example, after executing this code:

create table t1 (id int, c char(10), d date);
insert into t1 values (1, 'abc', '2008-01-01');
insert into t1 values (2, 'def', '2008-08-19');
insert into t1 values (3, 'ghi', current_date());
select * from t1; …

And since I mentioned this subject, there are two additions:

• the schema now supports partitioning. Instead of using employees.sql, load the data via employees_partitioned.sql
• the schema has been altered to be used with Drizzle. The test script works with Drizzle if you compile the MD5 plugin and load it at startup.

As I mentioned some time ago, Software Freedom Day 08 will take place on Saturday, 20th of September 2008.

Coincidentally, the a large number of Sun/MySQL Engineers and other Sun folks will be in Riga, Latvia for an internal developer meeting around this day. To make use of this opportunity, we plan to give a number of sessions and presentations (in english) about various topics and to contribute to this global celebration of Open Source Software.

We've set up a Team Page on the Software Freedom Day web site for this event - the venue will be the …

As I mentioned some time ago, Software Freedom Day 08 will take place on Saturday, 20th of September 2008.

Coincidentally, the a large number of Sun/MySQL Engineers and other Sun folks will be in Riga, Latvia for an internal developer meeting around this day. To make use of this opportunity, we plan to give a number of sessions and presentations (in english) about various topics and to contribute to this global celebration of Open Source Software.

We've set up a Team Page on the Software Freedom Day web site for this event - the venue will be the …

Today we announced (German press release, English press release) a partner deal with Dolphin Interconnect Solutions, makers of the Dolphin Express highspeed interconnect technology. Like DRBD, Dolphin Express and Dolphin SuperSockets are well established within the MySQL customer base — the latter as a low-latency interconnect for MySQL Cluster. As part of the deal, …

A couple of months ago Mark Callaghan mentioned it would be very nice to have a replication product that could transfer data from newer to older versions of MySQL. Ever since then I have been interested in trying it with our new Tungsten Replicator. Today I finally got the chance.

I have a couple of Centos5 virtual machines running on my Mac that I have been using to test the latest Tungsten Replicator 0.9.1 build. I happen to have MySQL 5.0.22 (the antiquated version that comes with CentOS5) on one VM. I set up MySQL 4.1.22 on the other CentOS5 VM and tried to make it a slave of the 5.0 server using MySQL replication. The result was the following error message:

080911 15:25:13 [ERROR] Master reported an …

Here's a question I posted to the DBI as well as mod_perl mailing list that I thought would be also a good question to ask here:

Hi all,

I'm currently working on... of all things, a book on book about web app programming with Perl/Apache/MySQL, and I'm trying to explain what Ubuntu packages to use for installation (and I'm sure other Linux variants same applies)

Ubuntu gives you:

apache2-mpm-prefork
apache2-prefork-dev
apache2-mpm-worker
apache2-threaded-dev

I've used both prefork and worker (as of late, due to concerns with perl and threads), both of which seem to work fine. Though, the DBI documentation warns of caveats of using threaded, especially if the client is not thread safe (I always compile mysql with a thread-safe client, and DBD::mysql against that thread safe client).

So... I'm trying to decide if I should explain
…

How would you expect AUTO_INCREMENT to work with MERGE tables ? Assuming INSERT_METHOD=LAST is used I would expect it to work same as in case insertion happens to the last table... which does not seems to be the case. Alternatively I would expect AUTO_INCREMENT to be based off the maximum value across all tables, respecting AUTO_INCREMENT set for the Merge Table itself. Neither of these expectations really true:

PLAIN TEXT SQL:

1. mysql> CREATE TABLE a1(i int UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY);
2. Query OK, 0 rows affected (0.01 sec)
3.  
4. mysql> CREATE TABLE a2 LIKE a1;
5. Query OK, 0 rows affected (0.00 sec)
6.  
7. mysql> INSERT INTO a1 VALUES(2);
8. Query OK, 1 row affected (0.00 …

Take a look at this:

PLAIN TEXT SQL:

1. mysql> repair TABLE a3;
2. +---------+--------+----------+----------+
3. | TABLE   | Op     | Msg_type | Msg_text |
4. +---------+--------+----------+----------+
5. | test.a3 | repair | STATUS   | OK       |
6. +---------+--------+----------+----------+
7. 1 row IN SET (0.10 sec)
8.  
9. mysql> SELECT * FROM a3 ORDER BY i;
10. +------------+
11. | i          |
12. +------------+
13. | 2147483648 |
14. |         11 |
15. |         13 |
16. |         14 |
17. | 2147483647 | …

My last post asking what people are looking for in being part of the Certified MySQL Community brought me a good deal of email. I will pursue looking into training and service contract discounts with my bosses. Mugs and t-shirts seem to be popular requests also.

I even had someone who saw my mention of beta exam testers as 'guinea pigs' and requested branded guinea pigs. Now, I live in Texas and two miles from my house there is a heard of Bison. A few folks in the area have cattle, mainly longhorns. A lot of livestock these days actually get implanted microchips but branding irons are still used for the recognition of livestock on the days the cowboys leave the RFID scanner out of the saddlebags. So I asked about branding.

My consultants on the subject were not inclined to favorably recommend branding Cavia porcellus. Having Sakila, the MySQL dolphin, and/or the letters 'MySQL' would probably be too busy …