ansaurus

Question

Answer 1

+1 A:

I'd say your problem is in the uninitialized constant Admin part of your migration issue. Have you tried finding where Admin is initialized and including the path to that wherever you're using it? (Also, what's the contents of the rake task you're running?)

Chris Bunch 2008-10-20 18:25:21

Answer 2

+2 A:

Sometimes Rails will throw this error if there's a syntax error where Admin is defined.

Try looking for admin.rb and make sure that it parses.

Also, you may want to try running the migrations one at a time (rake db:migrate VERSION=1, etc.) to see if that helps you track down which migration causes the error, or if it is a problem simply booting the application.

Luke Francl 2008-10-20 18:30:05

Answer 3

A:

It don't points me where i have a Admin constant. There is a way to check at least where should I look? my models, my controllers, etc?

rake db:migrate VERSION=1, gives me a error already. As I told you, am I just trying to finish a project unfinished by another guy.

How can i do a migration file per file?

Regards,

Victor

VP 2008-10-20 18:42:16

Make a backup of your database, then drop it completely and try to migrate to VERSION=1. Then VERSION=2, etc.The Admin constant is probably a model. Is there a file in your app called admin.rb?

Luke Francl 2008-10-20 20:11:49

it's strange. i have a 001_admin.rb but there is no Admin model. in my 001_admin.rb it tries to write in Default class.. make sense?

VP 2008-10-20 20:29:24

anyway i fixed. i just renamed the file to 001_default.rb and worked.

VP 2008-10-20 20:50:47

Answer 4

+2 A:

I suspect you had a migration that created a table and added some data using a model. Later in the project the model got renamed or removed (as did the table maybe?). As the model no longer existed the migrations failed to run, but no one noticed as by that point they were only running a few migrations at a time, not from a clean database.

The lesson here ... if you rename models or tables (or update their validations and fields) then check your migrations run from scratch as well on the current production version.

RichH 2008-10-21 17:01:38

This is very likely the correct answer.

James Baker 2008-10-23 20:14:00

Answer 5

A:

You can try loading the schema all at once instead of executing each migration:

rake db:schema:load

As RichH said there might have been a change to the schema not reflected in the migrations

2008-10-21 18:22:39

ansaurus

tags:

views:

answers:

Rake db:migration problem

related questions