The Wire · Showcase
RAILS SHIPS QUERY LOG CONTROL AND CLEANS UP PRIMARY KEY PLUMBING
By RepoJournal · Filed · About Rails
Per-pool query log configuration lands in Rails, letting you silence noisy database connections without framework-wide toggles.
Rails merged a significant query logging refinement [1] that adds fine-grained control over query_log_tags at the connection pool level. You can now disable query logging per database entry in database.yml instead of an all-or-nothing approach, which means you can keep logs clean on read replicas or noisy analytics connections without affecting your primary. The framework also shipped a primary key refactor [2] that removes a class ivar alias, making it easier to keep primary_key and primary_key_definition in sync going forward. In parallel, the team landed validation improvements for retry_on [4] that catch invalid wait arguments at class definition time rather than at runtime. Test infrastructure fixes [3] addressed concurrency issues in the Ruby pre-3.3.5 WeakThreadKeyMap fallback and resolved lingering timing issues from earlier test rewrites. Meanwhile, the Rails website updated Intercom branding to Fin [5] across member pages, the homepage, and the Foundation section, with a follow-up logo correction [6] to ensure consistency.
One email a day. Unsubscribe in one click.
Keep up with Rails in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
References
- [1] Enable per-pool query log tags prepend config ↗ rails/rails
- [2] Remove primary_key class ivar rails/rails
- [3] More test fixes ↗ rails/rails
- [4] Merge pull request #57765 from 55728/fix-retry-on-wait-type-validation rails/rails
- [5] Update Intercom to Fin (#675) rails/website
- [6] Correcting logo (#677) rails/website