Segment7: MySQL is Dum

MySQL is Dum

drbrain@segment7.net (Eric Hodel) — Sat, 25 Feb 2006 16:39:00 -0800

How hard is it to write data until the disk fills up? Creating more than 4GB of data isn’t that difficult, so shouldn’t the database be able to work with that much data out of the box?

How hard is it to write data to a table in-order when using INSERT INTO SELECT?

UPDATE: Seriously!

<samp>mysql&gt; delete from [...] where timestamp < [...];
Query OK, 35759328 rows affected (57 min 13.77 sec)</samp>

"MySQL is Dum" by thomas quas

Sat, 25 Feb 2006 16:39:31 -0800

Just check the obvious: is there an index on timestamp? You might want to try ‘explain select … where timestamp < ...’ which gives you information about how the database optimizes the statement. More detail can be found at http://dev.mysql.com/doc/refman/5.0/en/explain.html

Hope this helps.

"MySQL is Dum" by Eric Hodel

Sat, 25 Feb 2006 16:39:31 -0800

To be honest, I hate this table since it only gets used for one thing but we must keep the data around. Ordinarily we don’t do anything via the timestamp column.