This happened again to me. I verified that:
- the schema_migrations table was full of data
- that a Gemfile change didn't prompt this.
For whatever it's worth, here is the relevant portion of my Ruby script
for pushing my app to heroku:
#Push to Heroku
system 'git push heroku'
#Migrate the DB for the main application
system 'heroku rake db:migrate'
I have the DB backups in place to recover from this, but it is very
disconcerting.
I'm trying to think of a reason why the schema_migrations table might
not be available after the 'git push heroku' call. Should I make the
script sleep for a couple of seconds?
Wes
On 1/25/11 6:27 PM, Wes Gamble wrote:
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.
--
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.
