Sun + MySQL

nospam@example.com (Denis Arh) — Tue, 29 Jan 2008 19:21:21 +0000

... just kidding. I'm really getting sick of blog posts about Sun and MySQL. I't looks like everyone must have an opinion, write some predictions about the outcome for the MySQL community etc.

I just want to point out a great tip for spotting useless indexes in MySQL.

MySQL: Only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT

nospam@example.com (Denis Arh) — Tue, 01 Jan 2008 17:34:30 +0000

I've ran into a really stupid MySQL limitation today:

mysql> create table foo (foo_1 timestamp default now(), foo_2 timestamp default now());
ERROR 1293 (HY000): Incorrect table definition; there can be only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE clause

Nothing like that mentioned in the docs, but there is a small (deadend) thread in the lists.mysql.com -- nothing much

Meanwhile, on the other side of the town:

postgres=# create table foo (foo_1 timestamp default now(), foo_2 timestamp default now());
CREATE TABLE

darh|blog - dba

Sun + MySQL

MySQL: Only one TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT