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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T10:54:33+00:00 2026-06-07T10:54:33+00:00

In our Rails 3.2.6 app, we have a model attribute named ‘version’ that is

  • 0

In our Rails 3.2.6 app, we have a model attribute named ‘version’ that is incremented at the database level whenever an instance is created or updated (via trigger). However, after we do a successful create or update, the new value set by the database is not being returned to our instance, unless we explicitly do an instance.reload.

Does anyone know of a way to have active record automatically reload the instance after persisting to the database?

Background

In our Rails 3.2.6 app, we have a 3 tables that each have a ‘version’ column. Across all 3 tables, the ‘version’ integer column needs to be incremented during each insert and update, and the ‘version’ must never repeat.

Simple solution: we’ve created a version_sequence in postgres that all 3 tables share. We have a small trigger that updates the version column of any record from these tables with the nextval(‘version_sequence’) value:

  -- Resource Version Sequence
  CREATE SEQUENCE resource_versions_seq;


  -- Resource Version Trigger
  CREATE FUNCTION update_resource_version() RETURNS trigger AS $update_resource_version$
    BEGIN
      NEW.version := nextval('resource_versions_seq');
      RETURN NEW;
    END;
  $update_resource_version$ LANGUAGE plpgsql;

However, when we create, save, or update_attributes in active_record, the new ‘version’ value is not being reloaded after the record is persisted.

  • 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-06-07T10:54:35+00:00Added an answer on June 7, 2026 at 10:54 am

    How about using the after_save callback? In this callback you could fetch just that field and then set it on the model. Something like this:

    class Thing < ActiveRecord::Base
      after_save :refresh_version
    
      def refresh_version
        self.version = Thing.find(self.id).select(:version)
      end
    
    end
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Some of the users of our Ruby on Rails app have complained that page
In our Rails app that runs in Facebook canvas, we have a workflow where
I'm looking into database backup options for our Heroku rails app, and it looks
We have a Rails app that has some pages that are available to all
Our Rails app is using Restful Authentication for user/session management and it seems that
We recently upgraded our rails app from version 3.0.3 to 3.1.0. The application runs
I'm about to start rewriting bits and pieces of our Rails app that do
Consider this scenario. We have an internal Rails 2 app that connects to a
We have already built a rails app that has several users and an image
We've deployed our rails app to EC2. In our setup, we have two proxies

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.