Hi Ezra, and list,
Is there something fishy with the Merb-included migration? I ran it,
and MySQL complained.
I removed this line, by commenting it out:
# t.column :id, :integer, :null => false
(Since Rails migrations that create tables always create an auto-
increment as primary key, but they do use the NULL thing, so when you
pass in a null, things happen "the way MySQL users will expect them
to happen")
Apologies if this is a known issue. I just downloaded Merb 25 minutes
ago, so I am quite fresh at this.
best regards, and I love Merb (it seems neat),
Olle Jonsson
Copenhagen
