How can I exclude data from local schema_migrations tables that have been migrated to Heroku database?

I was able to get my Ruby on Rails application running with MySQL (local dev) to Heroku server and also migrate my model using the command heroku rake db:migrate

. I also read the documentation on Database Import / Export . Is this document a link to direct the actual data from my local DB detector to some Heroku DB? Do I need to change anything in the file database.yml

for this to happen?

I ran the following command:

heroku db:push

      

        
        
        
      

    

and I get the error:

Sending data
2 tables, 3 records
!!! Caught Server    Exception                                   | ETA:  --:--:--
Taps Server Error: PGError ERROR:  duplicate key value violates unique constraint
"unique_schema_migrations"

      

        
        
        
      

    

I have two tables, one I am creating for my application and the other schema_migrations

. The total number of records among the two tables is 3. I also print the number of records I have in the created table and it shows 0.

Any ideas what I might be missing or what I am doing wrong?

EDIT: I figured out above, Heroku DB already has a schema_migrations

point where I was running to migrate.

New question: Does anyone know how I can exclude data from a specific table due to the fact that it was migrated to Heroku database. The exclusion table in this case will be schema_migrations

.

Not a good solution : I googled around and someone else had the same problem. He offered to name the table schema_migrations

zschema_migrations

. This way, data from other tables will be inserted correctly until the last table ends. This is a pretty bad decision, but will do it for now.

A better solution would be to use an existing Rails command that can reset point to a specific table from the database. I don't think I Rake

can do it.