Hey,

Using refresh_from_update immediately before updating the object will not solve the problem (and will only add an additional useless query). It will minimize the risk of working on a stale copy of the data but it wont prevent it.

When talking about a resource that is being updated extensivly (think about a concert ticket sells counter seconds after the opening) you dont want to rely on chance.

Full Stack Developer, Team Leader, Independent. More from me at https://hakibenita.com

Full Stack Developer, Team Leader, Independent. More from me at https://hakibenita.com