title: Marking Rails migrations as migrated
body: <p>I've ended up with 9 migrations effectively duplicated. (I think this is because I installed/updated Gems and/or pulled in their migrations on both my dev and production machines, but am not entirely sure at this stage.)</p>
  
  <p>I moved out one set of the duplicated 9 from the rails directories on the production server, but now that I want to <code>db:migrate</code> on production in order to run another migration, I'm getting:</p>
  
  <pre><code>$ bundle exec rake db:migrate RAILS_ENV=production
  [DEPRECATION WARNING] Nested I18n namespace lookup under "activerecord.attributes.checkout" is no longer supported
  ==  CreatePages: migrating ====================================================
  -- create_table(:pages)
  rake aborted!
  An error has occurred, all later migrations canceled:
  
  Mysql2::Error: Table 'pages' already exists: CREATE TABLE `pages` (`id` int(11) DEFAULT NULL auto_increment PRIMARY KEY, `title` varchar(255), `body` text, `slug` varchar(255), `created_at` datetime, `updated_at` datetime) ENGINE=InnoDB
  </code></pre>
  
  <p>This is because the migrations have effectively already been run.</p>
  
  <p>I'd rather avoid doing <code>db:migrate:down</code> and <code>db:migrate:up</code> for each one - I think this will mean data in the production database is lost. (A couple of static pages in Spree in this case.)</p>
  
  <p>Is there a way I can tell this installation of Rails to forget all outstanding migrations, effectively marking all outstanding migrations as done?</p>