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 -~----------~----~----~----~------~----~------~--~---
