method
inverse_which_updates_counter_cache
v6.1.3.1 -
Show latest stable
-
0 notes -
Class: AbstractReflection
- 1.0.0
- 1.1.6
- 1.2.6
- 2.0.3
- 2.1.0
- 2.2.1
- 2.3.8
- 3.0.0
- 3.0.9
- 3.1.0
- 3.2.1
- 3.2.8
- 3.2.13
- 4.0.2
- 4.1.8
- 4.2.1
- 4.2.7
- 4.2.9
- 5.0.0.1 (0)
- 5.1.7 (0)
- 5.2.3 (0)
- 6.0.0 (0)
- 6.1.3.1 (0)
- 6.1.7.7 (0)
- 7.0.0 (-38)
- 7.1.3.2 (0)
- 7.1.3.4 (0)
- What's this?
inverse_which_updates_counter_cache()
public
This shit is nasty. We need to avoid the following situation:
* An associated record is deleted via record.destroy * Hence the callbacks run, and they find a belongs_to on the record with a :counter_cache options which points back at our owner. So they update the counter cache. * In which case, we must make sure to *not* update the counter cache, or else it will be decremented twice.
Hence this method.