Editing article

Title

Summary

Content

Hi, <a href="https://twitter.com/morgoth85">Wojtek</a> here exploring this week’s changes.

<a href="https://rubyonrails.org/world/2024">Rails World 2024 edition website is now live</a> 
With tickets going on sale in April.

<a href="https://github.com/rails/rails/pull/51474">Allow to register transaction callbacks outside of a record</a> 
ActiveRecord::Base.transaction now yields an ActiveRecord::Transaction object, which allows to register callbacks on it.
<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Article.transaction do |transaction|
 article.update(published: true)
 transaction.after_commit do
 PublishNotificationMailer.with(article: article).deliver_later
 end
end
</code></pre></div></div>

Added ActiveRecord::Base.current_transaction which also allows to register callbacks on it.
<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Article.current_transaction.after_commit do
 PublishNotificationMailer.with(article: article).deliver_later
end
</code></pre></div></div>

Add ActiveRecord.after_all_transactions_commit callback.

Useful for code that may run either inside or outside a transaction and need to perform works after the state changes have been properly peristed.
<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>def publish_article(article)
 article.update(published: true)
 ActiveRecord.after_all_transactions_commit do
 PublishNotificationMailer.with(article: article).deliver_later
 end
end
</code></pre></div></div>

<a href="https://github.com/rails/rails/pull/51426">Automatically delay Active Job enqueues to after commit</a> 
A common mistake with Active Job is to enqueue jobs from inside a transaction, causing them to potentially be picked and ran by another process, before the transaction is committed, which result in various errors.

<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Topic.transaction do
 topic = Topic.create
 NewTopicNotificationJob.perform_later(topic)
end
</code></pre></div></div>

Now Active Job will automatically defer the enqueuing to after the transaction is committed, and drop the job if the transaction is rolled back.

Various queue implementations can choose to disable this behavior, and users can disable it, or force it on a per job basis:
<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>class NewTopicNotificationJob &lt; ApplicationJob
 self.enqueue_after_transaction_commit = :never # or :always or :default
end
</code></pre></div></div>

<a href="https://github.com/rails/rails/pull/51457">Add queries count to template rendering instrumentation</a> 
There is often a need to quickly see how many SQL queries the current action produced. For example, to quickly check if N+1 was solved or if the caching is working and so the number of queries reduced etc. This can be done manually by inspecting the logs and counting the number of queries, but for largish actions with tens-hundreds of SQL queries this is not a simple task.

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code># Before
Completed 200 OK in 3804ms (Views: 41.0ms | ActiveRecord: 33.5ms | Allocations: 112788)
# After
Completed 200 OK in 3804ms (Views: 41.0ms | ActiveRecord: 33.5ms (2 queries, 1 cached) | Allocations: 112788)
</code></pre></div></div>

<a href="https://github.com/rails/rails/pull/51453">Add the ability to ignore counter cache columns while they are backfilling</a> 
Starting to use counter caches on existing large tables can be troublesome, because the column values must be backfilled separately of the column addition (to not lock the table for too long) and before the use of :counter_cache (otherwise methods like size/any?, which use counter caches internally, can produce incorrect results). People usually use database triggers or callbacks on child associations while backfilling before introducing a counter cache configuration to the association.

Now, to safely backfill the column, while keeping the column updated with child records added/removed, use:
<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>class Comment &lt; ApplicationRecord
 belongs_to :post, counter_cache: { active: false }
end
</code></pre></div></div>

While the counter cache is not “active”, the methods like size/any? will not use it, but get the results directly from the database. After the counter cache column is backfilled, simply remove the { active: false } part from the counter cache definition, and it will now be used by the mentioned methods.

<a href="https://github.com/rails/rails/pull/50941">Retry Actionable Error when running tests</a> 
Allow Actionable Errors encountered when running tests to be retried. This feature will only be present on interactive terminals.

<a href="https://github.com/rails/rails/pull/51478">Raise named exception when database reports an invalid version</a> 
When the MySQL database returns an invalid version string the ActiveRecord::ActiveRecordError error will now be raised.

<a href="https://github.com/rails/rails/pull/51447">Make ActiveSupport::BacktraceCleaner copy filters and silencers on dup and clone</a> 
 Previously the copy would still share the internal silencers and filters array, causing state to leak.

You can view the whole list of changes <a href="https://github.com/rails/rails/compare/@%7B2024-03-29%7D...main@%7B2024-04-05%7D">here</a>.
We had <a href="https://contributors.rubyonrails.org/contributors/in-time-window/20240329-20240405">16 contributors</a> to the Rails codebase this past week!

Until next time!

<a href="https://world.hey.com/this.week.in.rails">Subscribe</a> to get these updates mailed to you.

Author

Link

Published date

Image url

Feed url

Guid

Hidden blurb

--- !ruby/object:Feedjira::Parser::AtomEntry
author: Wojtek
content: |-
 Hi, <a href="https://twitter.com/morgoth85">Wojtek</a> here exploring this week’s changes.

<a href="https://rubyonrails.org/world/2024">Rails World 2024 edition website is now live</a> 
 With tickets going on sale in April.

<a href="https://github.com/rails/rails/pull/51474">Allow to register transaction callbacks outside of a record</a> 
 ActiveRecord::Base.transaction now yields an ActiveRecord::Transaction object, which allows to register callbacks on it.
 <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Article.transaction do |transaction|
 article.update(published: true)
 transaction.after_commit do
 PublishNotificationMailer.with(article: article).deliver_later
 end
 end
 </code></pre></div></div>

Added ActiveRecord::Base.current_transaction which also allows to register callbacks on it.
 <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Article.current_transaction.after_commit do
 PublishNotificationMailer.with(article: article).deliver_later
 end
 </code></pre></div></div>

Add ActiveRecord.after_all_transactions_commit callback.

Useful for code that may run either inside or outside a transaction and need to perform works after the state changes have been properly peristed.
 <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>def publish_article(article)
 article.update(published: true)
 ActiveRecord.after_all_transactions_commit do
 PublishNotificationMailer.with(article: article).deliver_later
 end
 end
 </code></pre></div></div>

<a href="https://github.com/rails/rails/pull/51426">Automatically delay Active Job enqueues to after commit</a> 
 A common mistake with Active Job is to enqueue jobs from inside a transaction, causing them to potentially be picked and ran by another process, before the transaction is committed, which result in various errors.

<div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>Topic.transaction do
 topic = Topic.create
 NewTopicNotificationJob.perform_later(topic)
 end
 </code></pre></div></div>

Now Active Job will automatically defer the enqueuing to after the transaction is committed, and drop the job if the transaction is rolled back.

Various queue implementations can choose to disable this behavior, and users can disable it, or force it on a per job basis:
 <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>class NewTopicNotificationJob &lt; ApplicationJob
 self.enqueue_after_transaction_commit = :never # or :always or :default
 end
 </code></pre></div></div>

<a href="https://github.com/rails/rails/pull/51457">Add queries count to template rendering instrumentation</a> 
 There is often a need to quickly see how many SQL queries the current action produced. For example, to quickly check if N+1 was solved or if the caching is working and so the number of queries reduced etc. This can be done manually by inspecting the logs and counting the number of queries, but for largish actions with tens-hundreds of SQL queries this is not a simple task.

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code># Before
 Completed 200 OK in 3804ms (Views: 41.0ms | ActiveRecord: 33.5ms | Allocations: 112788)
 # After
 Completed 200 OK in 3804ms (Views: 41.0ms | ActiveRecord: 33.5ms (2 queries, 1 cached) | Allocations: 112788)
 </code></pre></div></div>

<a href="https://github.com/rails/rails/pull/51453">Add the ability to ignore counter cache columns while they are backfilling</a> 
 Starting to use counter caches on existing large tables can be troublesome, because the column values must be backfilled separately of the column addition (to not lock the table for too long) and before the use of :counter_cache (otherwise methods like size/any?, which use counter caches internally, can produce incorrect results). People usually use database triggers or callbacks on child associations while backfilling before introducing a counter cache configuration to the association.

Now, to safely backfill the column, while keeping the column updated with child records added/removed, use:
 <div class="language-ruby highlighter-rouge"><div class="highlight"><pre class="highlight"><code>class Comment &lt; ApplicationRecord
 belongs_to :post, counter_cache: { active: false }
 end
 </code></pre></div></div>

<a href="https://github.com/rails/rails/pull/50941">Retry Actionable Error when running tests</a> 
 Allow Actionable Errors encountered when running tests to be retried. This feature will only be present on interactive terminals.

<a href="https://github.com/rails/rails/pull/51478">Raise named exception when database reports an invalid version</a> 
 When the MySQL database returns an invalid version string the ActiveRecord::ActiveRecordError error will now be raised.

<a href="https://github.com/rails/rails/pull/51447">Make ActiveSupport::BacktraceCleaner copy filters and silencers on dup and clone</a> 
 Previously the copy would still share the internal silencers and filters array, causing state to leak.

You can view the whole list of changes <a href="https://github.com/rails/rails/compare/@%7B2024-03-29%7D...main@%7B2024-04-05%7D">here</a>.
 We had <a href="https://contributors.rubyonrails.org/contributors/in-time-window/20240329-20240405">16 contributors</a> to the Rails codebase this past week!

Until next time!

<a href="https://world.hey.com/this.week.in.rails">Subscribe</a> to get these updates mailed to you.
title_type: html
title: Deferring jobs enqueueing to after the transaction commit, queries count in
 rendering logs and more
links:
- https://rubyonrails.org/2024/4/5/this-week-in-rails
published: 2024-04-05 00:00:00.000000000 Z
entry_id: https://rubyonrails.org/2024/4/5/this-week-in-rails
summary: Hi, Wojtek here exploring this week’s changes.
categories:
- news
carlessian_info:
 news_filer_version: 2
 newspaper: Ruby on Rails
 macro_region: Technology
rss_fields:
- author
- content
- title_type
- title
- links
- published
- entry_id
- summary
- categories
- url
- updated
- raw_title
url: https://rubyonrails.org/2024/4/5/this-week-in-rails
updated: 2024-04-05 00:00:00.000000000 Z
raw_title: Deferring jobs enqueueing to after the transaction commit, queries count
 in rendering logs and more

Language

Active

Ricc internal notes

Ricc source

Show this article Back to articles