CODEWITHSUNDEEP
ruby-on-railscallback
Kevin Dewalt
Kevin Dewalt

Reputation: 777

How can I access ActiveRecord Associations in class callbacks in rails?

Updated

Appears to be a precedence error and nothing to do with the question I originally asked. See discussion below.

Original question

Is it possible to use active record associations in callbacks? I've tested this code in the console and it works fine as long as it isn't in a callback. I'm trying to create callbacks that pull attributes from other associated models and I keep getting errors of nil.attribute.

If callbacks are not the correct approach to take, how would one do a similar action in rails? If the associations are simple, you could use create_association(attributes => ), but as associations get more complex this starts to get messy.

For example...

class User < ActiveRecord::Base
  belongs_to :b
  before_validation_on_create {|user| user.create_b} #note, other logic prevents creating multiple b
end

class B < ActiveRecord::Base
  has_many :users, :dependent => destroy
  after_create{ |b| b.create_c }
  has_one :c
end

class C < ActiveRecord::Base
  belongs_to :b
  after_create :create_alert_email

  private
  def create_alert_email 
    self.alert_email = User.find_by_b_id(self.b_id).email  #error, looks for nil.email
  end
end

Upvotes: 1

Views: 1112

Answers (1)

Simone Carletti
Simone Carletti

Reputation: 176562

Off course associations are available in your callbacks. After all, the create_after_email is simply a method. You can even call it alone, without using a callback. ActiveRecord doesn't apply any special flag to callback methods to prevent them from working as any other method.

Also notice you are running a User#find query directly without taking advantage of any association method. An other reason why ActiveRecord association feature should not be the guilty in this case.

The reason why you are getting the error should probably searched somewhere else. Be sure self.b_id is set and references a valid record. Perhaps it is nil or actually there's no User record with that value. In fact, you don't test whether the query returns a record or nil: you are assuming a record with that value always exists. Are you sure this assumption is always statisfied?

Upvotes: 2

Related Questions