title: How do I exclude data from local table schema_migrations from being pushed to Heroku DB?
body: <p>I was able to push my Ruby on Rails app with MySQL(local dev) to the Heroku server along with migrating my model with the command <code>heroku rake db:migrate</code>.  I have also read the documentation on <a href="http://docs.heroku.com/taps" rel="nofollow noreferrer">Database Import/Export</a>.  Is that doc referring to pushing actual data from my local dev DB to whichever Heroku's DB?  Do I need to modify anything in the file <code>database.yml</code> to make it happen?</p>
  
  <p>I ran the following command:</p>
  
  <pre><code>heroku db:push
  </code></pre>
  
  <p>and I am getting the error:</p>
  
  <pre><code>Sending data
  2 tables, 3 records
  !!! Caught Server    Exception                                   | ETA:  --:--:--
  Taps Server Error: PGError ERROR:  duplicate key value violates unique constraint
  "unique_schema_migrations"
  </code></pre>
  
  <p>I have 2 tables, one I create for my app and the other <code>schema_migrations</code>.  The total number of entries among the 2 tables is 3.  I'm also printing the number of entries I have in the table I have created and it's showing 0.</p>
  
  <p>Any ideas what I might be missing or what I am doing wrong?</p>
  
  <p><strong>EDIT:</strong>
  I figured out the above, Heroku's DB already have <code>schema_migrations</code> the moment I ran migrate.  </p>
  
  <p><strong>New question:</strong> Does anyone know how I can exclude data from a specific table from being pushed to Heroku DB.  The table to exclude in this case will be <code>schema_migrations</code>.</p>
  
  <p><strong>Not so good solution</strong>:
  I googled around and someone else was having the same issue. He suggested naming the <code>schema_migrations</code> table to <code>zschema_migrations</code>.  In this way data from the other tables will be pushed properly until it fails on the last table.  It's a pretty bad solution but will do for the time being.</p>
  
  <p>A better solution will be to use an existing Rails command which can reset a specific table from a database.  I don't think <code>Rake</code> can do that.</p>