The latest from the MySQL community

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 …

Well, that didn't take long. Monty Widenius, one of the founders of MySQL, resigned from Sun Microsystems last week but has already invested some of his hard-earned MySQL dollars in IT Mill, a Finland-based open-source start-up focused on the development of Rich Internet Applications.

While no mention is made ...

In the xml parser that I’ve been writing for rss/atom feeds I’ve encountered what many people have found; bizarre encoding issues when displaying the data from the database on a webpage. Since this is not really well explained by the searches I did on google I’ll explain it here.

Issue: you have utf-8 data coming from a source, you put it into a utf8_general_ci column of a mysql database table. You read the data from the database and display it as html/xhtml. Instead of getting things like double backquotes or long dashes you get euro signs or umlaut type of characters, usually strings of them instead of the correct format.

Potential solution: use utf8_encode and htmlentities in PHP to clean the data before going into the database. This does not work. Why? Those characters are not covered by html standards since they are above ascii code 126. See here for the full code chart: …

Knut Anders Hatlen writes about memcached user-defined functions (UDF) for Java DB on OpenSolaris.

Knut has also mentioned the recent release of Apache Derby 10.4.2. A corresponding Java DB release should be available for download soon. (Usually this happens immediately but we're all at a developers' conference for the next couple of …

We’re happy to announce the next release of MySQL Workbench 5.0. This one has 19 bugs fixed compared to the last version. We’re about to complete the first alpha version of Workbench 5.1 but in parallel we’re continuing our bug-raid for 5.0 (most of the fixes also go into 5.1 code as well). Stay tuned for the next announcements here on wb.mysql.com