Today, I ran my standard task to push changes to two different Heroku apps.
As part of this task, I issue a:
heroku rake db:migrate
In both cases, the database started migrating from the very first
migration. This, of course, doesn't make sense unless the
schema_migrations table were empty or something, which shouldn't have
been the case.
Has anyone else complained about this today?
After restoring the DBs in question up from my local installation using
taps, I didn't see this behavior again.
Wes
--
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.
