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

Don't run commit callbacks on first saved instances in transaction

Browse Source 
It probably doesn't directly affect us, since we don't use
`after_commit` callbacks, and, among our dependencies, AFAIK only the
Devise gem uses them, to send the email with confirmation/reconfirmation
instructions.

The reasons for this change are explained in the guide to configure
Rails [1], while the pull request introducing the change has a couple of
great examples in its description [2].

[1] https://guides.rubyonrails.org/v7.1/configuring.html#config-active-record-run-commit-callbacks-on-first-saved-instances-in-transaction
[2] Pull request 45280 in https://github.com/rails/rails
This commit is contained in:
Javi Martín
2024-04-15 04:08:12 +02:00
parent fbb40d701b
commit 6eebe4e984
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

@@ -55,7 +55,7 @@ Rails.application.config.active_record.encryption.support_sha1_for_non_determini
# state which matches what was committed to the database, typically the last # state which matches what was committed to the database, typically the last
# instance to save. # instance to save.
#++ #++
# Rails.application.config.active_record.run_commit_callbacks_on_first_saved_instances_in_transaction = false Rails.application.config.active_record.run_commit_callbacks_on_first_saved_instances_in_transaction = false
### ###
# Configures SQLite with a strict strings mode, which disables double-quoted string literals. # Configures SQLite with a strict strings mode, which disables double-quoted string literals.