Ahh. rake test. Well look at all your test fixtures. there is probably a column in one of those files that does not exist in real life.
H On Mon, Sep 22, 2008 at 12:06 AM, Victor Hahn <[EMAIL PROTECTED]> wrote: > Hank, > > thanks a lot for your answer! Actually, I'm still in development mode > on the server - didn't even dare touching this yet. I'm really > startled by the fact that the test complains about a "test" column. > There is none, I just double-checked the database and the migrations. > There is a "content_type" column because it's needed by attachment_fu, > but I suppose this shouldn't be a problem. After all, I still really > don't understand why it works on my laptop but not on the server using > exactly the same versions of Rails and attachment_fu. > > The error about the "test" column occurs when running "rake test" in > the attachment_fu directory. Are there any other places that could > have database definition? I noticed that "rake test" doesn't print any > errors when run in the attachment_fu directory on my laptop. > > Best regards, > Victor > > > On 21 Sep., 23:14, blasterpal <[EMAIL PROTECTED]> wrote: >> Victor, >> >> I have found production/test deployment oddities can be resolved by >> switching your local "development" into "production" mode to force >> Rails to behave like it would on your server. >> >> The quickest way to do this is to edit your database.yml and copy your >> "development:" block and rename to "production:". Then change the name >> of the original "production:" block to something else like >> "production_off:". Restart your local development server but add the "- >> e production" or just "production" argument and you might find the >> same behavior. Now have eliminated your server as the culprit of the >> issue. For example, it could be a problem in the way you are using >> attachment_fu. Development mode and production mode are not 100% >> congruous in my experience. >> >> secondly, make sure you are not using reserved column names in your >> tables. This looks suspicious in that regard: >> >> ...The single-table inheritance mechanism >> failed to locate the subclass: 'NULL'.... >> >> A good example is a "type" column. This is reserved for polymorphism >> and can introduce some unwanted automagically ActiveRecord behavior. >> >> Hank > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
