activerecord 8.0.2 → 8.1.0.beta1

data/CHANGELOG.md

@@ -1,667 +1,713 @@
-## Rails 8.0.2 (March 12, 2025) ##
+## Rails 8.1.0.beta1 (September 04, 2025) ##
 
-*   No changes.
+*   Remove deprecated `:unsigned_float` and `:unsigned_decimal` column methods for MySQL.
 
+    *Rafael Mendonça França*
 
-## Rails 8.0.2 (March 12, 2025) ##
+*   Remove deprecated `:retries` option for the SQLite3 adapter.
 
-*   Fix inverting `rename_enum_value` when `:from`/`:to` are provided.
+    *Rafael Mendonça França*
 
-    *fatkodima*
+*   Introduce new database configuration options `keepalive`, `max_age`, and
+    `min_connections` -- and rename `pool` to `max_connections` to match.
 
-*   Prevent persisting invalid record.
+    There are no changes to default behavior, but these allow for more specific
+    control over pool behavior.
 
-    *Edouard Chin*
+    *Matthew Draper*, *Chris AtLee*, *Rachael Wright-Munn*
 
-*   Fix inverting `drop_table` without options.
+*   Move `LIMIT` validation from query generation to when `limit()` is called.
 
-    *fatkodima*
+    *Hartley McGuire*, *Shuyang*
 
-*   Fix count with group by qualified name on loaded relation.
+*   Add `ActiveRecord::CheckViolation` error class for check constraint violations.
 
     *Ryuta Kamizono*
 
-*   Fix `sum` with qualified name on loaded relation.
-
-    *Chris Gunther*
+*   Add `ActiveRecord::ExclusionViolation` error class for exclusion constraint violations.
 
-*   The SQLite3 adapter quotes non-finite Numeric values like "Infinity" and "NaN".
-
-    *Mike Dalessio*
+    When an exclusion constraint is violated in PostgreSQL, the error will now be raised
+    as `ActiveRecord::ExclusionViolation` instead of the generic `ActiveRecord::StatementInvalid`,
+    making it easier to handle these specific constraint violations in application code.
 
-*   Handle libpq returning a database version of 0 on no/bad connection in `PostgreSQLAdapter`.
-
-    Before, this version would be cached and an error would be raised during connection configuration when
-    comparing it with the minimum required version for the adapter. This meant that the connection could
-    never be successfully configured on subsequent reconnection attempts.
-
-    Now, this is treated as a connection failure consistent with libpq, raising a `ActiveRecord::ConnectionFailed`
-    and ensuring the version isn't cached, which allows the version to be retrieved on the next connection attempt.
-
-    *Joshua Young*, *Rian McGuire*
-
-*   Fix error handling during connection configuration.
-
-    Active Record wasn't properly handling errors during the connection configuration phase.
-    This could lead to a partially configured connection being used, resulting in various exceptions,
-    the most common being with the PostgreSQLAdapter raising `undefined method `key?' for nil`
-    or `TypeError: wrong argument type nil (expected PG::TypeMap)`.
-
-    *Jean Boussier*
+    This follows the same pattern as other constraint violation error classes like
+    `RecordNotUnique` for unique constraint violations and `InvalidForeignKey` for
+    foreign key constraint violations.
 
-*   Fix a case where a non-retryable query could be marked retryable.
+    *Ryuta Kamizono*
 
-    *Hartley McGuire*
+*   Attributes filtered by `filter_attributes` will now also be filtered by `filter_parameters`
+    so sensitive information is not leaked.
 
-*   Handle circular references when autosaving associations.
+    *Jill Klang*
 
-    *zzak*
+*   Add `connection.current_transaction.isolation` API to check current transaction's isolation level.
 
-*   PoolConfig no longer keeps a reference to the connection class.
+    Returns the isolation level if it was explicitly set via the `isolation:` parameter
+    or through `ActiveRecord.with_transaction_isolation_level`, otherwise returns `nil`.
+    Nested transactions return the parent transaction's isolation level.
 
-    Keeping a reference to the class caused subtle issues when combined with reloading in
-    development. Fixes #54343.
+    ```ruby
+    # Returns nil when no transaction
+    User.connection.current_transaction.isolation # => nil
 
-    *Mike Dalessio*
+    # Returns explicitly set isolation level
+    User.transaction(isolation: :serializable) do
+      User.connection.current_transaction.isolation # => :serializable
+    end
 
-*   Fix SQL notifications sometimes not sent when using async queries.
+    # Returns nil when isolation not explicitly set
+    User.transaction do
+      User.connection.current_transaction.isolation # => nil
+    end
 
-    ```ruby
-    Post.async_count
-    ActiveSupport::Notifications.subscribed(->(*) { "Will never reach here" }) do
-      Post.count
+    # Nested transactions inherit parent's isolation
+    User.transaction(isolation: :read_committed) do
+      User.transaction do
+        User.connection.current_transaction.isolation # => :read_committed
+      end
     end
     ```
 
-    In rare circumstances and under the right race condition, Active Support notifications
-    would no longer be dispatched after using an asynchronous query.
-    This is now fixed.
-
-    *Edouard Chin*
-
-*   Fix support for PostgreSQL enum types with commas in their name.
+    *Kir Shatrov*
 
-    *Arthur Hess*
+*   Emit a warning for pg gem < 1.6.0 when using PostgreSQL 18+
 
-*   Fix inserts on MySQL with no RETURNING support for a table with multiple auto populated columns.
+    *Yasuo Honda*
 
-    *Nikita Vasilevsky*
-
-*   Fix joining on a scoped association with string joins and bind parameters.
+*   Fix `#merge` with `#or` or `#and` and a mixture of attributes and SQL strings resulting in an incorrect query.
 
     ```ruby
-    class Instructor < ActiveRecord::Base
-      has_many :instructor_roles, -> { active }
-    end
-
-    class InstructorRole < ActiveRecord::Base
-      scope :active, -> {
-        joins("JOIN students ON instructor_roles.student_id = students.id")
-        .where(students { status: 1 })
-      }
-    end
-
-    Instructor.joins(:instructor_roles).first
+    base = Comment.joins(:post).where(user_id: 1).where("recent = 1")
+    puts base.merge(base.where(draft: true).or(Post.where(archived: true))).to_sql
     ```
 
-    The above example would result in `ActiveRecord::StatementInvalid` because the
-    `active` scope bind parameters would be lost.
+    Before:
+
+    ```SQL
+    SELECT "comments".* FROM "comments"
+    INNER JOIN "posts" ON "posts"."id" = "comments"."post_id"
+    WHERE (recent = 1)
+    AND (
+      "comments"."user_id" = 1
+      AND (recent = 1)
+      AND "comments"."draft" = 1
+      OR "posts"."archived" = 1
+    )
+    ```
 
-    *Jean Boussier*
+    After:
+
+    ```SQL
+    SELECT "comments".* FROM "comments"
+    INNER JOIN "posts" ON "posts"."id" = "comments"."post_id"
+    WHERE "comments"."user_id" = 1
+    AND (recent = 1)
+    AND (
+      "comments"."user_id" = 1
+      AND (recent = 1)
+      AND "comments"."draft" = 1
+      OR "posts"."archived" = 1
+    )
+    ```
 
-*   Fix a potential race condition with system tests and transactional fixtures.
+    *Joshua Young*
 
-    *Sjoerd Lagarde*
+*   Make schema dumper to account for `ActiveRecord.dump_schemas` when dumping in `:ruby` format.
 
-*   Fix autosave associations to no longer validated unmodified associated records.
+    *fatkodima*
 
-    Active Record was incorrectly performing validation on associated record that
-    weren't created nor modified as part of the transaction:
+*   Add `:touch` option to `update_column`/`update_columns` methods.
 
     ```ruby
-    Post.create!(author: User.find(1)) # Fail if user is invalid
-    ```
-
-    *Jean Boussier*
-
-*   Remember when a database connection has recently been verified (for
-    two seconds, by default), to avoid repeated reverifications during a
-    single request.
+    # Will update :updated_at/:updated_on alongside :nice column.
+    user.update_column(:nice, true, touch: true)
 
-    This should recreate a similar rate of verification as in Rails 7.1,
-    where connections are leased for the duration of a request, and thus
-    only verified once.
+    # Will update :updated_at/:updated_on alongside :last_ip column
+    user.update_columns(last_ip: request.remote_ip, touch: true)
+    ```
 
-    *Matthew Draper*
+    *Dmitrii Ivliev*
 
+*   Optimize Active Record batching further when using ranges.
 
-## Rails 8.0.1 (December 13, 2024) ##
+    Tested on a PostgreSQL table with 10M records and batches of 10k records, the generation
+    of relations for the 1000 batches was `4.8x` faster (`6.8s` vs. `1.4s`), used `900x`
+    less bandwidth (`180MB` vs. `0.2MB`) and allocated `45x` less memory (`490MB` vs. `11MB`).
 
-*   Fix removing foreign keys with :restrict action for MySQL.
+    *Maxime Réty*, *fatkodima*
 
-    *fatkodima*
+*   Include current character length in error messages for index and table name length validations.
 
-*   Fix a race condition in `ActiveRecord::Base#method_missing` when lazily defining attributes.
+    *Joshua Young*
 
-    If multiple thread were concurrently triggering attribute definition on the same model,
-    it could result in a `NoMethodError` being raised.
+*   Add `rename_schema` method for PostgreSQL.
 
-    *Jean Boussier*
+    *T S Vallender*
 
-*   Fix MySQL default functions getting dropped when changing a column's nullability.
+*   Implement support for deprecating associations:
 
-    *Bastian Bartmann*
+    ```ruby
+    has_many :posts, deprecated: true
+    ```
 
-*   Fix `add_unique_constraint`/`add_check_constraint`/`add_foreign_key` to be revertible when given invalid options.
+    With that, Active Record will report any usage of the `posts` association.
 
-    *fatkodima*
+    Three reporting modes are supported (`:warn`, `:raise`, and `:notify`), and
+    backtraces can be enabled or disabled. Defaults are `:warn` mode and
+    disabled backtraces.
 
-*   Fix asynchronous destroying of polymorphic `belongs_to` associations.
+    Please, check the docs for further details.
 
-    *fatkodima*
+    *Xavier Noria*
 
-*   Fix `insert_all` to not update existing records.
+*   PostgreSQL adapter create DB now supports `locale_provider` and `locale`.
 
-    *fatkodima*
+    *Bengt-Ove Hollaender*
 
-*   `NOT VALID` constraints should not dump in `create_table`.
+*   Use ntuples to populate row_count instead of count for Postgres
 
-    *Ryuta Kamizono*
+    *Jonathan Calvert*
 
-*   Fix finding by nil composite primary key association.
+*   Fix checking whether an unpersisted record is `include?`d in a strictly
+    loaded `has_and_belongs_to_many` association.
 
-    *fatkodima*
+    *Hartley McGuire*
 
-*   Properly reset composite primary key configuration when setting a primary key.
+*   Add ability to change transaction isolation for all pools within a block.
 
-    *fatkodima*
+    This functionality is useful if your application needs to change the database
+    transaction isolation for a request or action.
 
-*   Fix Mysql2Adapter support for prepared statements
+    Calling `ActiveRecord.with_transaction_isolation_level(level) {}` in an around filter or
+    middleware will set the transaction isolation for all pools accessed within the block,
+    but not for the pools that aren't.
 
-    Using prepared statements with MySQL could result in a `NoMethodError` exception.
+    This works with explicit and implicit transactions:
 
-    *Jean Boussier*, *Leo Arnold*, *zzak*
+    ```ruby
+    ActiveRecord.with_transaction_isolation_level(:read_committed) do
+      Tag.transaction do # opens a transaction explicitly
+        Tag.create!
+      end
+    end
+    ```
 
-*   Fix parsing of SQLite foreign key names when they contain non-ASCII characters
+    ```ruby
+    ActiveRecord.with_transaction_isolation_level(:read_committed) do
+      Tag.create! # opens a transaction implicitly
+    end
+    ```
 
-    *Zacharias Knudsen*
+    *Eileen M. Uchitelle*
 
-*   Fix parsing of MySQL 8.0.16+ CHECK constraints when they contain new lines.
+*   Raise `ActiveRecord::MissingRequiredOrderError` when order dependent finder methods (e.g. `#first`, `#last`) are
+    called without `order` values on the relation, and the model does not have any order columns (`implicit_order_column`,
+    `query_constraints`, or `primary_key`) to fall back on.
 
-    *Steve Hill*
+    This change will be introduced with a new framework default for Rails 8.1, and the current behavior of not raising
+    an error has been deprecated with the aim of removing the configuration option in Rails 8.2.
 
-*   Ensure normalized attribute queries use `IS NULL` consistently for `nil` and normalized `nil` values.
+    ```ruby
+    config.active_record.raise_on_missing_required_finder_order_columns = true
+    ```
 
     *Joshua Young*
 
-*   Fix `sum` when performing a grouped calculation.
+*   `:class_name` is now invalid in polymorphic `belongs_to` associations.
 
-    `User.group(:friendly).sum` no longer worked. This is fixed.
+    Reason is `:class_name` does not make sense in those associations because
+    the class name of target records is dynamic and stored in the type column.
 
-    *Edouard Chin*
+    Existing polymorphic associations setting this option can just delete it.
+    While it did not raise, it had no effect anyway.
 
-*   Restore back the ability to pass only database name to `DATABASE_URL`.
+    *Xavier Noria*
 
-    *fatkodima*
+*   Add support for multiple databases to `db:migrate:reset`.
 
+    *Joé Dupuis*
 
-## Rails 8.0.0.1 (December 10, 2024) ##
+*   Add `affected_rows` to `ActiveRecord::Result`.
 
-*   No changes.
+    *Jenny Shen*
 
+*   Enable passing retryable SqlLiterals to `#where`.
 
-## Rails 8.0.0 (November 07, 2024) ##
+    *Hartley McGuire*
 
-*   Fix support for `query_cache: false` in `database.yml`.
+*   Set default for primary keys in `insert_all`/`upsert_all`.
 
-    `query_cache: false` would no longer entirely disable the Active Record query cache.
+    Previously in Postgres, updating and inserting new records in one upsert wasn't possible
+    due to null primary key values. `nil` primary key values passed into `insert_all`/`upsert_all`
+    are now implicitly set to the default insert value specified by adapter.
 
-    *zzak*
+    *Jenny Shen*
 
+*   Add a load hook `active_record_database_configurations` for `ActiveRecord::DatabaseConfigurations`
 
-## Rails 8.0.0.rc2 (October 30, 2024) ##
+    *Mike Dalessio*
 
-*   NULLS NOT DISTINCT works with UNIQUE CONSTRAINT as well as UNIQUE INDEX.
+*   Use `TRUE` and `FALSE` for SQLite queries with boolean columns.
 
-    *Ryuta Kamizono*
+    *Hartley McGuire*
 
-*   The `db:prepare` task no longer loads seeds when a non-primary database is created.
+*   Bump minimum supported SQLite to 3.23.0.
 
-    Previously, the `db:prepare` task would load seeds whenever a new database
-    is created, leading to potential loss of data if a database is added to an
-    existing environment.
+    *Hartley McGuire*
 
-    Introduces a new database config property `seeds` to control whether seeds
-    are loaded during `db:prepare` which defaults to `true` for primary database
-    configs and `false` otherwise.
+*   Allow allocated Active Records to lookup associations.
 
-    Fixes #53348.
+    Previously, the association cache isn't setup on allocated record objects, so association
+    lookups will crash. Test frameworks like mocha use allocate to check for stubbable instance
+    methods, which can trigger an association lookup.
 
-    *Mike Dalessio*
+    *Gannon McGibbon*
 
-*   `PG::UnableToSend: no connection to the server` is now retryable as a connection-related exception
+*   Encryption now supports `support_unencrypted_data: true` being set per-attribute.
 
-    *Kazuma Watanabe*
+    Previously this only worked if `ActiveRecord::Encryption.config.support_unencrypted_data == true`.
+    Now, if the global config is turned off, you can still opt in for a specific attribute.
 
-*   Fix strict loading propagation even if statement cache is not used.
+    ```ruby
+    # ActiveRecord::Encryption.config.support_unencrypted_data = true
+    class User < ActiveRecord::Base
+      encrypts :name, support_unencrypted_data: false # only supports encrypted data
+      encrypts :email # supports encrypted or unencrypted data
+    end
+    ```
 
-    *Ryuta Kamizono*
+    ```ruby
+    # ActiveRecord::Encryption.config.support_unencrypted_data = false
+    class User < ActiveRecord::Base
+      encrypts :name, support_unencrypted_data: true # supports encrypted or unencrypted data
+      encrypts :email  # only supports encrypted data
+    end
+    ```
 
-*   Allow `rename_enum` accepts two from/to name arguments as `rename_table` does so.
+    *Alex Ghiculescu*
 
-    *Ryuta Kamizono*
+*   Model generator no longer needs a database connection to validate column types.
 
+    *Mike Dalessio*
 
-## Rails 8.0.0.rc1 (October 19, 2024) ##
+*   Allow signed ID verifiers to be configurable via `Rails.application.message_verifiers`
 
-*   Remove deprecated support to setting `ENV["SCHEMA_CACHE"]`.
+    Prior to this change, the primary way to configure signed ID verifiers was
+    to set `signed_id_verifier` on each model class:
 
-    *Rafael Mendonça França*
+      ```ruby
+      Post.signed_id_verifier = ActiveSupport::MessageVerifier.new(...)
+      Comment.signed_id_verifier = ActiveSupport::MessageVerifier.new(...)
+      ```
 
-*   Remove deprecated support to passing a database name to `cache_dump_filename`.
+    And if the developer did not set `signed_id_verifier`, a verifier would be
+    instantiated with a secret derived from `secret_key_base` and the following
+    options:
 
-    *Rafael Mendonça França*
+      ```ruby
+      { digest: "SHA256", serializer: JSON, url_safe: true }
+      ```
 
-*   Remove deprecated `ActiveRecord::ConnectionAdapters::ConnectionPool#connection`.
+    Thus it was cumbersome to rotate configuration for all verifiers.
 
-    *Rafael Mendonça França*
+    This change defines a new Rails config: [`config.active_record.use_legacy_signed_id_verifier`][].
+    The default value is `:generate_and_verify`, which preserves the previous
+    behavior. However, when set to `:verify`, signed ID verifiers will use
+    configuration from `Rails.application.message_verifiers` (specifically,
+    `Rails.application.message_verifiers["active_record/signed_id"]`) to
+    generate and verify signed IDs, but will also verify signed IDs using the
+    older configuration.
 
-*   Remove deprecated `config.active_record.sqlite3_deprecated_warning`.
+    To avoid complication, the new behavior only applies when `signed_id_verifier_secret`
+    is not set on a model class or any of its ancestors. Additionally,
+    `signed_id_verifier_secret` is now deprecated. If you are currently setting
+    `signed_id_verifier_secret` on a model class, you can set `signed_id_verifier`
+    instead:
 
-    *Rafael Mendonça França*
+      ```ruby
+      # BEFORE
+      Post.signed_id_verifier_secret = "my secret"
 
-*   Remove deprecated `config.active_record.warn_on_records_fetched_greater_than`.
+      # AFTER
+      Post.signed_id_verifier = ActiveSupport::MessageVerifier.new("my secret", digest: "SHA256", serializer: JSON, url_safe: true)
+      ```
 
-    *Rafael Mendonça França*
+    To ease migration, `signed_id_verifier` has also been changed to behave as a
+    `class_attribute` (i.e. inheritable), but _only when `signed_id_verifier_secret`
+    is not set_:
 
-*   Remove deprecated support for defining `enum` with keyword arguments.
+      ```ruby
+      # BEFORE
+      ActiveRecord::Base.signed_id_verifier = ActiveSupport::MessageVerifier.new(...)
+      Post.signed_id_verifier == ActiveRecord::Base.signed_id_verifier # => false
 
-    *Rafael Mendonça França*
+      # AFTER
+      ActiveRecord::Base.signed_id_verifier = ActiveSupport::MessageVerifier.new(...)
+      Post.signed_id_verifier == ActiveRecord::Base.signed_id_verifier # => true
 
-*   Remove deprecated support to finding database adapters that aren't registered to Active Record.
+      Post.signed_id_verifier_secret = "my secret" # => deprecation warning
+      Post.signed_id_verifier == ActiveRecord::Base.signed_id_verifier # => false
+      ```
 
-    *Rafael Mendonça França*
+    Note, however, that it is recommended to eventually migrate from
+    model-specific verifiers to a unified configuration managed by
+    `Rails.application.message_verifiers`. `ActiveSupport::MessageVerifier#rotate`
+    can facilitate that transition. For example:
 
-*   Remove deprecated `config.active_record.allow_deprecated_singular_associations_name`.
+      ```ruby
+      # BEFORE
+      # Generate and verify signed Post IDs using Post-specific configuration
+      Post.signed_id_verifier = ActiveSupport::MessageVerifier.new("post secret", ...)
 
-    *Rafael Mendonça França*
+      # AFTER
+      # Generate and verify signed Post IDs using the unified configuration
+      Post.signed_id_verifier = Post.signed_id_verifier.dup
+      # Fall back to Post-specific configuration when verifying signed IDs
+      Post.signed_id_verifier.rotate("post secret", ...)
+      ```
 
-*   Remove deprecated `config.active_record.commit_transaction_on_non_local_return`.
+    [`config.active_record.use_legacy_signed_id_verifier`]: https://guides.rubyonrails.org/v8.1/configuring.html#config-active-record-use-legacy-signed-id-verifier
 
-    *Rafael Mendonça França*
+    *Ali Sepehri*, *Jonathan Hefner*
 
-*   Fix incorrect SQL query when passing an empty hash to `ActiveRecord::Base.insert`.
+*   Prepend `extra_flags` in postgres' `structure_load`
 
-    *David Stosik*
+    When specifying `structure_load_flags` with a postgres adapter, the flags
+    were appended to the default flags, instead of prepended.
+    This caused issues with flags not being taken into account by postgres.
 
-*   Allow to save records with polymorphic join tables that have `inverse_of`
-    specified.
+    *Alice Loeser*
 
-    *Markus Doits*
+*   Allow bypassing primary key/constraint addition in `implicit_order_column`
 
-*   Fix association scopes applying on the incorrect join when using a polymorphic `has_many through:`.
+    When specifying multiple columns in an array for `implicit_order_column`, adding
+    `nil` as the last element will prevent appending the primary key to order
+    conditions. This allows more precise control of indexes used by
+    generated queries. It should be noted that this feature does introduce the risk
+    of API misbehavior if the specified columns are not fully unique.
 
-    *Joshua Young*
+    *Issy Long*
 
-*   Allow `ActiveRecord::Base#pluck` to accept hash arguments with symbol and string values.
+*   Allow setting the `schema_format` via database configuration.
 
-    ```ruby
-    Post.joins(:comments).pluck(:id, comments: :id)
-    Post.joins(:comments).pluck("id", "comments" => "id")
+    ```
+    primary:
+      schema_format: ruby
     ```
 
-    *Joshua Young*
-
-*   Make Float distinguish between `float4` and `float8` in PostgreSQL.
-
-    Fixes #52742
+    Useful for multi-database setups when apps require different formats per-database.
 
-    *Ryota Kitazawa*, *Takayuki Nagatomi*
+    *T S Vallender*
 
+*   Support disabling indexes for MySQL v8.0.0+ and MariaDB v10.6.0+
 
-## Rails 8.0.0.beta1 (September 26, 2024) ##
+    MySQL 8.0.0 added an option to disable indexes from being used by the query
+    optimizer by making them "invisible". This allows the index to still be maintained
+    and updated but no queries will be permitted to use it. This can be useful for adding
+    new invisible indexes or making existing indexes invisible before dropping them
+    to ensure queries are not negatively affected.
+    See https://dev.mysql.com/blog-archive/mysql-8-0-invisible-indexes/ for more details.
 
-*   Allow `drop_table` to accept an array of table names.
+    MariaDB 10.6.0 also added support for this feature by allowing indexes to be "ignored"
+    in queries. See https://mariadb.com/kb/en/ignored-indexes/ for more details.
 
-    This will let you to drop multiple tables in a single call.
+    Active Record now supports this option for MySQL 8.0.0+ and MariaDB 10.6.0+ for
+    index creation and alteration where the new index option `enabled: true/false` can be
+    passed to column and index methods as below:
 
     ```ruby
-    ActiveRecord::Base.lease_connection.drop_table(:users, :posts)
+    add_index :users, :email, enabled: false
+    enable_index :users, :email
+    add_column :users, :dob, :string, index: { enabled: false }
+
+    change_table :users do |t|
+      t.index :name, enabled: false
+      t.index :dob
+      t.disable_index :dob
+      t.column :username, :string, index: { enabled: false }
+      t.references :account, index: { enabled: false }
+    end
+
+    create_table :users do |t|
+      t.string :name, index: { enabled: false }
+      t.string :email
+      t.index :email, enabled: false
+    end
     ```
 
-    *Gabriel Sobrinho*
+    *Merve Taner*
 
-*   Add support for PostgreSQL `IF NOT EXISTS` via the `:if_not_exists` option
-    on the `add_enum_value` method.
+*   Respect `implicit_order_column` in `ActiveRecord::Relation#reverse_order`.
 
-    *Ariel Rzezak*
+    *Joshua Young*
 
-*   When running `db:migrate` on a fresh database, load the databases schemas before running migrations.
+*   Add column types to `ActiveRecord::Result` for SQLite3.
 
-    *Andrew Novoselac*, *Marek Kasztelnik*
+    *Andrew Kane*
 
-*   Fix an issue where `.left_outer_joins` used with multiple associations that have
-    the same child association but different parents does not join all parents.
+*   Raise `ActiveRecord::ReadOnlyError` when pessimistically locking with a readonly role.
 
-    Previously, using `.left_outer_joins` with the same child association would only join one of the parents.
+    *Joshua Young*
 
-    Now it will correctly join both parents.
+*   Fix using the `SQLite3Adapter`'s `dbconsole` method outside of a Rails application.
 
-    Fixes #41498.
+    *Hartley McGuire*
 
-    *Garrett Blehm*
+*   Fix migrating multiple databases with `ActiveRecord::PendingMigration` action.
 
-*   Deprecate `unsigned_float` and `unsigned_decimal` short-hand column methods.
+    *Gannon McGibbon*
 
-    As of MySQL 8.0.17, the UNSIGNED attribute is deprecated for columns of type FLOAT, DOUBLE,
-    and DECIMAL. Consider using a simple CHECK constraint instead for such columns.
+*   Enable automatically retrying idempotent association queries on connection
+    errors.
 
-    https://dev.mysql.com/doc/refman/8.0/en/numeric-type-syntax.html
+    *Hartley McGuire*
 
-    *Ryuta Kamizono*
+*   Add `allow_retry` to `sql.active_record` instrumentation.
 
-*   Drop MySQL 5.5 support.
+    This enables identifying queries which queries are automatically retryable on connection errors.
 
-    MySQL 5.5 is the only version that does not support datetime with precision,
-    which we have supported in the core. Now we support MySQL 5.6.4 or later, which
-    is the first version to support datetime with precision.
+    *Hartley McGuire*
 
-    *Ryuta Kamizono*
+*   Better support UPDATE with JOIN for Postgresql and SQLite3
 
-*   Make Active Record asynchronous queries compatible with transactional fixtures.
+    Previously when generating update queries with one or more JOIN clauses,
+    Active Record would use a sub query which would prevent to reference the joined
+    tables in the `SET` clause, for instance:
 
-    Previously transactional fixtures would disable asynchronous queries, because transactional
-    fixtures impose all queries use the same connection.
+    ```ruby
+    Comment.joins(:post).update_all("title = posts.title")
+    ```
 
-    Now asynchronous queries will use the connection pinned by transactional fixtures, and behave
-    much closer to production.
+    This is now supported as long as the relation doesn't also use a `LIMIT`, `ORDER` or
+    `GROUP BY` clause. This was supported by the MySQL adapter for a long time.
 
     *Jean Boussier*
 
-*   Deserialize binary data before decrypting
-
-    This ensures that we call `PG::Connection.unescape_bytea` on PostgreSQL before decryption.
-
-    *Donal McBreen*
-
-*   Ensure `ActiveRecord::Encryption.config` is always ready before access.
-
-    Previously, `ActiveRecord::Encryption` configuration was deferred until `ActiveRecord::Base`
-    was loaded. Therefore, accessing `ActiveRecord::Encryption.config` properties before
-    `ActiveRecord::Base` was loaded would give incorrect results.
-
-    `ActiveRecord::Encryption` now has its own loading hook so that its configuration is set as
-    soon as needed.
-
-    When `ActiveRecord::Base` is loaded, even lazily, it in turn triggers the loading of
-    `ActiveRecord::Encryption`, thus preserving the original behavior of having its config ready
-    before any use of `ActiveRecord::Base`.
-
-    *Maxime Réty*
-
-*   Add `TimeZoneConverter#==` method, so objects will be properly compared by
-    their type, scale, limit & precision.
+*   Introduce a before-fork hook in `ActiveSupport::Testing::Parallelization` to clear existing
+    connections, to avoid fork-safety issues with the mysql2 adapter.
 
-    Address #52699.
+    Fixes #41776
 
-    *Ruy Rocha*
+    *Mike Dalessio*, *Donal McBreen*
 
-*   Add support for SQLite3 full-text-search and other virtual tables.
-
-    Previously, adding sqlite3 virtual tables messed up `schema.rb`.
+*   PoolConfig no longer keeps a reference to the connection class.
 
-    Now, virtual tables can safely be added using `create_virtual_table`.
+    Keeping a reference to the class caused subtle issues when combined with reloading in
+    development. Fixes #54343.
 
-    *Zacharias Knudsen*
+    *Mike Dalessio*
 
-*   Support use of alternative database interfaces via the `database_cli` ActiveRecord configuration option.
+*   Fix SQL notifications sometimes not sent when using async queries.
 
     ```ruby
-    Rails.application.configure do
-      config.active_record.database_cli = { postgresql: "pgcli" }
+    Post.async_count
+    ActiveSupport::Notifications.subscribed(->(*) { "Will never reach here" }) do
+      Post.count
     end
     ```
 
-    *T S Vallender*
+    In rare circumstances and under the right race condition, Active Support notifications
+    would no longer be dispatched after using an asynchronous query.
+    This is now fixed.
 
-*   Add support for dumping table inheritance and native partitioning table definitions for PostgeSQL adapter
+    *Edouard Chin*
 
-    *Justin Talbott*
+*   Eliminate queries loading dumped schema cache on Postgres
 
-*   Add support for `ActiveRecord::Point` type casts using `Hash` values
+    Improve resiliency by avoiding needing to open a database connection to load the
+    type map while defining attribute methods at boot when a schema cache file is
+    configured on PostgreSQL databases.
 
-    This allows `ActiveRecord::Point` to be cast or serialized from a hash
-    with `:x` and `:y` keys of numeric values, mirroring the functionality of
-    existing casts for string and array values. Both string and symbol keys are
-    supported.
+    *James Coleman*
 
-    ```ruby
-    class PostgresqlPoint < ActiveRecord::Base
-      attribute :x, :point
-      attribute :y, :point
-      attribute :z, :point
-    end
+*   `ActiveRecord::Coder::JSON` can be instantiated
 
-    val = PostgresqlPoint.new({
-      x: '(12.34, -43.21)',
-      y: [12.34, '-43.21'],
-      z: {x: '12.34', y: -43.21}
-    })
-    ActiveRecord::Point.new(12.32, -43.21) == val.x == val.y == val.z
+    Options can now be passed to `ActiveRecord::Coder::JSON` when instantiating the coder. This allows:
+    ```ruby
+    serialize :config, coder: ActiveRecord::Coder::JSON.new(symbolize_names: true)
     ```
+    *matthaigh27*
 
-    *Stephen Drew*
+*   Deprecate using `insert_all`/`upsert_all` with unpersisted records in associations.
 
-*   Replace `SQLite3::Database#busy_timeout` with `#busy_handler_timeout=`.
+    Using these methods on associations containing unpersisted records will now
+    show a deprecation warning, as the unpersisted records will be lost after
+    the operation.
 
-    Provides a non-GVL-blocking, fair retry interval busy handler implementation.
+    *Nick Schwaderer*
 
-    *Stephen Margheim*
+*   Make column name optional for `index_exists?`.
 
-*   SQLite3Adapter: Translate `SQLite3::BusyException` into `ActiveRecord::StatementTimeout`.
+    This aligns well with `remove_index` signature as well, where
+    index name doesn't need to be derived from the column names.
 
-    *Matthew Nguyen*
+    *Ali Ismayiliov*
 
-*   Include schema name in `enable_extension` statements in `db/schema.rb`.
+*   Change the payload name of `sql.active_record` notification for eager
+    loading from "SQL" to "#{model.name} Eager Load".
 
-    The schema dumper will now include the schema name in generated
-    `enable_extension` statements if they differ from the current schema.
+    *zzak*
 
-    For example, if you have a migration:
+*   Enable automatically retrying idempotent `#exists?` queries on connection
+    errors.
 
-    ```ruby
-    enable_extension "heroku_ext.pgcrypto"
-    enable_extension "pg_stat_statements"
-    ```
+    *Hartley McGuire*, *classidied*
 
-    then the generated schema dump will also contain:
+*   Deprecate usage of unsupported methods in conjunction with `update_all`:
 
-    ```ruby
-    enable_extension "heroku_ext.pgcrypto"
-    enable_extension "pg_stat_statements"
-    ```
+    `update_all` will now print a deprecation message if a query includes either `WITH`,
+    `WITH RECURSIVE` or `DISTINCT` statements. Those were never supported and were ignored
+    when generating the SQL query.
 
-    *Tony Novak*
+    An error will be raised in a future Rails release. This behavior will be consistent
+    with `delete_all` which currently raises an error for unsupported statements.
 
-*   Fix `ActiveRecord::Encryption::EncryptedAttributeType#type` to return
-    actual cast type.
+    *Edouard Chin*
 
-    *Vasiliy Ermolovich*
+*   The table columns inside `schema.rb` are now sorted alphabetically.
 
-*   SQLite3Adapter: Bulk insert fixtures.
+    Previously they'd be sorted by creation order, which can cause merge conflicts when two
+    branches modify the same table concurrently.
 
-    Previously one insert command was executed for each fixture, now they are
-    aggregated in a single bulk insert command.
+    *John Duff*
 
-    *Lázaro Nixon*
+*   Introduce versions formatter for the schema dumper.
 
-*   PostgreSQLAdapter: Allow `disable_extension` to be called with schema-qualified name.
+    It is now possible to override how schema dumper formats versions information inside the
+    `structure.sql` file. Currently, the versions are simply sorted in the decreasing order.
+    Within large teams, this can potentially cause many merge conflicts near the top of the list.
 
-    For parity with `enable_extension`, the `disable_extension` method can be called with a schema-qualified
-    name (e.g. `disable_extension "myschema.pgcrypto"`). Note that PostgreSQL's `DROP EXTENSION` does not
-    actually take a schema name (unlike `CREATE EXTENSION`), so the resulting SQL statement will only name
-    the extension, e.g. `DROP EXTENSION IF EXISTS "pgcrypto"`.
+    Now, the custom formatter can be provided with a custom sorting logic (e.g. by hash values
+    of the versions), which can greatly reduce the number of conflicts.
 
-    *Tony Novak*
+    *fatkodima*
 
-*   Make `create_schema` / `drop_schema` reversible in migrations.
+*   Serialized attributes can now be marked as comparable.
 
-    Previously, `create_schema` and `drop_schema` were irreversible migration operations.
+    A not rare issue when working with serialized attributes is that the serialized representation of an object
+    can change over time. Either because you are migrating from one serializer to the other (e.g. YAML to JSON or to msgpack),
+    or because the serializer used subtly changed its output.
 
-    *Tony Novak*
+    One example is libyaml that used to have some extra trailing whitespaces, and recently fixed that.
+    When this sorts of thing happen, you end up with lots of records that report being changed even though
+    they aren't, which in the best case leads to a lot more writes to the database and in the worst case lead to nasty bugs.
 
-*   Support batching using custom columns.
+    The solution is to instead compare the deserialized representation of the object, however Active Record
+    can't assume the deserialized object has a working `==` method. Hence why this new functionality is opt-in.
 
     ```ruby
-    Product.in_batches(cursor: [:shop_id, :id]) do |relation|
-      # do something with relation
-    end
+    serialize :config, type: Hash, coder: JSON, comparable: true
     ```
 
-    *fatkodima*
-
-*   Use SQLite `IMMEDIATE` transactions when possible.
-
-    Transactions run against the SQLite3 adapter default to IMMEDIATE mode to improve concurrency support and avoid busy exceptions.
-
-    *Stephen Margheim*
-
-*   Raise specific exception when a connection is not defined.
-
-    The new `ConnectionNotDefined` exception provides connection name, shard and role accessors indicating the details of the connection that was requested.
-
-    *Hana Harencarova*, *Matthew Draper*
+    *Jean Boussier*
 
-*   Delete the deprecated constant `ActiveRecord::ImmutableRelation`.
+*   Fix MySQL default functions getting dropped when changing a column's nullability.
 
-    *Xavier Noria*
+    *Bastian Bartmann*
 
-*   Fix duplicate callback execution when child autosaves parent with `has_one` and `belongs_to`.
+*   SQLite extensions can be configured in `config/database.yml`.
 
-    Before, persisting a new child record with a new associated parent record would run `before_validation`,
-    `after_validation`, `before_save` and `after_save` callbacks twice.
+    The database configuration option `extensions:` allows an application to load SQLite extensions
+    when using `sqlite3` >= v2.4.0. The array members may be filesystem paths or the names of
+    modules that respond to `.to_path`:
 
-    Now, these callbacks are only executed once as expected.
+    ``` yaml
+    development:
+      adapter: sqlite3
+      extensions:
+        - SQLean::UUID                     # module name responding to `.to_path`
+        - .sqlpkg/nalgeon/crypto/crypto.so # or a filesystem path
+        - <%= AppExtensions.location %>    # or ruby code returning a path
+    ```
 
-    *Joshua Young*
+    *Mike Dalessio*
 
-*   `ActiveRecord::Encryption::Encryptor` now supports a `:compressor` option to customize the compression algorithm used.
+*   `ActiveRecord::Middleware::ShardSelector` supports granular database connection switching.
 
-    ```ruby
-    module ZstdCompressor
-      def self.deflate(data)
-        Zstd.compress(data)
-      end
+    A new configuration option, `class_name:`, is introduced to
+    `config.active_record.shard_selector` to allow an application to specify the abstract connection
+    class to be switched by the shard selection middleware. The default class is
+    `ActiveRecord::Base`.
 
-      def self.inflate(data)
-        Zstd.decompress(data)
-      end
-    end
+    For example, this configuration tells `ShardSelector` to switch shards using
+    `AnimalsRecord.connected_to`:
 
-    class User
-      encrypts :name, compressor: ZstdCompressor
-    end
     ```
-
-    You disable compression by passing `compress: false`.
-
-    ```ruby
-    class User
-      encrypts :name, compress: false
-    end
+    config.active_record.shard_selector = { class_name: "AnimalsRecord" }
     ```
 
-    *heka1024*
-
-*   Add condensed `#inspect` for `ConnectionPool`, `AbstractAdapter`, and
-    `DatabaseConfig`.
-
-    *Hartley McGuire*
-
-*   Add `.shard_keys`, `.sharded?`, & `.connected_to_all_shards` methods.
-
-    ```ruby
-    class ShardedBase < ActiveRecord::Base
-        self.abstract_class = true
-
-        connects_to shards: {
-          shard_one: { writing: :shard_one },
-          shard_two: { writing: :shard_two }
-        }
-    end
-
-    class ShardedModel < ShardedBase
-    end
+    *Mike Dalessio*
 
-    ShardedModel.shard_keys => [:shard_one, :shard_two]
-    ShardedModel.sharded? => true
-    ShardedBase.connected_to_all_shards { ShardedModel.current_shard } => [:shard_one, :shard_two]
-    ```
+*   Reset relations after `insert_all`/`upsert_all`.
 
-    *Nony Dutton*
+    Bulk insert/upsert methods will now call `reset` if used on a relation, matching the behavior of `update_all`.
 
-*   Add a `filter` option to `in_order_of` to prioritize certain values in the sorting without filtering the results
-    by these values.
+    *Milo Winningham*
 
-    *Igor Depolli*
+*   Use `_N` as a parallel tests databases suffixes
 
-*   Fix an issue where the IDs reader method did not return expected results
-    for preloaded associations in models using composite primary keys.
+    Peviously, `-N` was used as a suffix. This can cause problems for RDBMSes
+    which do not support dashes in database names.
 
-    *Jay Ang*
+    *fatkodima*
 
-*   Allow to configure `strict_loading_mode` globally or within a model.
+*   Remember when a database connection has recently been verified (for
+    two seconds, by default), to avoid repeated reverifications during a
+    single request.
 
-    Defaults to `:all`, can be changed to `:n_plus_one_only`.
+    This should recreate a similar rate of verification as in Rails 7.1,
+    where connections are leased for the duration of a request, and thus
+    only verified once.
 
-    *Garen Torikian*
+    *Matthew Draper*
 
-*   Add `ActiveRecord::Relation#readonly?`.
+*   Allow to reset cache counters for multiple records.
 
-    Reflects if the relation has been marked as readonly.
+    ```
+    Aircraft.reset_counters([1, 2, 3], :wheels_count)
+    ```
 
-    *Theodor Tonum*
+    It produces much fewer queries compared to the custom implementation using looping over ids.
+    Previously: `O(ids.size * counters.size)` queries, now: `O(ids.size + counters.size)` queries.
 
-*   Improve `ActiveRecord::Store` to raise a descriptive exception if the column is not either
-    structured (e.g., PostgreSQL +hstore+/+json+, or MySQL +json+) or declared serializable via
-    `ActiveRecord.store`.
+    *fatkodima*
 
-    Previously, a `NoMethodError` would be raised when the accessor was read or written:
+*   Add `affected_rows` to `sql.active_record` Notification.
 
-        NoMethodError: undefined method `accessor' for an instance of ActiveRecord::Type::Text
+    *Hartley McGuire*
 
-    Now, a descriptive `ConfigurationError` is raised:
+*   Fix `sum` when performing a grouped calculation.
 
-        ActiveRecord::ConfigurationError: the column 'metadata' has not been configured as a store.
-          Please make sure the column is declared serializable via 'ActiveRecord.store' or, if your
-          database supports it, use a structured column type like hstore or json.
+    `User.group(:friendly).sum` no longer worked. This is fixed.
 
-    *Mike Dalessio*
+    *Edouard Chin*
 
-*   Fix inference of association model on nested models with the same demodularized name.
+*   Add support for enabling or disabling transactional tests per database.
 
-    E.g. with the following setup:
+    A test class can now override the default `use_transactional_tests` setting
+    for individual databases, which can be useful if some databases need their
+    current state to be accessible to an external process while tests are running.
 
     ```ruby
-    class Nested::Post < ApplicationRecord
-      has_one :post, through: :other
+    class MostlyTransactionalTest < ActiveSupport::TestCase
+      self.use_transactional_tests = true
+      skip_transactional_tests_for_database :shared
     end
     ```
 
-    Before, `#post` would infer the model as `Nested::Post`, but now it correctly infers `Post`.
+    *Matthew Cheetham*, *Morgan Mareve*
 
-    *Joshua Young*
+*   Cast `query_cache` value when using URL configuration.
+
+    *zzak*
 
-*   Add public method for checking if a table is ignored by the schema cache.
+*   NULLS NOT DISTINCT works with UNIQUE CONSTRAINT as well as UNIQUE INDEX.
 
-    Previously, an application would need to reimplement `ignored_table?` from the schema cache class to check if a table was set to be ignored. This adds a public method to support this and updates the schema cache to use that directly.
+    *Ryuta Kamizono*
 
-    ```ruby
-    ActiveRecord.schema_cache_ignored_tables = ["developers"]
-    ActiveRecord.schema_cache_ignored_table?("developers")
-    => true
-    ```
+*   `PG::UnableToSend: no connection to the server` is now retryable as a connection-related exception
 
-    *Eileen M. Uchitelle*
+    *Kazuma Watanabe*
 
-Please check [7-2-stable](https://github.com/rails/rails/blob/7-2-stable/activerecord/CHANGELOG.md) for previous changes.
+Please check [8-0-stable](https://github.com/rails/rails/blob/8-0-stable/activerecord/CHANGELOG.md) for previous changes.