Rails Daily: Ractor Safety and the Great Database Cleanup
Rails merged a cluster of changes making core framework internals safe to run on Ractors, alongside a broad cleanup of database adapter internals from Ryuta Kamizono that trims redundant code around inserts and returning values. A handful of correctness fixes round out the day, including a template digest encoding bug and a scheme-dropping issue in token authentication.
Duration: PT2M24S
Episode overview
This episode is a short developer briefing from Rails Daily.
It explains recent repository work in plain language.
- Show: Rails Daily
- Published: 2026-07-29T06:01:36Z
- Audio duration: PT2M24S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
It's July 29th, 2026, and this is Rails Daily.
Today's biggest thread is Ractor safety. Rails has been steadily removing barriers that keep multi-Ractor apps from using standard framework features, and three merges push that forward. Edouard-chin's PR 57854 makes controller middleware safe to share across Ractors using a copy-on-write approach. His earlier PR…
The second theme is database internals, largely from Ryuta Kamizono. PR 58283 consolidates the returning-column logic that Postgres, SQLite, and MySQL each implemented separately into one abstract adapter method. PR 58285 follows up by stripping insert callers down to only the arguments they actually use. And PR…
A few standalone fixes matter too. PR 58237 fixes an encoding crash when computing template digests for files with non-ASCII text, which could surface as a 500 error under fragment caching. PR 58211 restores the authentication scheme when it's yielded to token-authentication blocks, useful for anyone supporting…
What's next: expect the Ractor-safety work to keep expanding into other subsystems, and expect more of these adapter consolidations as Kamizono continues auditing insert and returning behavior across databases.
T…