Brian Aker starts work on a memcache engine for mysql. so your memcache cache acts just like a table.

the big thing here which I’ve seen asked for a couple of times on the memcached list is the ability to see a list of keys.

mysql > select * from foo1 WHERE k=”mine”;

freaking amazing.. I love these kind of mashups.

and the 2nd important event.

Django is starting a branch to integrate SQLAlchemy

There's a good blog by a former tech analyst, who also happens to be my twin brother, called OnDisruption.  While I don't normally like to promote something as blatantly nepotistic (is that even a word?) as this, his blog doesn't cost anything to read so I don't think there's a conflict of interest here. 

His most recent posting is on the "Eight Traps of Disruption" and does a good job analyzing some of the common mistakes businesses make when they think they are being disruptive.  For those who lived through the dot com era in Silicon Valley, you may recognize a few of the examples.  For others, yes, it sounds crazy, but people really did make these mistakes.  And often to the tune …

“The key, the whole key, and nothing but the key, so help me Codd!”

The database guys should like that one. Can’t remember where I saw it today to acknowledge reference.

Today MySQL published the press release with results of Database Contest (results on German available here http://www.mysql.de/ct-dbcontest).

Peter and me spent quite some time working on this project while being employed by MySQL and it is great to see results finally publicly available.

The story began about year ago when C'T magazine had called for Database competiton using Dell DVD Store benchmark (details available here: http://firebird.sourceforge.net/connect/ct-dbContest.html).

Most interesting results are (more orders per minute are better ):
MySQL5/PHP (our solution) : 3664 orders per minute
DB2/Java : 1537 opm
Oracle / Java: 1412 opm
…

Peter Zaitsev over at the excellent MySQL Performance Blog recently wrote an article on duplicated and redundant indexes -- any indexes which cover exactly the same columns as another index, or cover a leftmost prefix of another index. While there are subtleties, such as FULLTEXT indexes not being the same as non-FULLTEXT, for the most part this is sufficient criteria to raise possible duplicates to a DBA's attention. I opened my big mouth in the comments and said I could write a quick Perl script to discover possible offenders in just a few lines of code. Once I did that, I had to do it and give you the script. Here it is.

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 |
…