I'm giving a webinar on tag schema designs and folksonomy concepts tomorrow, from 1pm to 2pm EST. The webinar is chock full of SQL code and optimization tips, so it should be a fun time ...

We'll go over tagging database access patterns, many-to-many mapping techniques, using MySQL's storage engines and replication effectively to scale out the schema, and discuss the advantages of a normalized schema approach versus other popular approaches. Oh, and we'll make fun of rounded corners, too.

Beijing, August 29 2006 - MySQL AB, the developer of the world's most popular open source database, and Greatlinux Inc, a leading open source solutions and services provider in China, today jointly announced a strategic partnership to deliver commercial MySQL-based solutions to the burgeoning Chinese market.

I just uploaded the first ready-to-use package of the MySQL Index Analyzer (version 0.02). You can download it via its download site.

I recommend going to the MIA homepage to see what's new and how to use it.

Recently I was reminded painfully of the fact that habits you have taken to once hardly ever get laid off.

I usually consider myself someone who tries to write software after I have thought it through. I do not mean "over-engineering", "over-abstracting" and "over-prepare-for-anything-that-might-ever-come'ing". However I also believe that starting hacking blindly is not a good thing either. And I try to write "nice" code, even though it might be a little more work, as long as it is easier to read or just plain more stable (which is often the same).

Sometimes however, especially under a tight schedule, by force of habit I (and probably any developer out there) tend to do things that upon later review make me feel deeply embarrassed. Just so I did a couple of weeks ago...

I had to write a component that translates data from a legacy system, stored in plain text files, into a relational database, accessed through an object …

mysql> select count(*) from file_to_delete;
+----------+
| count(*) |
+----------+
| 40510413 |
+----------+

mysql> select count(*) from file_on;
+-----------+
| count(*) |
+-----------+
| 178473804 |
+-----------+



Was wondering about this:

host device size(G) used(G) free(G) use%
---- --------------- ---------- ---------- ---------- ------
[...]
---- --------------- ---------- ---------- ---------- ------
total: 3437.986 2722.549 715.437 79.19%


when:

mysql> select count(*) from file;
+----------+
| count(*) |
+----------+
| 19229098 |
+----------+

mysql> select (sum(length) / 1024) / 1024 from file;
+-----------------------------+
| (sum(length) / 1024) / 1024 |
…

The results are in, and MySQL came out on top. C't just did a comparison of different databases and found that MySQL is the "fastest database application." The magazine's editors held the contest to evaluate database performance in real-world business use by creating a standard online inventory system.

From the announcement:

"The DVD shop created by MySQL is the hands-down winner of the performance crown. It clearly demonstrates the capabilities of a carefully configured MySQL/PHP application.”The MySQL DVD online store was able to process 3,664 orders per minute (opm). If a second computer had been used, the figure would have gone up to 6,000 opm, indicating that MySQL is business ready. No more of this silly nonsense about it being a low-end utility database. Nothing could be farther from the truth.

(You can see the full results from the contest …

So I've set up this cast-aside laptop as a machine to do pulls from BitKeeper and do builds and installs and it's working pretty well. I was able to do pulls of six different versions of MySQL and build them. They are now happily running simultaneously.

Then I went away for three days, taking my younger daughter to boarding school where she is starting as a freshman in high school. At the same time my older daughter is off to college so the nest is now basically empty. But I digress.

I said 'was' because shortly after that a couple bugs manifested, one as noted before and one new one which I was pleased to report and have verified. I have been following the …

So I've set up this cast-aside laptop as a machine to do pulls from BitKeeper and do builds and installs and it's working pretty well. I was able to do pulls of six different versions of MySQL and build them. They are now happily running simultaneously.

Then I went away for three takes, taking my younger daughter to boarding school where she is starting as a freshman in high school. At the same time my older daughter is off to college so the nest is now basically empty. But I digress.

I said 'was' because shortly after that a couple bugs manifested, one as noted before and one new one which I was pleased to report and have verified. I have been following the …

Update: As some people have pointed out, if this is on all the time in a production environment, it could be bad. We only enable it when debugging. But, in the interest of keeping the PHP world safe, I have edited the code.

Preface: I would not use this in a production environment on a full time basis.  When we do use it, we turn it on, gather some logs and turn it off.  Also, it has been pointed out to me that this will cause MySQL to not use the query cache in versions previous to 5.0.  That is another reason to not use this in a production environment full time.

So, on dealnews.com we often end up with a lot of queries that look kind of the same. It usually because we have a complex query that simply selects article ids from one or two tables and then a second query to select the data from the article table using those ids. If you have used MySQL …

As I explained in this blog, it’s always a difficult decision for me to keep postponing my own project in order to work on the patent policy front. But once again, like so many times before, I have decided to do so for some more time. Given what happened at the July 12 hearing, there are some important things to do right away. I’ll talk a little more about my personal future on some other occasion, but suffice it to say that I’m still actively involved in the European patent policy debate!