consul/grecia
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Run after_commit callbacks in order defined

Browse Source 
This change doesn't affect us, since we don't use `after_commit`
callbacks, and, among our dependencies, AFAIK only the Devise gem uses
them, and it only defines one after_commit callback when creating a
record and another one when updating it, so we're never going to have
more than one callback being executed after a transaction is finished.
This commit is contained in:
Javi Martín
2024-04-15 16:38:26 +02:00
parent 0d0f3a48ff
commit d6b642a23d
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
config/initializers/new_framework_defaults_7_1.rb
View File

@@ -204,7 +204,7 @@ Rails.application.config.active_record.marshalling_format_version = 7.1
# This matches the behaviour of all other callbacks. # This matches the behaviour of all other callbacks.
# In previous versions of Rails, they ran in the inverse order. # In previous versions of Rails, they ran in the inverse order.
#++ #++
# Rails.application.config.active_record.run_after_transaction_callbacks_in_order_defined = true Rails.application.config.active_record.run_after_transaction_callbacks_in_order_defined = true
### ###
# Whether a `transaction` block is committed or rolled back when exited via `return`, `break` or `throw`. # Whether a `transaction` block is committed or rolled back when exited via `return`, `break` or `throw`.