rails changelog

The commit addresses an issue related to the retrieval of records using a nil composite primary key association. It implements a fix that ensures the system can correctly identify and handle cases where the composite primary key is not provided, thereby preventing errors and improving the reliability of data fetching operations.

Additionally, the changes likely include updates to the underlying logic that governs how associations are managed in the database, ensuring that nil values are appropriately accounted for in queries and associations. This enhancement aims to streamline data interactions and enhance overall application stability.

Files changed

The recent commit enhances the ActiveRecord::Base#select method by preserving duplicate columns in the selection process. Previously, when multiple identical column names were specified in a query, only the first occurrence would be retained, potentially leading to data loss or unexpected behavior. This update ensures that all specified duplicate columns are included in the result set, allowing developers to work with the full dataset as intended.

By maintaining duplicates, the commit improves the flexibility of querying in ActiveRecord, enabling developers to handle scenarios where the same column might be needed multiple times, such as in complex joins or when performing aggregate functions. This change is expected to streamline data retrieval and enhance the overall usability of the ActiveRecord querying interface.

Files changed

This commit addresses the handling of NOT VALID constraints in PostgreSQL during the database schema dumping process. It clarifies that while FOREIGN KEY constraints are not included in the create_table statements, CHECK constraints, which are supported by all database adapters, will only dump NOT VALID constraints as ALTER TABLE statements. This approach ensures that the PostgreSQL-specific NOT VALID option does not impact the behavior of other database adapters, maintaining compatibility across different systems.

The change resolves issue #53732 by ensuring that NOT VALID constraints are appropriately managed during schema dumps, thereby preventing potential conflicts and ensuring that the ALTER TABLE options are restored correctly. This improvement enhances the overall functionality and reliability of the schema management process in PostgreSQL.

Files changed

This commit disables the YJIT (Yet another Just-In-Time Compiler) feature in development and test environments. The rationale behind this decision is that these environments often involve frequent code reloading and method redefining, such as during mocking, which diminishes the performance benefits that YJIT typically provides. As a result, enabling YJIT in these contexts is not generally advantageous.

The commit was co-authored by Jean Boussier and aims to streamline the development process by preventing unnecessary complexity and potential slowdowns associated with YJIT in scenarios where its optimizations are not effectively utilized.

Files changed

This commit introduces the use of WeakKeyMap for the connection lease registry in the Rails framework, addressing a previous limitation due to a bug in WeakKeyMap that could crash the Ruby VM. With the release of Ruby version 3.3.5, the functionality is now stable and safe to implement.

The change enhances the connection lease registry by leveraging the properties of WeakKeyMap, which allows for more efficient memory management by automatically removing entries when their keys are no longer in use. This update is a follow-up to a prior pull request and marks a significant improvement in the handling of connection leases within the Rails application.

Files changed

The commit addresses an issue related to the documented order of the to_prepare initialization event in the codebase, specifically fixing a problem identified in issue #53682. The update ensures that the documentation accurately reflects the correct sequence in which the to_prepare event is triggered during the initialization process.

By clarifying the order of operations, this change aims to enhance the understanding and usability of the event for developers, thereby improving the overall quality and reliability of the documentation associated with the initialization events.

Files changed

The recent commit addresses an issue in the example code for Request-Based Constraints within the routing documentation. Specifically, it modifies the code snippet by simplifying the structure of the namespace for the admin subdomain, removing unnecessary lines to enhance clarity and readability.

In the updated example, the namespace :admin block has been removed, allowing the constraints block to directly encompass the resources :photos declaration. This change streamlines the example, making it easier for users to understand how to implement subdomain constraints in their routing configurations. Overall, the commit improves the documentation by providing a more concise and effective illustration of the concept.

Files changed

• guides/source/routing.md