Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1070975
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T20:38:50+00:00 2026-05-16T20:38:50+00:00

I have an ActiveRecord model with several virtual attribute setters. I want to build

  • 0

I have an ActiveRecord model with several virtual attribute setters. I want to build an object but not save it to the database. One setter must execute before the others. How to do?

As a workaround, I build the object in two steps

@other_model = @some_model.build_other_model
@other_model.setup(params[:other_model)

Where setup is:

class OtherModel < ActiveRecord::Base
  def setup(other_params)
     # execute the important_attribute= setter first
    important_attribute = other_params.delete(:important_attribute)

     # set the other attributes in whatever order they occur in the params hash
    other_params.each { |k,v| self.send("#{k}=",v) }
  end
end

This seems to work, but looks kludgy. Is there a better way?

EDIT

per neutrino‘s suggestion, I added a method to SomeModel:

class SomeModel < ActiveRecord::Base
  def build_other_model(other_params)
    other_model = OtherModel.new(:some_model=>self)
    other_model.setup(other_params)
    other_model
  end
end
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T20:38:51+00:00Added an answer on May 16, 2026 at 8:38 pm

    It’s a good thing that you have this manipulations done in an OtherModel‘s method, because you can just call this method and not worry about the order of assignments. So I would leave this part but just call it from a SomeModel‘s method:

    class SomeModel < ActiveRecord::Base
      def build_other_model(other_params)
        other_model = build_other_model
        other_model.setup(other_params)
        other_model
      end
    end
    

    So then you would have

    @other_model = @some_model.build_other_model(params[:other_model])
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an ActiveRecord model that I would like to convert to xml, but
I have an ActiveRecord model, Foo , which has a name field. I'd like
I have a basic ActiveRecord model in which i have two fields that i
I have this Task model: class Task < ActiveRecord::Base acts_as_tree :order => 'sort_order' end
I have a rails model that looks something like this: class Recipe < ActiveRecord::Base
Suppose you have an ActiveRecord::Observer in one of your Ruby on Rails applications -
I have three models: class ReleaseItem < ActiveRecord::Base has_many :pack_release_items has_one :pack, :through =>
I have the following models. # app/models/domain/domain_object.rb class Domain::DomainObject < ActiveRecord::Base has_many :links_from, :class_name
Have you refactored from an ActiveRecord to a DataMapper pattern? What conditions prompted the
I have a JSON array with ActiveRecord objects. These objects can be reconstructed using

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.