rake db:migrate not working on Rails 3
Reported by Greg Campbell | October 7th, 2010 @ 02:52 PM | in 1.1
rake db:migrate does not appear to do anything in
Rails 3. The issue appears to be that each migration adds to the
@migration array on the main object (which has
DataMapper::MigrationRunner included) , whereas the
rake task calls
::DataMapper::MigrationRunner.migrate_up!, which
references the (empty) @migration array on
::DataMapper::MigrationRunner. Either the
migrate() method needs to be changed to add to
::DataMapper::MigrationRunner.migrations, or the rake
task needs to be changed to call simply
migrate_up!
Comments and changes to this ticket
-
Martin Gamsjaeger (snusnu) October 24th, 2010 @ 01:13 PM
- State changed from “unconfirmed” to “resolved”
- Milestone set to “1.1”
- Assigned user set to “Martin Gamsjaeger (snusnu)”
- Milestone order changed from “196296” to “0”
This should be fixed in http://github.com/datamapper/dm-migrations/commit/cd9d62ee08b6615a2...
Since no new dm-migrations has been released since then, you could a) use dm-migrations from git using bundler, b) apply the monkeypatch described in http://datamapper.lighthouseapp.com/projects/20609/tickets/1214 or c) wait for a new dm-migrations (and thus, datamapper release, which probably isn't too far off either).
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Greg Campbell
Martin Gamsjaeger (snusnu)