Rails - Best-Practice: How to create dependent has_one relations

Question

What's the best practice to create has_one relations?

For example, if I have a user model, and it must have a profile...

How could I accomplish that?

One solution would be:

# user.rb class User << ActiveRecord::Base   after_create :set_default_association    def set_default_association     self.create_profile   end end 

But that doesn't seem very clean... Any suggestions?

Answer 1

Best practice to create has_one relation is to use the ActiveRecord callback before_create rather than after_create. Or use an even earlier callback and deal with the issues (if any) of the child not passing its own validation step.

Because:

• with good coding, you have the opportunity for the child record's validations to be shown to the user if the validations fail
• it's cleaner and explicitly supported by ActiveRecord -- AR automagically fills in the foreign key in the child record after it saves the parent record (on create). AR then saves the child record as part of creating the parent record.

How to do it:

# in your User model... has_one :profile before_create :build_default_profile  private def build_default_profile   # build default profile instance. Will use default params.   # The foreign key to the owning User model is set automatically   build_profile   true # Always return true in callbacks as the normal 'continue' state        # Assumes that the default_profile can **always** be created.        # or        # Check the validation of the profile. If it is not valid, then        # return false from the callback. Best to use a before_validation         # if doing this. View code should check the errors of the child.        # Or add the child's errors to the User model's error array of the :base        # error item end