taps 0.2.14 should fix your schema_migrations issue. also, you can wipe out (reset) your database by doing heroku db:reset --app <app name>
On Apr 9, 9:44 pm, Bill Burcham <[email protected]> wrote: > The reason it worked for me was that: > precondition: fully migrated schema existed on heroku > 1. tried to push from local db to heroku–this failed because of > schema_migrations primary key conflict (I surmise) > 2. deleted all schema_migrations records from my local db > 3. successfully pushed from local db to heroku > > See my heroku db already had good schema_migrations to start with. > > Better solution would have been to drop all my data from heroku before the > push. But I don't think heroku provides any such canned capability. I did > find a rake task that purported to do it though. Haven't tested it yet. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
