I have the same problem, but I don't want to delete my schema_migrations table. Wouldn't deleting it do strange things to Rails's understanding of the state of the database?
I've worked around the problem by renaming the "schema_migrations" table to "zschema_migrations", doing the db:push, and renaming the table back to "schema_migrations". Since the tables are uploaded in alphabetical order, this table is now uploaded after all the others, and so now all my data is on Heroku. This makes for a strange kind of workflow though. Hopefully there's some simple answer, a simple thing I'm doing wrong? On Apr 5, 10:24 pm, Bill Burcham <[email protected]> wrote: > Well I didn't figure out why I couldn't push the schema_migrations. > Might have been a unique key constraint violation since the target > database already had the schema migrations in it. Nevertheless I just > deleted the schema_migrations records from the source database and now > the upload works. And my site works. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
