We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
rails changelog
Changelog
Hey there, lovely developers! We've got some snazzy updates to make your coding life a bit more awesome. Let's dive into the goodies! 🎉
New Feature: Now you can see the record count in the generator guide template override example. This little nugget of joy makes it super easy to know how many records you've got on your hands. It's like having a magic mirror that tells you all the secrets of your data. 🪞✨
Bugfix: We've squashed a bug in the include?
method on strict-loaded has-and-belongs-to-many (HABTM) associations in ActiveRecord. No more StrictLoadingViolationError
when checking if a new record is included in a loaded association. Phew! Now, it just uses the target
like a pro, making your life a whole lot easier. 🐛🚫
Improvement: Added some sparkle to the CHANGELOG! It now includes recent updates like the fix for unpersisted record checks in strictly loaded HABTM associations and a cool new feature that lets you change transaction isolation for all database connection pools within a block. It's like a party for your database settings! 🎊🎈
Improvement: We've translated the Trilogy::SSLError
to ActiveRecord::ConnectionFailed
. This means more consistent and friendly error messages when dealing with SSL-related connection issues. Your database connections just got a whole lot smoother. 🌊🔧
That's all for now, folks! Keep on coding and making magic happen. 🧙♂️💻
Included Commits
This commit adds functionality to display the record count within the generator guide template override example. By implementing this feature, users can now easily see the total number of records processed, enhancing the usability and clarity of the template. This improvement aims to provide better insights during the generation process, allowing developers and users to have a clearer understanding of the data being handled.
Overall, the inclusion of the record count serves as a valuable addition to the generator guide template, making it more informative and user-friendly. This change underscores the commitment to improving the developer experience by providing essential information at a glance.
Files changed
This commit addresses an issue with the include?
method on strict-loaded has-and-belongs-to-many (HABTM) associations in ActiveRecord. Previously, checking if a new record (e.g., Post.new
) was included in a strict-loaded HABTM association would raise a StrictLoadingViolationError
, even when the association was already loaded. The fix ensures that if the association is loaded, the method will now use the target
to check for inclusion, eliminating the unnecessary query to the Through association, which is only required when the association is dirty or contains newly built records.
The changes involve modifications to the collection_association.rb
file, where the logic of the include?
method has been rearranged. Additionally, the commit introduces a test case in strict_loading_test.rb
to verify that no error is raised when checking for inclusion of a new record in an eagerly loaded HABTM relation. This enhancement improves the handling of strict loading in ActiveRecord, making it more robust and user-friendly.
Files changed
- activerecord/lib/active_record/associations/collection_association.rb
- activerecord/test/cases/strict_loading_test.rb
This commit adds a new entry to the CHANGELOG for ActiveRecord, documenting a couple of recent updates. Notably, it includes a fix for the issue of checking whether an unpersisted record is included in a strictly loaded has_and_belongs_to_many
association, contributed by Hartley McGuire.
Additionally, the commit highlights a new feature that allows developers to change transaction isolation for all database connection pools within a block, which can be particularly beneficial for applications that require dynamic adjustments to database transaction settings. Overall, the changes enhance both functionality and clarity in ActiveRecord's capabilities.
Files changed
- activerecord/CHANGELOG.md
This commit addresses the translation of the Trilogy::SSLError
exception to the ActiveRecord::ConnectionFailed
exception within the Rails framework. By implementing this change, the commit aims to improve error handling and consistency when dealing with SSL-related connection issues in applications using the Trilogy gem for MySQL connections.
The update resolves issue #55126, ensuring that developers receive a more standardized error message when encountering SSL errors, thereby enhancing the overall robustness of database connection management in ActiveRecord.