Undefined method when accessing through association and uninitialized constant when trying to destroy with :dependent = :destroy

Question

I've tried persistently googling this error, but to no avail. I currently have these models app/models/survey.rb ``` class Survey < ActiveRecord::Base belongs_to :user has_attached_file :original, :default_url => "/public/:class/:attachment/:basename.:extension" has_many :sub_surveys, :dependent => :destroy end ``` app/models/sub_survey.rb ``` class SubSurvey < ActiveRecord::Base belongs_to :survey has_many :questions, :dependent => :destroy end ``` app/models/question.rb ``` class Question < ActiveRecord::Base belongs_to :sub_survey validates_presence_of :sub_survey acts_as_list :scope => :sub_survey #after_destroy :destroy_orphaned_choices has_many :answers, :dependent => :destroy has_many :choices, :dependent => :destroy end ``` app/models/choice.rb ``` class Choices < ActiveRecord::Base belongs_to :question validates_presence_of :question end ``` app/models/answer.rb ``` class Answer < ActiveRecord::Base belongs_to :question belongs_to :user belongs_to :game validates_uniqueness_o…

Accepted Answer

Your `Choices` table has already got a pluralised name which may be causing problems. Ideally that table should be called `Choice` otherwise your `has_many :choices` should specify the `class_name` option too. E.g.

```
has_many :choices, :class_name => 'Choices'
```

Though I'd opt for renaming the class and table `Choice` if you can.

Attachment_fu is probably appearing in the stack trace because they have overridden or aliased the `method_missing` method to add their own behaviour. It's not necessarily anything to be concerned about.

Undefined method when accessing through association and uninitialized constant when trying to destroy with :dependent => :destroy

Solution

Problem