On Mar 18, 2010, at 11:23 PM, Mike wrote: > I'm not really sure why, but now it thinks it's on version 0 of the > database, even while it already has all of the tables from the full > migration set. This leaves me unable to perform another db:migrate > VERSION=0, and attempts to do so error out as it tries to create my > first migration for some reason.
My guess is that you CTRL-C'd out before the schema_migrations table got copied. The contents of this table are how Rails knows which migrations have been applied. > I'm unable to perform either db:migrate:reset or db:reset because I do > not have drop permission on the database. heroku db:reset (not heroku rake db:reset) > What procedure should I follow to clear out the database? Also, is > this type of corruption always going to happen if a db:push is > canceled part way through? If my guess is correct and the corruption is just caused by the missing schema_migrations data, then it will happen if you CTRL-C before that. I wouldn't really call it corrupt, just incomplete. You could either reset and repush, or probably just start another push on top of this one. Hope this helps, David -- 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.
