You can see what's the current version of your DB schema by running rake db:version.
Is it on the latest version? schema.rb is versioned, so a db:schema:load shouldn't put your database in a state unreachable by migrations (unless you pushed a migration without pushing the updated schema). On Wed, Feb 3, 2010 at 10:00 PM, Justin Kan <justin....@gmail.com> wrote: > I am having the same problem with my app as well. I don't get any > feedback from the console at all. Any ideas? > > On Feb 3, 5:11 pm, Steve Odom <steve.o...@gmail.com> wrote: >> I did a heroku db:reset on my staging server to start fresh. >> >> My problem now is that my migrations aren't working. I'm not getting >> any errors when I do a heroku rake db:migrate, but not all of my >> migrations are reflected in the database. >> >> My earlier migrations are reflected, but I'm thinking that might have >> something to do with when I did my initial schema.db when I setup my >> account. >> >> I tried adding a --trace but that didn't help. I tried adding >> VERSION=0 and then re-migrating but that doesn't help. >> >> Any ideas on how I might troubleshoot this? >> >> Thanks! >> >> Steve > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to her...@googlegroups.com. > To unsubscribe from this group, send email to > heroku+unsubscr...@googlegroups.com. > 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 her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
