The Wire · Showcase
RAILS FIXES TIMESTAMP PRECISION AND MIGRATION REVERSIBILITY IN OVERNIGHT PUSH
By RepoJournal · Filed · About Rails
PostgreSQL timestamp columns now report their actual microsecond precision to Active Record, fixing a long-standing type casting inconsistency that could silently corrupt datetime handling across your stack.
The Rails team shipped three critical fixes that tighten database schema handling. First, Rails now correctly reports PostgreSQL's default timestamp/time precision as 6 (microseconds) [1], ensuring type casting normalizes timestamps consistently with what's actually stored. This matters because bare timestamp columns without explicit precision were being misreported, causing data integrity issues on read. Second, the migration system now properly handles reversibility for `drop_virtual_table` [2] and `remove_check_constraint` with the `if_exists` flag [3], so your down migrations won't fail on already-missing objects. In parallel, the docs got fixed: month_field and week_field examples were incorrectly showing type="date" [4], and select helpers were documenting impossible boolean attributes. Over in the concurrency department, ActiveSupport JSON encoders are now Ractor-shareable [5], clearing the way for safer concurrent encoding in Ruby 3.2+. Meanwhile, solid_cable got a stability patch: reconnect attempts now reset properly after successful database access [6], preventing cascading failures on temporary connection hiccups.
Action items
- → Review timestamp handling in datetime-heavy models and add tests for microsecond precision consistency rails/rails [plan]
- → Update any custom migrations using drop_virtual_table or remove_check_constraint to verify reversibility rails/rails [plan]
- → If running solid_cable, upgrade to pick up the reconnect_attempt reset fix rails/solid_cable [monitor]
References
- [1] Report PostgreSQL default timestamp/time precision as 6 ↗ rails/rails
- [2] Merge pull request #57872 from 55728/fix-invert-drop-virtual-table-positional rails/rails
- [3] Merge pull request #57871 from 55728/fix-remove-check-constraint-if-exists-expression rails/rails
- [4] Fix incorrect RDoc examples in ActionView form helpers [ci skip] rails/rails
- [5] Make ActiveSupport::JSON encoders Ractor-shareable ↗ rails/rails
- [6] Reset reconnect_attempt after successfuly accessing the DB. ↗ rails/solid_cable
FAQ
- What changed in Rails on June 27, 2026?
- PostgreSQL timestamp columns now report their actual microsecond precision to Active Record, fixing a long-standing type casting inconsistency that could silently corrupt datetime handling across your stack.
- What should Rails teams do about it?
- Review timestamp handling in datetime-heavy models and add tests for microsecond precision consistency • Update any custom migrations using drop_virtual_table or remove_check_constraint to verify reversibility • If running solid_cable, upgrade to pick up the reconnect_attempt reset fix
- Which Rails repositories shipped on June 27, 2026?
- rails/rails, rails/solid_cable