Unfortunately I had to spend some time to find the...

2009-07-14T06:27:30.793-05:00

Unfortunately I had to spend some time to find the cause of migration error and want to share my solution/bug fix (maybe :)).

On the following migration

up do
create_table :sph_counter do
column :counter_id, Integer, :serial => true
column :max_doc_id, Integer, :null => false
end
end

I got the following SQL

CREATE TABLE `sph_counter`
ENGINE = InnoDB
CHARACTER SET utf8
COLLATE utf8_general_ci (`counter_id` serial PRIMARY KEY, `max_doc_id` INT(11))

Here are two little changes for fixing this (dm-migrations-0.9.11):
lib/sql/table_creator.rb:
def to_sql
"#{@adapter.create_table_statement(quoted_table_name, @columns)}"
end

lib/sql/mysql.rb:

def create_table_statement(quoted_table_name, columns)
"CREATE TABLE #{quoted_table_name} (#{columns.map{ |c| c.to_sql }.join(', ')}) ENGINE = InnoDB CHARACTER SET #{character_set} COLLATE #{collation}"
end

Comments on Ruby, Javascript, Erlang blog: Snakes, Gems & Coffee: DataMapper does have migrations

Unfortunately I had to spend some time to find the...