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 652205
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T22:14:49+00:00 2026-05-13T22:14:49+00:00

If a model changes an attribute locally, then changes it back, ActiveRecord doesn’t send

  • 0

If a model changes an attribute locally, then changes it back, ActiveRecord doesn’t send the change to the DB. This is great for performance, but if something else changes the database, and I want to revert it to the original value, the change doesn’t take:

model = Model.find(1)
model.update_attribute(:a, 1) # start it off at 1

# some code here that changes model.a to 2
model.a = 2 # I know it changed, reflecting my local model of the change

model.update_attribute(:a, 1) # try change it back, DOESN'T WORK

The last line doesn’t work because AR thinks in the DB it’s still 1, even though something else changed it to 2. How can I force an AR update, or update the cache directly if I know the new value?

Side note: the code that changes it is an update_all query that locks the record, but it has side effects that mess up the cache. Multiple machines read this table. If there’s a better way to do this I’d love to know.

Model.update_all(["locked_by = ?", lock_name], ["id = ? AND locked_by IS NULL", id])
  • 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-13T22:14:49+00:00Added an answer on May 13, 2026 at 10:14 pm

    Use the reload method for this.

    model.reload(:select => "a")
    

    OR

    You can try the will_change! method(Its not clear how your change happens. But you can try this method).

    model.update_attribute(:a, 1) # start it off at 1
    model.a_will_change! #fore warn the model about the change
    model.a = 2  #perform the change
    model.update_attribute(:a, 1)
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 426k
  • Answers 426k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer You can use the quantile and ecdf functions to get… May 15, 2026 at 12:32 pm
  • Editorial Team
    Editorial Team added an answer I tried a few different cases, and this works (will… May 15, 2026 at 12:32 pm
  • Editorial Team
    Editorial Team added an answer can you try window.open(....) ? Edit on opening parent window,… May 15, 2026 at 12:32 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

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.