Project

General

Profile

Actions
Copy link

Bug #12241

closed

Counter cache update didn't pick up changes from after_commit callback

Added by Tomer Brisker over 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Tomer Brisker
Category:
Rails
Target version:
1.10.1
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/2839
Fixed in Releases:
Found in Releases:
1.9.1
Red Hat JIRA:

Description

`after_commit` callback doesn't have a `changes` hash, instead need to use `previous_changes` hash.

Related issues 1 (0 open — 1 closed)

Related to Foreman - Bug #10133: Massive db deadlocks in postgres from hosts_counter updates with counter_cache_fix.rbClosedTomer Brisker04/14/2015Actions
Actions
Copy link
 #1

Updated by Tomer Brisker over 8 years ago

  • Related to Bug #10133: Massive db deadlocks in postgres from hosts_counter updates with counter_cache_fix.rb added
Actions
Copy link
 #2

Updated by The Foreman Bot over 8 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2839 added
  • Pull request deleted ()
Actions
Copy link
 #3

Updated by Dominic Cleal over 8 years ago

  • translation missing: en.field_release set to 104
Actions
Copy link
 #4

Updated by Dominic Cleal over 8 years ago

  • Subject changed from fix for #10133 was incorrect to Counter cache update didn't pick up changes from after_commit callback
  • Category changed from Dashboard to Rails
Actions
Copy link
 #5

Updated by Anonymous over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link

Also available in: Atom PDF