I got it working. The problem was an old migration failing. Blah. Time
to consider consolidating old migrations.
Steve
On Feb 4, 7:35 am, Steve Odom wrote:
> Quick edit:
>
> > My migrations seem okay *on my development box* because I can migrate down
> > to 0 and back up
> > again with no probl
Quick edit:
> My migrations seem okay *on my development box* because I can migrate down to
> 0 and back up
> again with no problem.
On Feb 4, 7:34 am, Steve Odom wrote:
> heroku rake db:version doesn't return anything for me.
>
> I did not previously have schema.rb under version control. I a
heroku rake db:version doesn't return anything for me.
I did not previously have schema.rb under version control. I added it.
Reloaded it and a bunch of other things and still nothing.
My migrations seem okay because I can migrate down to 0 and back up
again with no problem.
I even said screw it
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 W
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 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
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 m
