ads' corner

f* MySQL

Today I woke up because the Nagios used by our ISP sent me a SMS: something does not work well on one of the association servers. According to the SMS, the webserver was not responding. Ok, the webserver is never the cause of the problem, something else is going wrong.


MySQL Limitations

You will find Casey Allen Shobe’s site with limitations of MySQL very interesting:


How does your database count?

Just found out a curiosity which was only recently fixed:


There is no spoon^M^M^M^M^Mauto_increment

Got this from a mysqlcheck report:

1
2
warning : Found row where the auto_increment column has the value 0
unihelp_db_propietary.unihelp_stats

some tests from tweakers.net

tweakers.net has again tested the performance of PostgreSQL 8.2-dev and MySQL 4.1.20 and MySQL 5.0.20a. Results are nice and shown here.

Best thing: the collapse for requests per seconds if MySQL has a concurrency greater than 7. Oh, and by the way, they don’t state the table type for MySQL so we don’t know, if it is the fast and forgetfully MyIsam or the better but slower InnoDB type.


Safety of your data

Today I got this after running a mysqlcheck:

1
warning : Found row where the auto_increment column has the value 0

MySQL and real trigger support

I just answered a question on the Usenet about triggers in MySQL and discovered something very scary:


Good article about comparisation of PostgreSQL and MySQL

devx.com has a fair comparisation about the two databases engines, not looking at the speed but at more important points like features, ACID, transactions or commercial and 24/7/365 support. In other words, all the things you want, if you decide to use a database in a production environment.


Wie gut repariert man eine Datenbank in MySQL

Letztens in einem IRC Channel:


Atomisch oder doch lieber atomar?

Diese wannabe Datenbank macht immer alles anders:

Google Suche nach “mysql” + “atomisch”