Issues with db:setup and db:migrate

[spockz]

Given an initial model Foo:

class Rekenservice
  include DataMapper::Resource  

  property :prop1,      Integer
end

We perform a rake db:setup && rake db:migrate and all is fine. Now later in development we add a new
property to our column :prop2.

class Rekenservice
  include DataMapper::Resource  

  property :prop1, Integer
  property :prop2, Integer
end

We write a migration for this that reads as follows:

migration 1, :add_prop2 do
  up do
        modify_table :foos do
            add_column :prop2, Integer
        end
    end
end

Subsequently calling rake db:migrate is no problem. However, now when we run rake db:setup && rake db:migrate again after deleting our database we get the following error:

duplicate column name: prop2

This because auto_migrate! in rake db:setup already created the column for :prop2.

What to do about this?

[c0ze]

Sorry for digging this up. Have you found a solution for this ? (other than moving away to another ORM). Currently I'm simply not running migrations for new DBs.

[spockz]

@c0ze I honestly don't remember and I'm no longer with the project. I suppose setup and migrate at the same time might be a bit strange.

[tpitale]

Not a good idea to mix auto migration and migration files. One or the other. Also, db:setup appears to do some portion of the migration. Try db:create db:migrate if you don't want auto migration.