Fascinating article documenting a clear challenge over multiple versions of Rails. My read on the subtext of the article is that these issues of proper SQLite support within Active Record won’t fix with a clever gem or quick script but rather need dedicated effort in the rails core.

What surprises me a little is that the article is written just now in April 2025 but makes no mention of recent developments in rails.

Specially I’m referring to the Rails 8 release. My take away from Rails 8 is that one of the biggest features is significant work towards making SQLite very much a first class citizen of rails, with significant focus on enhancin support for it across the stack.

The text below is from the announcement: “Rails 8 No PASS required”

“Getting SQLite ready for production

On top of the trifecta of Solid adapters that makes it possible for SQLite to power Action Cable, Rails.cache, and Active Job, a bunch of work has gone into making the SQLite adapter and Ruby driver suitable for real production use in Rails 8. At 37signals, we’re building a growing suite of apps that use SQLite in production with ONCE. There are now thousands of installations of both Campfire and Writebook running in the wild that all run SQLite. This has meant a lot of real-world pressure on ensuring that Rails (and Ruby) is working that wonderful file-based database as well as it can be.”

https://rubyonrails.org/2024/11/7/rails-8-no-paas-required

Surely this work bears fruit for the challenges the developer speaks of here. Curious as to if anyone has further insight into what extent Rails 8 addresses the highlighted shortcomings and further if there is a significant gap what would be needed to have this resolved for Rails 9 which I expect is underway.