activerecord 6.1.7 → 7.1.0

data/CHANGELOG.md

@@ -1,1767 +1,2264 @@
-## Rails 6.1.7 (September 09, 2022) ##
+## Rails 7.1.0 (October 05, 2023) ##
 
-*   Symbol is allowed by default for YAML columns
+*   No changes.
 
-    *Étienne Barrié*
 
-*   Fix `ActiveRecord::Store` to serialize as a regular Hash
+## Rails 7.1.0.rc2 (October 01, 2023) ##
 
-    Previously it would serialize as an `ActiveSupport::HashWithIndifferentAccess`
-    which is wasteful and cause problem with YAML safe_load.
+*   Remove -shm and -wal SQLite files when `rails db:drop` is run.
 
-    *Jean Boussier*
+    *Niklas Häusele*
 
-*   Fix PG.connect keyword arguments deprecation warning on ruby 2.7
+*   Revert the change to raise an `ArgumentError` when `#accepts_nested_attributes_for` is declared more than once for
+    an association in the same class.
 
-    Fixes #44307.
+    The reverted behavior broke the case where the `#accepts_nested_attributes_for` was defined in a concern and
+    where overridden in the class that included the concern.
 
-    *Nikita Vasilevsky*
+    *Rafael Mendonça França*
+
+
+## Rails 7.1.0.rc1 (September 27, 2023) ##
 
-## Rails 6.1.6.1 (July 12, 2022) ##
+*   Better naming for unique constraints support.
 
-*   Change ActiveRecord::Coders::YAMLColumn default to safe_load
+    Naming unique keys leads to misunderstanding it's a short-hand of unique indexes.
+    Just naming it unique constraints is not misleading.
 
-    This adds two new configuration options The configuration options are as
-    follows:
-    
-    * `config.active_storage.use_yaml_unsafe_load`
-    
-    When set to true, this configuration option tells Rails to use the old
-    "unsafe" YAML loading strategy, maintaining the existing behavior but leaving
-    the possible escalation vulnerability in place.  Setting this option to true
-    is *not* recommended, but can aid in upgrading.
-    
-    * `config.active_record.yaml_column_permitted_classes`
-    
-    The "safe YAML" loading method does not allow all classes to be deserialized
-    by default.  This option allows you to specify classes deemed "safe" in your
-    application.  For example, if your application uses Symbol and Time in
-    serialized data, you can add Symbol and Time to the allowed list as follows:
-    
+    In Rails 7.1.0.beta1 or before:
+
+    ```ruby
+    add_unique_key :sections, [:position], deferrable: :deferred, name: "unique_section_position"
+    remove_unique_key :sections, name: "unique_section_position"
     ```
-    config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]
+
+    Now:
+
+    ```ruby
+    add_unique_constraint :sections, [:position], deferrable: :deferred, name: "unique_section_position"
+    remove_unique_constraint :sections, name: "unique_section_position"
     ```
 
-    [CVE-2022-32224]
+    *Ryuta Kamizono*
 
+*   Fix duplicate quoting for check constraint expressions in schema dump when using MySQL
 
-## Rails 6.1.6 (May 09, 2022) ##
+    A check constraint with an expression, that already contains quotes, lead to an invalid schema
+    dump with the mysql2 adapter.
 
-*   No changes.
+    Fixes #42424.
 
+    *Felix Tscheulin*
 
-## Rails 6.1.5.1 (April 26, 2022) ##
+*   Performance tune the SQLite3 adapter connection configuration
 
-*   No changes.
+    For Rails applications, the Write-Ahead-Log in normal syncing mode with a capped journal size, a healthy shared memory buffer and a shared cache will perform, on average, 2× better.
 
+    *Stephen Margheim*
 
-## Rails 6.1.5 (March 09, 2022) ##
+*   Allow SQLite3 `busy_handler` to be configured with simple max number of `retries`
 
-*   Fix `ActiveRecord::ConnectionAdapters::SchemaCache#deep_deduplicate` for Ruby 2.6.
+    Retrying busy connections without delay is a preferred practice for performance-sensitive applications. Add support for a `database.yml` `retries` integer, which is used in a simple `busy_handler` function to retry busy connections without exponential backoff up to the max number of `retries`.
 
-    Ruby 2.6 and 2.7 have slightly different implementations of the `String#-@` method.
-    In Ruby 2.6, the receiver of the `String#-@` method is modified under certain circumstances.
-    This was later identified as a bug (https://bugs.ruby-lang.org/issues/15926) and only
-    fixed in Ruby 2.7.
+    *Stephen Margheim*
 
-    Before the changes in this commit, the
-    `ActiveRecord::ConnectionAdapters::SchemaCache#deep_deduplicate` method, which internally
-    calls the `String#-@` method, could also modify an input string argument in Ruby 2.6 --
-    changing a tainted, unfrozen string into a tainted, frozen string.
+*   The SQLite3 adapter now supports `supports_insert_returning?`
 
-    Fixes #43056
+    Implementing the full `supports_insert_returning?` contract means the SQLite3 adapter supports auto-populated columns (#48241) as well as custom primary keys.
 
-    *Eric O'Hanlon*
+    *Stephen Margheim*
 
-*   Fix migration compatibility to create SQLite references/belongs_to column as integer when
-    migration version is 6.0.
+*   Ensure the SQLite3 adapter handles default functions with the `||` concatenation operator
 
-    `reference`/`belongs_to` in migrations with version 6.0 were creating columns as
-    bigint instead of integer for the SQLite Adapter.
+    Previously, this default function would produce the static string `"'Ruby ' || 'on ' || 'Rails'"`.
+    Now, the adapter will appropriately receive and use `"Ruby on Rails"`.
 
-    *Marcelo Lauxen*
+    ```ruby
+    change_column_default "test_models", "ruby_on_rails", -> { "('Ruby ' || 'on ' || 'Rails')" }
+    ```
 
-*   Fix dbconsole for 3-tier config.
+    *Stephen Margheim*
 
-    *Eileen M. Uchitelle*
+*   Dump PostgreSQL schemas as part of the schema dump.
+
+    *Lachlan Sylvester*
+
+
+## Rails 7.1.0.beta1 (September 13, 2023) ##
 
-*   Better handle SQL queries with invalid encoding.
+*   Encryption now supports `support_unencrypted_data` being set per-attribute.
+
+    You can now opt out of `support_unencrypted_data` on a specific encrypted attribute.
+    This only has an effect if `ActiveRecord::Encryption.config.support_unencrypted_data == true`.
 
     ```ruby
-    Post.create(name: "broken \xC8 UTF-8")
+    class User < ActiveRecord::Base
+      encrypts :name, deterministic: true, support_unencrypted_data: false
+      encrypts :email, deterministic: true
+    end
     ```
 
-    Would cause all adapters to fail in a non controlled way in the code
-    responsible to detect write queries.
+    *Alex Ghiculescu*
 
-    The query is now properly passed to the database connection, which might or might
-    not be able to handle it, but will either succeed or failed in a more correct way.
+*   Add instrumentation for Active Record transactions
 
-    *Jean Boussier*
+    Allows subscribing to transaction events for tracking/instrumentation. The event payload contains the connection and the outcome (commit, rollback, restart, incomplete), as well as timing details.
 
-*   Ignore persisted in-memory records when merging target lists.
+    ```ruby
+    ActiveSupport::Notifications.subscribe("transaction.active_record") do |event|
+      puts "Transaction event occurred!"
+      connection = event.payload[:connection]
+      puts "Connection: #{connection.inspect}"
+    end
+    ```
 
-    *Kevin Sjöberg*
+    *Daniel Colson*, *Ian Candy*
 
-*   Fix regression bug that caused ignoring additional conditions for preloading
-    `has_many` through relations.
+*   Support composite foreign keys via migration helpers.
 
-    Fixes #43132
+    ```ruby
+    # Assuming "carts" table has "(shop_id, user_id)" as a primary key.
 
-    *Alexander Pauly*
+    add_foreign_key(:orders, :carts, primary_key: [:shop_id, :user_id])
 
-*   Fix `ActiveRecord::InternalMetadata` to not be broken by
-    `config.active_record.record_timestamps = false`
+    remove_foreign_key(:orders, :carts, primary_key: [:shop_id, :user_id])
+    foreign_key_exists?(:orders, :carts, primary_key: [:shop_id, :user_id])
+    ```
 
-    Since the model always create the timestamp columns, it has to set them, otherwise it breaks
-    various DB management tasks.
+    *fatkodima*
 
-    Fixes #42983
+*   Adds support for `if_not_exists` when adding a check constraint.
 
-    *Jean Boussier*
+    ```ruby
+    add_check_constraint :posts, "post_type IN ('blog', 'comment', 'share')", if_not_exists: true
+    ```
 
-*   Fix duplicate active record objects on `inverse_of`.
+    *Cody Cutrer*
 
-    *Justin Carvalho*
+*   Raise an `ArgumentError` when `#accepts_nested_attributes_for` is declared more than once for an association in
+    the same class. Previously, the last declaration would silently override the previous one. Overriding in a subclass
+    is still allowed.
 
-*   Fix duplicate objects stored in has many association after save.
+    *Joshua Young*
 
-    Fixes #42549.
+*   Deprecate `rewhere` argument on `#merge`.
 
-    *Alex Ghiculescu*
+    The `rewhere` argument on `#merge`is deprecated without replacement and
+    will be removed in Rails 7.2.
 
-*   Fix performance regression in `CollectionAssocation#build`.
+    *Adam Hess*
 
-    *Alex Ghiculescu*
+*   Fix unscope is not working in specific case
 
-*   Fix retrieving default value for text column for MariaDB.
+    Before:
+    ```ruby
+    Post.where(id: 1...3).unscope(where: :id).to_sql # "SELECT `posts`.* FROM `posts` WHERE `posts`.`id` >= 1 AND `posts`.`id` < 3"
 
-    *fatkodima*
+    ```
 
+    After:
+    ```ruby
+    Post.where(id: 1...3).unscope(where: :id).to_sql # "SELECT `posts`.* FROM `posts`"
+    ```
 
-## Rails 6.1.4.7 (March 08, 2022) ##
+    Fixes #48094.
 
-*   No changes.
+    *Kazuya Hatanaka*
 
+*   Change `has_secure_token` default to `on: :initialize`
 
-## Rails 6.1.4.6 (February 11, 2022) ##
+    Change the new default value from `on: :create` to `on: :initialize`
 
-*   No changes.
+    Can be controlled by the `config.active_record.generate_secure_token_on`
+    configuration:
 
+    ```ruby
+    config.active_record.generate_secure_token_on = :create
+    ```
 
-## Rails 6.1.4.5 (February 11, 2022) ##
+    *Sean Doyle*
 
-*   No changes.
+*   Fix `change_column` not setting `precision: 6` on `datetime` columns when
+    using 7.0+ Migrations and SQLite.
 
+    *Hartley McGuire*
 
-## Rails 6.1.4.4 (December 15, 2021) ##
+*   Support composite identifiers in `to_key`
 
-*   No changes.
+    `to_key` avoids wrapping `#id` value into an `Array` if `#id` already an array
 
+    *Nikita Vasilevsky*
 
-## Rails 6.1.4.3 (December 14, 2021) ##
+*   Add validation option for `enum`
 
-*   No changes.
+    ```ruby
+    class Contract < ApplicationRecord
+      enum :status, %w[in_progress completed], validate: true
+    end
+    Contract.new(status: "unknown").valid? # => false
+    Contract.new(status: nil).valid? # => false
+    Contract.new(status: "completed").valid? # => true
 
+    class Contract < ApplicationRecord
+      enum :status, %w[in_progress completed], validate: { allow_nil: true }
+    end
+    Contract.new(status: "unknown").valid? # => false
+    Contract.new(status: nil).valid? # => true
+    Contract.new(status: "completed").valid? # => true
+    ```
 
-## Rails 6.1.4.2 (December 14, 2021) ##
+    *Edem Topuzov*, *Ryuta Kamizono*
 
-*   No changes.
+*   Allow batching methods to use already loaded relation if available
 
+    Calling batch methods on already loaded relations will use the records previously loaded instead of retrieving
+    them from the database again.
 
-## Rails 6.1.4.1 (August 19, 2021) ##
+    *Adam Hess*
 
-*   No changes.
+*   Deprecate `read_attribute(:id)` returning the primary key if the primary key is not `:id`.
 
+    Starting in Rails 7.2, `read_attribute(:id)` will return the value of the id column, regardless of the model's
+    primary key. To retrieve the value of the primary key, use `#id` instead. `read_attribute(:id)` for composite
+    primary key models will now return the value of the id column.
 
-## Rails 6.1.4 (June 24, 2021) ##
+    *Adrianna Chang*
 
-*   Do not try to rollback transactions that failed due to a `ActiveRecord::TransactionRollbackError`.
+*   Fix `change_table` setting datetime precision for 6.1 Migrations
 
-    *Jamie McCarthy*
+    *Hartley McGuire*
 
-*   Raise an error if `pool_config` is `nil` in `set_pool_config`.
+*   Fix change_column setting datetime precision for 6.1 Migrations
 
-    *Eileen M. Uchitelle*
+    *Hartley McGuire*
 
-*   Fix compatibility with `psych >= 4`.
+*   Add `ActiveRecord::Base#id_value` alias to access the raw value of a record's id column.
 
-    Starting in Psych 4.0.0 `YAML.load` behaves like `YAML.safe_load`. To preserve compatibility
-    Active Record's schema cache loader and `YAMLColumn` now uses `YAML.unsafe_load` if available.
+    This alias is only provided for models that declare an `:id` column.
 
-    *Jean Boussier*
+    *Adrianna Chang*
 
-*   Support using replicas when using `rails dbconsole`.
+*   Fix previous change tracking for `ActiveRecord::Store` when using a column with JSON structured database type
 
-    *Christopher Thornton*
+    Before, the methods to access the changes made during the last save `#saved_change_to_key?`, `#saved_change_to_key`, and `#key_before_last_save` did not work if the store was defined as a `store_accessor` on a column with a JSON structured database type
 
-*   Restore connection pools after transactional tests.
+    *Robert DiMartino*
 
-    *Eugene Kenny*
+*   Fully support `NULLS [NOT] DISTINCT` for PostgreSQL 15+ indexes.
 
-*   Change `upsert_all` to fails cleanly for MySQL when `:unique_by` is used.
+    Previous work was done to allow the index to be created in a migration, but it was not
+    supported in schema.rb. Additionally, the matching for `NULLS [NOT] DISTINCT` was not
+    in the correct order, which could have resulted in inconsistent schema detection.
 
-    *Bastian Bartmann*
+    *Gregory Jones*
 
-*   Fix user-defined `self.default_scope` to respect table alias.
+*   Allow escaping of literal colon characters in `sanitize_sql_*` methods when named bind variables are used
 
-    *Ryuta Kamizono*
+    *Justin Bull*
 
-*   Clear `@cache_keys` cache after `update_all`, `delete_all`, `destroy_all`.
+*   Fix `#previously_new_record?` to return true for destroyed records.
 
-    *Ryuta Kamizono*
+    Before, if a record was created and then destroyed, `#previously_new_record?` would return true.
+    Now, any UPDATE or DELETE to a record is considered a change, and will result in `#previously_new_record?`
+    returning false.
 
-*   Changed Arel predications `contains` and `overlaps` to use
-    `quoted_node` so that PostgreSQL arrays are quoted properly.
+    *Adrianna Chang*
 
-    *Bradley Priest*
+*   Specify callback in `has_secure_token`
 
-*   Fix `merge` when the `where` clauses have string contents.
+    ```ruby
+    class User < ApplicationRecord
+      has_secure_token on: :initialize
+    end
 
-    *Ryuta Kamizono*
+    User.new.token # => "abc123...."
+    ```
 
-*   Fix rollback of parent destruction with nested `dependent: :destroy`.
+    *Sean Doyle*
 
-    *Jacopo Beschi*
+*   Fix incrementation of in memory counter caches when associations overlap
 
-*   Fix binds logging for `"WHERE ... IN ..."` statements.
+    When two associations had a similarly named counter cache column, Active Record
+    could sometime increment the wrong one.
 
-    *Ricardo Díaz*
+    *Jacopo Beschi*, *Jean Boussier*
 
-*   Handle `false` in relation strict loading checks.
+*   Don't show secrets for Active Record's `Cipher::Aes256Gcm#inspect`.
 
-    Previously when a model had strict loading set to true and then had a
-    relation set `strict_loading` to false the false wasn't considered when
-    deciding whether to raise/warn about strict loading.
+    Before:
 
+    ```ruby
+    ActiveRecord::Encryption::Cipher::Aes256Gcm.new(secret).inspect
+    "#<ActiveRecord::Encryption::Cipher::Aes256Gcm:0x0000000104888038 ... @secret=\"\\xAF\\bFh]LV}q\\nl\\xB2U\\xB3 ... >"
+    ```
+
+    After:
+
+    ```ruby
+    ActiveRecord::Encryption::Cipher::Aes256Gcm(secret).inspect
+    "#<ActiveRecord::Encryption::Cipher::Aes256Gcm:0x0000000104888038>"
     ```
-    class Dog < ActiveRecord::Base
-      self.strict_loading_by_default = true
 
-      has_many :treats, strict_loading: false
+    *Petrik de Heus*
+
+*   Bring back the historical behavior of committing transaction on non-local return.
+
+    ```ruby
+    Model.transaction do
+      model.save
+      return
+      other_model.save # not executed
     end
     ```
 
-    In the example, `dog.treats` would still raise even though
-    `strict_loading` was set to false. This is a bug affecting more than
-    Active Storage which is why I made this PR superseding #41461. We need
-    to fix this for all applications since the behavior is a little
-    surprising. I took the test from #41461 and the code suggestion from #41453
-    with some additions.
+    Historically only raised errors would trigger a rollback, but in Ruby `2.3`, the `timeout` library
+    started using `throw` to interrupt execution which had the adverse effect of committing open transactions.
 
-    *Eileen M. Uchitelle*, *Radamés Roriz*
+    To solve this, in Active Record 6.1 the behavior was changed to instead rollback the transaction as it was safer
+    than to potentially commit an incomplete transaction.
 
-*   Fix numericality validator without precision.
+    Using `return`, `break` or `throw` inside a `transaction` block was essentially deprecated from Rails 6.1 onwards.
 
-    *Ryuta Kamizono*
+    However with the release of `timeout 0.4.0`, `Timeout.timeout` now raises an error again, and Active Record is able
+    to return to its original, less surprising, behavior.
 
-*   Fix aggregate attribute on Enum types.
+    This historical behavior can now be opt-ed in via:
 
-    *Ryuta Kamizono*
+    ```
+    Rails.application.config.active_record.commit_transaction_on_non_local_return = true
+    ```
 
-*   Fix `CREATE INDEX` statement generation for PostgreSQL.
+    And is the default for new applications created in Rails 7.1.
 
-    *eltongo*
+    *Jean Boussier*
 
-*   Fix where clause on enum attribute when providing array of strings.
+*   Deprecate `name` argument on `#remove_connection`.
 
-    *Ryuta Kamizono*
+    The `name` argument is deprecated on `#remove_connection` without replacement. `#remove_connection` should be called directly on the class that established the connection.
 
-*   Fix `unprepared_statement` to work it when nesting.
+    *Eileen M. Uchitelle*
 
-    *Ryuta Kamizono*
+*   Fix has_one through singular building with inverse.
 
+    Allows building of records from an association with a has_one through a
+    singular association with inverse. For belongs_to through associations,
+    linking the foreign key to the primary key model isn't needed.
+    For has_one, we cannot build records due to the association not being mutable.
 
-## Rails 6.1.3.2 (May 05, 2021) ##
+    *Gannon McGibbon*
 
-*   No changes.
+*   Disable database prepared statements when query logs are enabled
 
+    Prepared Statements and Query Logs are incompatible features due to query logs making every query unique.
 
-## Rails 6.1.3.1 (March 26, 2021) ##
+    *zzak, Jean Boussier*
 
-*   No changes.
+*   Support decrypting data encrypted non-deterministically with a SHA1 hash digest.
 
+    This adds a new Active Record encryption option to support decrypting data encrypted
+    non-deterministically with a SHA1 hash digest:
 
-## Rails 6.1.3 (February 17, 2021) ##
+    ```
+    Rails.application.config.active_record.encryption.support_sha1_for_non_deterministic_encryption = true
+    ```
 
-*   Fix the MySQL adapter to always set the right collation and charset
-    to the connection session.
+    The new option addresses a problem when upgrading from 7.0 to 7.1. Due to a bug in how Active Record
+    Encryption was getting initialized, the key provider used for non-deterministic encryption were using
+    SHA-1 as its digest class, instead of the one configured globally by Rails via
+    `Rails.application.config.active_support.key_generator_hash_digest_class`.
 
-    *Rafael Mendonça França*
+    *Cadu Ribeiro and Jorge Manrubia*
 
-*   Fix MySQL adapter handling of time objects when prepared statements
-    are enabled.
+*   Added PostgreSQL migration commands for enum rename, add value, and rename value.
 
-    *Rafael Mendonça França*
+    `rename_enum` and `rename_enum_value` are reversible. Due to Postgres
+    limitation, `add_enum_value` is not reversible since you cannot delete enum
+    values. As an alternative you should drop and recreate the enum entirely.
+
+    ```ruby
+    rename_enum :article_status, to: :article_state
+    ```
 
-*   Fix scoping in enum fields using conditions that would generate
-    an `IN` clause.
+    ```ruby
+    add_enum_value :article_state, "archived" # will be at the end of existing values
+    add_enum_value :article_state, "in review", before: "published"
+    add_enum_value :article_state, "approved", after: "in review"
+    ```
 
-    *Ryuta Kamizono*
+    ```ruby
+    rename_enum_value :article_state, from: "archived", to: "deleted"
+    ```
 
-*   Skip optimised #exist? query when #include? is called on a relation
-    with a having clause
+    *Ray Faddis*
 
-    Relations that have aliased select values AND a having clause that
-    references an aliased select value would generate an error when
-    #include? was called, due to an optimisation that would generate
-    call #exists? on the relation instead, which effectively alters
-    the select values of the query (and thus removes the aliased select
-    values), but leaves the having clause intact. Because the having
-    clause is then referencing an aliased column that is no longer
-    present in the simplified query, an ActiveRecord::InvalidStatement
-    error was raised.
+*   Allow composite primary key to be derived from schema
 
-    An sample query affected by this problem:
+    Booting an application with a schema that contains composite primary keys
+    will not issue warning and won't `nil`ify the `ActiveRecord::Base#primary_key` value anymore.
 
+    Given a `travel_routes` table definition and a `TravelRoute` model like:
     ```ruby
-    Author.select('COUNT(*) as total_posts', 'authors.*')
-          .joins(:posts)
-          .group(:id)
-          .having('total_posts > 2')
-          .include?(Author.first)
+    create_table :travel_routes, primary_key: [:origin, :destination], force: true do |t|
+      t.string :origin
+      t.string :destination
+    end
+
+    class TravelRoute < ActiveRecord::Base; end
     ```
+    The `TravelRoute.primary_key` value will be automatically derived to `["origin", "destination"]`
 
-    This change adds an addition check to the condition that skips the
-    simplified #exists? query, which simply checks for the presence of
-    a having clause.
+    *Nikita Vasilevsky*
 
-    Fixes #41417
+*   Include the `connection_pool` with exceptions raised from an adapter.
 
-    *Michael Smart*
+    The `connection_pool` provides added context such as the connection used
+    that led to the exception as well as which role and shard.
 
-*   Increment postgres prepared statement counter before making a prepared statement, so if the statement is aborted
-    without Rails knowledge (e.g., if app gets kill -9d during long-running query or due to Rack::Timeout), app won't end
-    up in perpetual crash state for being inconsistent with Postgres.
+    *Luan Vieira*
 
-    *wbharding*, *Martin Tepper*
+*   Support multiple column ordering for `find_each`, `find_in_batches` and `in_batches`.
 
+    When find_each/find_in_batches/in_batches are performed on a table with composite primary keys, ascending or descending order can be selected for each key.
 
-## Rails 6.1.2.1 (February 10, 2021) ##
+    ```ruby
+    Person.find_each(order: [:desc, :asc]) do |person|
+      person.party_all_night!
+    end
+    ```
 
-*   Fix possible DoS vector in PostgreSQL money type
+    *Takuya Kurimoto*
 
-    Carefully crafted input can cause a DoS via the regular expressions used
-    for validating the money format in the PostgreSQL adapter.  This patch
-    fixes the regexp.
+*   Fix where on association with has_one/has_many polymorphic relations.
 
-    Thanks to @dee-see from Hackerone for this patch!
+    Before:
+    ```ruby
+    Treasure.where(price_estimates: PriceEstimate.all)
+    #=> SELECT (...) WHERE "treasures"."id" IN (SELECT "price_estimates"."estimate_of_id" FROM "price_estimates")
+    ```
 
-    [CVE-2021-22880]
+    Later:
+    ```ruby
+    Treasure.where(price_estimates: PriceEstimate.all)
+    #=> SELECT (...) WHERE "treasures"."id" IN (SELECT "price_estimates"."estimate_of_id" FROM "price_estimates" WHERE "price_estimates"."estimate_of_type" = 'Treasure')
+    ```
 
-    *Aaron Patterson*
+    *Lázaro Nixon*
+
+*   Assign auto populated columns on Active Record record creation.
+
+    Changes record creation logic to allow for the `auto_increment` column to be assigned
+    immediately after creation regardless of it's relation to the model's primary key.
 
+    The PostgreSQL adapter benefits the most from the change allowing for any number of auto-populated
+    columns to be assigned on the object immediately after row insertion utilizing the `RETURNING` statement.
 
-## Rails 6.1.2 (February 09, 2021) ##
+    *Nikita Vasilevsky*
+
+*   Use the first key in the `shards` hash from `connected_to` for the `default_shard`.
+
+    Some applications may not want to use `:default` as a shard name in their connection model. Unfortunately Active Record expects there to be a `:default` shard because it must assume a shard to get the right connection from the pool manager. Rather than force applications to manually set this, `connects_to` can infer the default shard name from the hash of shards and will now assume that the first shard is your default.
 
-*   Fix timestamp type for sqlite3.
+    For example if your model looked like this:
+
+    ```ruby
+    class ShardRecord < ApplicationRecord
+      self.abstract_class = true
+
+      connects_to shards: {
+        shard_one: { writing: :shard_one },
+        shard_two: { writing: :shard_two }
+      }
+    ```
+
+    Then the `default_shard` for this class would be set to `shard_one`.
+
+    Fixes: #45390
 
     *Eileen M. Uchitelle*
 
-*   Make destroy async transactional.
+*   Fix mutation detection for serialized attributes backed by binary columns.
 
-    An active record rollback could occur while enqueuing a job. In this
-    case the job would enqueue even though the database deletion
-    rolledback putting things in a funky state.
+    *Jean Boussier*
 
-    Now the jobs are only enqueued until after the db transaction has been committed.
+*   Add `ActiveRecord.disconnect_all!` method to immediately close all connections from all pools.
 
-    *Cory Gwin*
+    *Jean Boussier*
 
-*   Fix malformed packet error in MySQL statement for connection configuration.
+*   Discard connections which may have been left in a transaction.
 
-    *robinroestenburg*
+    There are cases where, due to an error, `within_new_transaction` may unexpectedly leave a connection in an open transaction. In these cases the connection may be reused, and the following may occur:
+    - Writes appear to fail when they actually succeed.
+    - Writes appear to succeed when they actually fail.
+    - Reads return stale or uncommitted data.
 
-*   Connection specification now passes the "url" key as a configuration for the
-    adapter if the "url" protocol is "jdbc", "http", or "https". Previously only
-    urls with the "jdbc" prefix were passed to the Active Record Adapter, others
-    are assumed to be adapter specification urls.
+    Previously, the following case was detected:
+    - An error is encountered during the transaction, then another error is encountered while attempting to roll it back.
 
-    Fixes #41137.
+    Now, the following additional cases are detected:
+    - An error is encountered just after successfully beginning a transaction.
+    - An error is encountered while committing a transaction, then another error is encountered while attempting to roll it back.
+    - An error is encountered while rolling back a transaction.
 
-    *Jonathan Bracy*
+    *Nick Dower*
 
-*   Fix granular connection swapping when there are multiple abstract classes.
+*   Active Record query cache now evicts least recently used entries
 
-    *Eileen M. Uchitelle*
+    By default it only keeps the `100` most recently used queries.
 
-*   Fix `find_by` with custom primary key for belongs_to association.
+    The cache size can be configured via `database.yml`
 
-    *Ryuta Kamizono*
+    ```yaml
+    development:
+      adapter: mysql2
+      query_cache: 200
+    ```
 
-*   Add support for `rails console --sandbox` for multiple database applications.
+    It can also be entirely disabled:
 
-    *alpaca-tc*
+    ```yaml
+    development:
+      adapter: mysql2
+      query_cache: false
+    ```
 
-*   Fix `where` on polymorphic association with empty array.
+    *Jean Boussier*
 
-    *Ryuta Kamizono*
+*   Deprecate `check_pending!` in favor of `check_all_pending!`.
 
-*   Fix preventing writes for `ApplicationRecord`.
+    `check_pending!` will only check for pending migrations on the current database connection or the one passed in. This has been deprecated in favor of `check_all_pending!` which will find all pending migrations for the database configurations in a given environment.
 
     *Eileen M. Uchitelle*
 
+*   Make `increment_counter`/`decrement_counter` accept an amount argument
 
-## Rails 6.1.1 (January 07, 2021) ##
+    ```ruby
+    Post.increment_counter(:comments_count, 5, by: 3)
+    ```
 
-*   Fix fixtures loading when strict loading is enabled for the association.
+    *fatkodima*
 
-    *Alex Ghiculescu*
+*   Add support for `Array#intersect?` to `ActiveRecord::Relation`.
 
-*   Fix `where` with custom primary key for belongs_to association.
+    `Array#intersect?` is only available on Ruby 3.1 or later.
 
-    *Ryuta Kamizono*
+    This allows the Rubocop `Style/ArrayIntersect` cop to work with `ActiveRecord::Relation` objects.
 
-*   Fix `where` with aliased associations.
+    *John Harry Kelly*
 
-    *Ryuta Kamizono*
+*   The deferrable foreign key can be passed to `t.references`.
 
-*   Fix `composed_of` with symbol mapping.
+    *Hiroyuki Ishii*
 
-    *Ryuta Kamizono*
+*   Deprecate `deferrable: true` option of `add_foreign_key`.
 
-*   Don't skip money's type cast for pluck and calculations.
+    `deferrable: true` is deprecated in favor of `deferrable: :immediate`, and
+    will be removed in Rails 7.2.
 
-    *Ryuta Kamizono*
+    Because `deferrable: true` and `deferrable: :deferred` are hard to understand.
+    Both true and :deferred are truthy values.
+    This behavior is the same as the deferrable option of the add_unique_key method, added in #46192.
 
-*   Fix `where` on polymorphic association with non Active Record object.
+    *Hiroyuki Ishii*
 
-    *Ryuta Kamizono*
+*   `AbstractAdapter#execute` and `#exec_query` now clear the query cache
 
-*   Make sure `db:prepare` works even the schema file doesn't exist.
+    If you need to perform a read only SQL query without clearing the query
+    cache, use `AbstractAdapter#select_all`.
 
-    *Rafael Mendonça França*
+    *Jean Boussier*
 
-*   Fix complicated `has_many :through` with nested where condition.
+*   Make `.joins` / `.left_outer_joins` work with CTEs.
 
-    *Ryuta Kamizono*
+    For example:
 
-*   Handle STI models for `has_many dependent: :destroy_async`.
+    ```ruby
+    Post
+     .with(commented_posts: Comment.select(:post_id).distinct)
+     .joins(:commented_posts)
+    #=> WITH (...) SELECT ... INNER JOIN commented_posts on posts.id = commented_posts.post_id
+    ```
 
-    *Muhammad Usman*
+    *Vladimir Dementyev*
 
-*   Restore possibility of passing `false` to :polymorphic option of `belongs_to`.
+*   Add a load hook for `ActiveRecord::ConnectionAdapters::Mysql2Adapter`
+    (named `active_record_mysql2adapter`) to allow for overriding aspects of the
+    `ActiveRecord::ConnectionAdapters::Mysql2Adapter` class. This makes `Mysql2Adapter`
+    consistent with `PostgreSQLAdapter` and `SQLite3Adapter` that already have load hooks.
 
-    Previously, passing `false` would trigger the option validation logic
-    to throw an error saying :polymorphic would not be a valid option.
+    *fatkodima*
 
-    *glaszig*
+*   Introduce adapter for Trilogy database client
 
-*   Allow adding nonnamed expression indexes to be revertible.
+    Trilogy is a MySQL-compatible database client. Rails applications can use Trilogy
+    by configuring their `config/database.yml`:
 
-    Fixes #40732.
+    ```yaml
+    development:
+    adapter: trilogy
+    database: blog_development
+    pool: 5
+    ```
 
-    Previously, the following code would raise an error, when executed while rolling back,
-    and the index name should be specified explicitly. Now, the index name is inferred
-    automatically.
+    Or by using the `DATABASE_URL` environment variable:
 
     ```ruby
-    add_index(:items, "to_tsvector('english', description)")
+    ENV['DATABASE_URL'] # => "trilogy://localhost/blog_development?pool=5"
     ```
 
-    *fatkodima*
+    *Adrianna Chang*
 
+*   `after_commit` callbacks defined on models now execute in the correct order.
 
-## Rails 6.1.0 (December 09, 2020) ##
+    ```ruby
+    class User < ActiveRecord::Base
+      after_commit { puts("this gets called first") }
+      after_commit { puts("this gets called second") }
+    end
+    ```
 
-*   Only warn about negative enums if a positive form that would cause conflicts exists.
+    Previously, the callbacks executed in the reverse order. To opt in to the new behaviour:
+
+    ```ruby
+    config.active_record.run_after_transaction_callbacks_in_order_defined = true
+    ```
 
-    Fixes #39065.
+    This is the default for new apps.
 
     *Alex Ghiculescu*
 
-*   Change `attribute_for_inspect` to take `filter_attributes` in consideration.
+*   Infer `foreign_key` when `inverse_of` is present on `has_one` and `has_many` associations.
 
-    *Rafael Mendonça França*
+    ```ruby
+    has_many :citations, foreign_key: "book1_id", inverse_of: :book
+    ```
+
+    can be simplified to
+
+    ```ruby
+    has_many :citations, inverse_of: :book
+    ```
+
+    and the foreign_key will be read from the corresponding `belongs_to` association.
+
+    *Daniel Whitney*
+
+*   Limit max length of auto generated index names
+
+    Auto generated index names are now limited to 62 bytes, which fits within
+    the default index name length limits for MySQL, Postgres and SQLite.
+
+    Any index name over the limit will fallback to the new short format.
+
+    Before (too long):
+    ```
+    index_testings_on_foo_and_bar_and_first_name_and_last_name_and_administrator
+    ```
 
-*   Fix odd behavior of inverse_of with multiple belongs_to to same class.
+    After (short format):
+    ```
+    idx_on_foo_bar_first_name_last_name_administrator_5939248142
+    ```
+
+    The short format includes a hash to ensure the name is unique database-wide.
 
-    Fixes #35204.
+    *Mike Coutermarsh*
 
-    *Tomoyuki Kai*
+*   Introduce a more stable and optimized Marshal serializer for Active Record models.
+
+    Can be enabled with `config.active_record.marshalling_format_version = 7.1`.
+
+    *Jean Boussier*
 
-*   Build predicate conditions with objects that delegate `#id` and primary key:
+*   Allow specifying where clauses with column-tuple syntax.
+
+    Querying through `#where` now accepts a new tuple-syntax which accepts, as
+    a key, an array of columns and, as a value, an array of corresponding tuples.
+    The key specifies a list of columns, while the value is an array of
+    ordered-tuples that conform to the column list.
+
+    For instance:
 
     ```ruby
-    class AdminAuthor
-      delegate_missing_to :@author
+    # Cpk::Book => Cpk::Book(author_id: integer, number: integer, title: string, revision: integer)
+    # Cpk::Book.primary_key => ["author_id", "number"]
 
-      def initialize(author)
-        @author = author
-      end
+    book = Cpk::Book.create!(author_id: 1, number: 1)
+    Cpk::Book.where(Cpk::Book.primary_key => [[1, 2]]) # => [book]
+
+    # Topic => Topic(id: integer, title: string, author_name: string...)
+
+    Topic.where([:title, :author_name] => [["The Alchemist", "Paulo Coelho"], ["Harry Potter", "J.K Rowling"]])
+    ```
+
+    *Paarth Madan*
+
+*   Allow warning codes to be ignore when reporting SQL warnings.
+
+    Active Record config that can ignore warning codes
+
+    ```ruby
+    # Configure allowlist of warnings that should always be ignored
+    config.active_record.db_warnings_ignore = [
+      "1062", # MySQL Error 1062: Duplicate entry
+    ]
+    ```
+
+    This is supported for the MySQL and PostgreSQL adapters.
+
+    *Nick Borromeo*
+
+*   Introduce `:active_record_fixtures` lazy load hook.
+
+    Hooks defined with this name will be run whenever `TestFixtures` is included
+    in a class.
+
+    ```ruby
+    ActiveSupport.on_load(:active_record_fixtures) do
+      self.fixture_paths << "test/fixtures"
     end
 
-    Post.where(author: AdminAuthor.new(author))
+    klass = Class.new
+    klass.include(ActiveRecord::TestFixtures)
+
+    klass.fixture_paths # => ["test/fixtures"]
     ```
 
-    *Sean Doyle*
+    *Andrew Novoselac*
 
-*   Add `connected_to_many` API.
+*   Introduce `TestFixtures#fixture_paths`.
 
-    This API allows applications to connect to multiple databases at once without switching all of them or implementing a deeply nested stack.
+    Multiple fixture paths can now be specified using the `#fixture_paths` accessor.
+    Apps will continue to have `test/fixtures` as their one fixture path by default,
+    but additional fixture paths can be specified.
 
-    Before:
+    ```ruby
+    ActiveSupport::TestCase.fixture_paths << "component1/test/fixtures"
+    ActiveSupport::TestCase.fixture_paths << "component2/test/fixtures"
+    ```
 
-        AnimalsRecord.connected_to(role: :reading) do
-          MealsRecord.connected_to(role: :reading) do
-            Dog.first # read from animals replica
-            Dinner.first # read from meals replica
-            Person.first # read from primary writer
-          end
-        end
+    `TestFixtures#fixture_path` is now deprecated.
 
-    After:
+    *Andrew Novoselac*
 
-        ActiveRecord::Base.connected_to_many([AnimalsRecord, MealsRecord], role: :reading) do
-          Dog.first # read from animals replica
-          Dinner.first # read from meals replica
-          Person.first # read from primary writer
-        end
+*   Adds support for deferrable exclude constraints in PostgreSQL.
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+    By default, exclude constraints in PostgreSQL are checked after each statement.
+    This works for most use cases, but becomes a major limitation when replacing
+    records with overlapping ranges by using multiple statements.
 
-*   Add option to raise or log for `ActiveRecord::StrictLoadingViolationError`.
+    ```ruby
+    exclusion_constraint :users, "daterange(valid_from, valid_to) WITH &&", deferrable: :immediate
+    ```
 
-    Some applications may not want to raise an error in production if using `strict_loading`. This would allow an application to set strict loading to log for the production environment while still raising in development and test environments.
+    Passing `deferrable: :immediate` checks constraint after each statement,
+    but allows manually deferring the check using `SET CONSTRAINTS ALL DEFERRED`
+    within a transaction. This will cause the excludes to be checked after the transaction.
 
-    Set `config.active_record.action_on_strict_loading_violation` to `:log` errors instead of raising.
+    It's also possible to change the default behavior from an immediate check
+    (after the statement), to a deferred check (after the transaction):
 
-    *Eileen M. Uchitelle*
+    ```ruby
+    exclusion_constraint :users, "daterange(valid_from, valid_to) WITH &&", deferrable: :deferred
+    ```
 
-*   Allow the inverse of a `has_one` association that was previously autosaved to be loaded.
+    *Hiroyuki Ishii*
 
-    Fixes #34255.
+*   Respect `foreign_type` option to `delegated_type` for `{role}_class` method.
 
-    *Steven Weber*
+    Usage of `delegated_type` with non-conventional `{role}_type` column names can now be specified with `foreign_type` option.
+    This option is the same as `foreign_type` as forwarded to the underlying `belongs_to` association that `delegated_type` wraps.
 
-*   Optimise the length of index names for polymorphic references by using the reference name rather than the type and id column names.
+    *Jason Karns*
 
-    Because the default behaviour when adding an index with multiple columns is to use all column names in the index name, this could frequently lead to overly long index names for polymorphic references which would fail the migration if it exceeded the database limit.
+*   Add support for unique constraints (PostgreSQL-only).
 
-    This change reduces the chance of that happening by using the reference name, e.g. `index_my_table_on_my_reference`.
+    ```ruby
+    add_unique_key :sections, [:position], deferrable: :deferred, name: "unique_section_position"
+    remove_unique_key :sections, name: "unique_section_position"
+    ```
 
-    Fixes #38655.
+    See PostgreSQL's [Unique Constraints](https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-UNIQUE-CONSTRAINTS) documentation for more on unique constraints.
 
-    *Luke Redpath*
+    By default, unique constraints in PostgreSQL are checked after each statement.
+    This works for most use cases, but becomes a major limitation when replacing
+    records with unique column by using multiple statements.
 
-*   MySQL: Uniqueness validator now respects default database collation,
-    no longer enforce case sensitive comparison by default.
+    An example of swapping unique columns between records.
 
-    *Ryuta Kamizono*
+    ```ruby
+    # position is unique column
+    old_item = Item.create!(position: 1)
+    new_item = Item.create!(position: 2)
 
-*   Remove deprecated methods from `ActiveRecord::ConnectionAdapters::DatabaseLimits`.
+    Item.transaction do
+      old_item.update!(position: 2)
+      new_item.update!(position: 1)
+    end
+    ```
 
-    `column_name_length`
-    `table_name_length`
-    `columns_per_table`
-    `indexes_per_table`
-    `columns_per_multicolumn_index`
-    `sql_query_length`
-    `joins_per_query`
+    Using the default behavior, the transaction would fail when executing the
+    first `UPDATE` statement.
 
-    *Rafael Mendonça França*
+    By passing the `:deferrable` option to the `add_unique_key` statement in
+    migrations, it's possible to defer this check.
 
-*   Remove deprecated `ActiveRecord::ConnectionAdapters::AbstractAdapter#supports_multi_insert?`.
+    ```ruby
+    add_unique_key :items, [:position], deferrable: :immediate
+    ```
 
-    *Rafael Mendonça França*
+    Passing `deferrable: :immediate` does not change the behaviour of the previous example,
+    but allows manually deferring the check using `SET CONSTRAINTS ALL DEFERRED` within a transaction.
+    This will cause the unique constraints to be checked after the transaction.
 
-*   Remove deprecated `ActiveRecord::ConnectionAdapters::AbstractAdapter#supports_foreign_keys_in_create?`.
+    It's also possible to adjust the default behavior from an immediate
+    check (after the statement), to a deferred check (after the transaction):
 
-    *Rafael Mendonça França*
+    ```ruby
+    add_unique_key :items, [:position], deferrable: :deferred
+    ```
 
-*   Remove deprecated `ActiveRecord::ConnectionAdapters::PostgreSQLAdapter#supports_ranges?`.
+    If you want to change an existing unique index to deferrable, you can use :using_index
+    to create deferrable unique constraints.
 
-    *Rafael Mendonça França*
+    ```ruby
+    add_unique_key :items, deferrable: :deferred, using_index: "index_items_on_position"
+    ```
 
-*   Remove deprecated `ActiveRecord::Base#update_attributes` and `ActiveRecord::Base#update_attributes!`.
+    *Hiroyuki Ishii*
+
+*   Remove deprecated `Tasks::DatabaseTasks.schema_file_type`.
 
     *Rafael Mendonça França*
 
-*   Remove deprecated `migrations_path` argument in `ActiveRecord::ConnectionAdapter::SchemaStatements#assume_migrated_upto_version`.
+*   Remove deprecated `config.active_record.partial_writes`.
 
     *Rafael Mendonça França*
 
-*   Remove deprecated `config.active_record.sqlite3.represent_boolean_as_integer`.
+*   Remove deprecated `ActiveRecord::Base` config accessors.
 
     *Rafael Mendonça França*
 
-*   `relation.create` does no longer leak scope to class level querying methods
-    in initialization block and callbacks.
+*   Remove the `:include_replicas` argument from `configs_for`. Use `:include_hidden` argument instead.
 
-    Before:
+    *Eileen M. Uchitelle*
 
-        User.where(name: "John").create do |john|
-          User.find_by(name: "David") # => nil
-        end
+*   Allow applications to lookup a config via a custom hash key.
 
-    After:
+    If you have registered a custom config or want to find configs where the hash matches a specific key, now you can pass `config_key` to `configs_for`. For example if you have a `db_config` with the key `vitess` you can look up a database configuration hash by  matching that key.
 
-        User.where(name: "John").create do |john|
-          User.find_by(name: "David") # => #<User name: "David", ...>
-        end
+    ```ruby
+    ActiveRecord::Base.configurations.configs_for(env_name: "development", name: "primary", config_key: :vitess)
+    ActiveRecord::Base.configurations.configs_for(env_name: "development", config_key: :vitess)
+    ```
 
-    *Ryuta Kamizono*
+    *Eileen M. Uchitelle*
+
+*   Allow applications to register a custom database configuration handler.
+
+    Adds a mechanism for registering a custom handler for cases where you want database configurations to respond to custom methods. This is useful for non-Rails database adapters or tools like Vitess that you may want to configure differently from a standard `HashConfig` or `UrlConfig`.
+
+    Given the following database YAML we want the `animals` db to create a `CustomConfig` object instead while the `primary` database will be a `UrlConfig`:
+
+    ```yaml
+    development:
+      primary:
+        url: postgres://localhost/primary
+      animals:
+        url: postgres://localhost/animals
+        custom_config:
+          sharded: 1
+    ```
 
-*   Named scope chain does no longer leak scope to class level querying methods.
+    To register a custom handler first make a class that has your custom methods:
 
-        class User < ActiveRecord::Base
-          scope :david, -> { User.where(name: "David") }
+    ```ruby
+    class CustomConfig < ActiveRecord::DatabaseConfigurations::UrlConfig
+      def sharded?
+        custom_config.fetch("sharded", false)
+      end
+
+      private
+        def custom_config
+          configuration_hash.fetch(:custom_config)
         end
+    end
+    ```
 
-    Before:
+    Then register the config in an initializer:
 
-        User.where(name: "John").david
-        # SELECT * FROM users WHERE name = 'John' AND name = 'David'
+    ```ruby
+    ActiveRecord::DatabaseConfigurations.register_db_config_handler do |env_name, name, url, config|
+      next unless config.key?(:custom_config)
+      CustomConfig.new(env_name, name, url, config)
+    end
+    ```
 
-    After:
+    When the application is booted, configuration hashes with the `:custom_config` key will be `CustomConfig` objects and respond to `sharded?`. Applications must handle the condition in which Active Record should use their custom handler.
 
-        User.where(name: "John").david
-        # SELECT * FROM users WHERE name = 'David'
+    *Eileen M. Uchitelle and John Crepezzi*
 
-    *Ryuta Kamizono*
+*   `ActiveRecord::Base.serialize` no longer uses YAML by default.
 
-*   Remove deprecated methods from `ActiveRecord::DatabaseConfigurations`.
+    YAML isn't particularly performant and can lead to security issues
+    if not used carefully.
 
-    `fetch`
-    `each`
-    `first`
-    `values`
-    `[]=`
+    Unfortunately there isn't really any good serializers in Ruby's stdlib
+    to replace it.
 
-    *Rafael Mendonça França*
+    The obvious choice would be JSON, which is a fine format for this use case,
+    however the JSON serializer in Ruby's stdlib isn't strict enough, as it fallback
+    to casting unknown types to strings, which could lead to corrupted data.
 
-*   `where.not` now generates NAND predicates instead of NOR.
+    Some third party JSON libraries like `Oj` have a suitable strict mode.
 
-     Before:
+    So it's preferable that users choose a serializer based on their own constraints.
 
-        User.where.not(name: "Jon", role: "admin")
-        # SELECT * FROM users WHERE name != 'Jon' AND role != 'admin'
+    The original default can be restored by setting `config.active_record.default_column_serializer = YAML`.
 
-     After:
+    *Jean Boussier*
 
-        User.where.not(name: "Jon", role: "admin")
-        # SELECT * FROM users WHERE NOT (name == 'Jon' AND role == 'admin')
+*   `ActiveRecord::Base.serialize` signature changed.
 
-    *Rafael Mendonça França*
+    Rather than a single positional argument that accepts two possible
+    types of values, `serialize` now accepts two distinct keyword arguments.
 
-*   Remove deprecated `ActiveRecord::Result#to_hash` method.
+    Before:
 
-    *Rafael Mendonça França*
+    ```ruby
+    serialize :content, JSON
+    serialize :backtrace, Array
+    ```
 
-*   Deprecate `ActiveRecord::Base.allow_unsafe_raw_sql`.
+    After:
 
-    *Rafael Mendonça França*
+    ```ruby
+    serialize :content, coder: JSON
+    serialize :backtrace, type: Array
+    ```
 
-*   Remove deprecated support for using unsafe raw SQL in `ActiveRecord::Relation` methods.
+    *Jean Boussier*
 
-    *Rafael Mendonça França*
+*   YAML columns use `YAML.safe_dump` if available.
 
-*   Allow users to silence the "Rails couldn't infer whether you are using multiple databases..."
-    message using `config.active_record.suppress_multiple_database_warning`.
+    As of `psych 5.1.0`, `YAML.safe_dump` can now apply the same permitted
+    types restrictions than `YAML.safe_load`.
 
-    *Omri Gabay*
+    It's preferable to ensure the payload only use allowed types when we first
+    try to serialize it, otherwise you may end up with invalid records in the
+    database.
 
-*   Connections can be granularly switched for abstract classes when `connected_to` is called.
+    *Jean Boussier*
 
-    This change allows `connected_to` to switch a `role` and/or `shard` for a single abstract class instead of all classes globally. Applications that want to use the new feature need to set `config.active_record.legacy_connection_handling` to `false` in their application configuration.
+*   `ActiveRecord::QueryLogs` better handle broken encoding.
 
-    Example usage:
+    It's not uncommon when building queries with BLOB fields to contain
+    binary data. Unless the call carefully encode the string in ASCII-8BIT
+    it generally end up being encoded in `UTF-8`, and `QueryLogs` would
+    end up failing on it.
 
-    Given an application we have a `User` model that inherits from `ApplicationRecord` and a `Dog` model that inherits from `AnimalsRecord`. `AnimalsRecord` and `ApplicationRecord` have writing and reading connections as well as shard `default`, `one`, and `two`.
+    `ActiveRecord::QueryLogs` no longer depend on the query to be properly encoded.
 
-    ```ruby
-    ActiveRecord::Base.connected_to(role: :reading) do
-      User.first # reads from default replica
-      Dog.first # reads from default replica
+    *Jean Boussier*
 
-      AnimalsRecord.connected_to(role: :writing, shard: :one) do
-        User.first # reads from default replica
-        Dog.first # reads from shard one primary
-      end
+*   Fix a bug where `ActiveRecord::Generators::ModelGenerator` would not respect create_table_migration template overrides.
 
-      User.first # reads from default replica
-      Dog.first # reads from default replica
+    ```
+    rails g model create_books title:string content:text
+    ```
+    will now read from the create_table_migration.rb.tt template in the following locations in order:
+    ```
+    lib/templates/active_record/model/create_table_migration.rb
+    lib/templates/active_record/migration/create_table_migration.rb
+    ```
 
-      ApplicationRecord.connected_to(role: :writing, shard: :two) do
-        User.first # reads from shard two primary
-        Dog.first # reads from default replica
-      end
-    end
+    *Spencer Neste*
+
+*   `ActiveRecord::Relation#explain` now accepts options.
+
+    For databases and adapters which support them (currently PostgreSQL
+    and MySQL), options can be passed to `explain` to provide more
+    detailed query plan analysis:
+
+    ```ruby
+    Customer.where(id: 1).joins(:orders).explain(:analyze, :verbose)
     ```
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+    *Reid Lynch*
+
+*   Multiple `Arel::Nodes::SqlLiteral` nodes can now be added together to
+    form `Arel::Nodes::Fragments` nodes. This allows joining several pieces
+    of SQL.
+
+    *Matthew Draper*, *Ole Friis*
 
-*   Allow double-dash comment syntax when querying read-only databases
+*   `ActiveRecord::Base#signed_id` raises if called on a new record.
 
-    *James Adam*
+    Previously it would return an ID that was not usable, since it was based on `id = nil`.
+
+    *Alex Ghiculescu*
 
-*   Add `values_at` method.
+*   Allow SQL warnings to be reported.
 
-    Returns an array containing the values associated with the given methods.
+    Active Record configs can be set to enable SQL warning reporting.
 
     ```ruby
-    topic = Topic.first
-    topic.values_at(:title, :author_name)
-    # => ["Budget", "Jason"]
+    # Configure action to take when SQL query produces warning
+    config.active_record.db_warnings_action = :raise
+
+    # Configure allowlist of warnings that should always be ignored
+    config.active_record.db_warnings_ignore = [
+      /Invalid utf8mb4 character string/,
+      "An exact warning message",
+    ]
     ```
 
-    Similar to `Hash#values_at` but on an Active Record instance.
+    This is supported for the MySQL and PostgreSQL adapters.
 
-    *Guillaume Briday*
+    *Adrianna Chang*, *Paarth Madan*
 
-*   Fix `read_attribute_before_type_cast` to consider attribute aliases.
+*   Add `#regroup` query method as a short-hand for `.unscope(:group).group(fields)`
 
-    *Marcelo Lauxen*
-
-*   Support passing record to uniqueness validator `:conditions` callable:
+    Example:
 
     ```ruby
-    class Article < ApplicationRecord
-      validates_uniqueness_of :title, conditions: ->(article) {
-        published_at = article.published_at
-        where(published_at: published_at.beginning_of_year..published_at.end_of_year)
-      }
-    end
+    Post.group(:title).regroup(:author)
+    # SELECT `posts`.`*` FROM `posts` GROUP BY `posts`.`author`
     ```
 
-    *Eliot Sykes*
+    *Danielius Visockas*
 
-*   `BatchEnumerator#update_all` and `BatchEnumerator#delete_all` now return the
-    total number of rows affected, just like their non-batched counterparts.
+*   PostgreSQL adapter method `enable_extension` now allows parameter to be `[schema_name.]<extension_name>`
+    if the extension must be installed on another schema.
+
+    Example: `enable_extension('heroku_ext.hstore')`
+
+    *Leonardo Luarte*
+
+*   Add `:include` option to `add_index`.
+
+    Add support for including non-key columns in indexes for PostgreSQL
+    with the `INCLUDE` parameter.
 
     ```ruby
-    Person.in_batches.update_all("first_name = 'Eugene'") # => 42
-    Person.in_batches.delete_all # => 42
+    add_index(:users, :email, include: [:id, :created_at])
     ```
 
-    Fixes #40287.
+    will result in:
 
-    *Eugene Kenny*
+    ```sql
+    CREATE INDEX index_users_on_email USING btree (email) INCLUDE (id, created_at)
+    ```
 
-*   Add support for PostgreSQL `interval` data type with conversion to
-    `ActiveSupport::Duration` when loading records from database and
-    serialization to ISO 8601 formatted duration string on save.
-    Add support to define a column in migrations and get it in a schema dump.
-    Optional column precision is supported.
+    *Steve Abrams*
 
-    To use this in 6.1, you need to place the next string to your model file:
+*   `ActiveRecord::Relation`’s `#any?`, `#none?`, and `#one?` methods take an optional pattern
+    argument, more closely matching their `Enumerable` equivalents.
 
-        attribute :duration, :interval
+    *George Claghorn*
 
-    To keep old behavior until 7.0 is released:
+*   Add `ActiveRecord::Base.normalizes` for declaring attribute normalizations.
 
-        attribute :duration, :string
+    An attribute normalization is applied when the attribute is assigned or
+    updated, and the normalized value will be persisted to the database.  The
+    normalization is also applied to the corresponding keyword argument of query
+    methods, allowing records to be queried using unnormalized values.
 
-    Example:
+    For example:
 
-        create_table :events do |t|
-          t.string   :name
-          t.interval :duration
-        end
+      ```ruby
+      class User < ActiveRecord::Base
+        normalizes :email, with: -> email { email.strip.downcase }
+        normalizes :phone, with: -> phone { phone.delete("^0-9").delete_prefix("1") }
+      end
 
-        class Event < ApplicationRecord
-          attribute :duration, :interval
-        end
+      user = User.create(email: " CRUISE-CONTROL@EXAMPLE.COM\n")
+      user.email                  # => "cruise-control@example.com"
+
+      user = User.find_by(email: "\tCRUISE-CONTROL@EXAMPLE.COM ")
+      user.email                  # => "cruise-control@example.com"
+      user.email_before_type_cast # => "cruise-control@example.com"
+
+      User.where(email: "\tCRUISE-CONTROL@EXAMPLE.COM ").count         # => 1
+      User.where(["email = ?", "\tCRUISE-CONTROL@EXAMPLE.COM "]).count # => 0
+
+      User.exists?(email: "\tCRUISE-CONTROL@EXAMPLE.COM ")         # => true
+      User.exists?(["email = ?", "\tCRUISE-CONTROL@EXAMPLE.COM "]) # => false
+
+      User.normalize_value_for(:phone, "+1 (555) 867-5309") # => "5558675309"
+      ```
+
+    *Jonathan Hefner*
 
-        Event.create!(name: 'Rock Fest', duration: 2.days)
-        Event.last.duration # => 2 days
-        Event.last.duration.iso8601 # => "P2D"
-        Event.new(duration: 'P1DT12H3S').duration # => 1 day, 12 hours, and 3 seconds
-        Event.new(duration: '1 day') # Unknown value will be ignored and NULL will be written to database
+*   Hide changes to before_committed! callback behaviour behind flag.
 
-    *Andrey Novikov*
+    In #46525, behavior around before_committed! callbacks was changed so that callbacks
+    would run on every enrolled record in a transaction, not just the first copy of a record.
+    This change in behavior is now controlled by a configuration option,
+    `config.active_record.before_committed_on_all_records`. It will be enabled by default on Rails 7.1.
 
-*   Allow associations supporting the `dependent:` key to take `dependent: :destroy_async`.
+    *Adrianna Chang*
+
+*   The `namespaced_controller` Query Log tag now matches the `controller` format
+
+    For example, a request processed by `NameSpaced::UsersController` will now log as:
+
+    ```
+    :controller # "users"
+    :namespaced_controller # "name_spaced/users"
+    ```
+
+    *Alex Ghiculescu*
+
+*   Return only unique ids from ActiveRecord::Calculations#ids
+
+    Updated ActiveRecord::Calculations#ids to only return the unique ids of the base model
+    when using eager_load, preload and includes.
 
     ```ruby
-    class Account < ActiveRecord::Base
-        belongs_to :supplier, dependent: :destroy_async
-    end
+    Post.find_by(id: 1).comments.count
+    # => 5
+    Post.includes(:comments).where(id: 1).pluck(:id)
+    # => [1, 1, 1, 1, 1]
+    Post.includes(:comments).where(id: 1).ids
+    # => [1]
     ```
 
-    `:destroy_async` will enqueue a job to destroy associated records in the background.
+    *Joshua Young*
 
-    *DHH*, *George Claghorn*, *Cory Gwin*, *Rafael Mendonça França*, *Adrianna Chang*
+*   Stop using `LOWER()` for case-insensitive queries on `citext` columns
 
-*   Add `SKIP_TEST_DATABASE` environment variable to disable modifying the test database when `rails db:create` and `rails db:drop` are called.
+    Previously, `LOWER()` was added for e.g. uniqueness validations with
+    `case_sensitive: false`.
+    It wasn't mentioned in the documentation that the index without `LOWER()`
+    wouldn't be used in this case.
 
-    *Jason Schweier*
+    *Phil Pirozhkov*
 
-*   `connects_to` can only be called on `ActiveRecord::Base` or abstract classes.
+*   Extract `#sync_timezone_changes` method in AbstractMysqlAdapter to enable subclasses
+    to sync database timezone changes without overriding `#raw_execute`.
 
-    Ensure that `connects_to` can only be called from `ActiveRecord::Base` or abstract classes. This protects the application from opening duplicate or too many connections.
+    *Adrianna Chang*, *Paarth Madan*
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+*   Do not write additional new lines when dumping sql migration versions
 
-*   All connection adapters `execute` now raises `ActiveRecord::ConnectionNotEstablished` rather than
-    `ActiveRecord::StatementInvalid` when they encounter a connection error.
+    This change updates the `insert_versions_sql` function so that the database insert string containing the current database migration versions does not end with two additional new lines.
 
-    *Jean Boussier*
+    *Misha Schwartz*
 
-*   `Mysql2Adapter#quote_string` now raises `ActiveRecord::ConnectionNotEstablished` rather than
-    `ActiveRecord::StatementInvalid` when it can't connect to the MySQL server.
+*   Fix `composed_of` value freezing and duplication.
 
-    *Jean Boussier*
+    Previously composite values exhibited two confusing behaviors:
 
-*   Add support for check constraints that are `NOT VALID` via `validate: false` (PostgreSQL-only).
+    - When reading a compositve value it'd _NOT_ be frozen, allowing it to get out of sync with its underlying database
+      columns.
+    - When writing a compositve value the argument would be frozen, potentially confusing the caller.
 
-    *Alex Robbin*
+    Currently, composite values instantiated based on database columns are frozen (addressing the first issue) and
+    assigned compositve values are duplicated and the duplicate is frozen (addressing the second issue).
 
-*   Ensure the default configuration is considered primary or first for an environment
+    *Greg Navis*
 
-    If a multiple database application provides a configuration named primary, that will be treated as default. In applications that do not have a primary entry, the default database configuration will be the first configuration for an environment.
+*   Fix redundant updates to the column insensitivity cache
 
-    *Eileen M. Uchitelle*
+    Fixed redundant queries checking column capability for insensitive
+    comparison.
 
-*   Allow `where` references association names as joined table name aliases.
+    *Phil Pirozhkov*
 
-    ```ruby
-    class Comment < ActiveRecord::Base
-      enum label: [:default, :child]
-      has_many :children, class_name: "Comment", foreign_key: :parent_id
-    end
+*   Allow disabling methods generated by `ActiveRecord.enum`.
 
-    # ... FROM comments LEFT OUTER JOIN comments children ON ... WHERE children.label = 1
-    Comment.includes(:children).where("children.label": "child")
-    ```
+    *Alfred Dominic*
 
-    *Ryuta Kamizono*
+*   Avoid validating `belongs_to` association if it has not changed.
 
-*   Support storing demodulized class name for polymorphic type.
+    Previously, when updating a record, Active Record will perform an extra query to check for the presence of
+    `belongs_to` associations (if the presence is configured to be mandatory), even if that attribute hasn't changed.
 
-    Before Rails 6.1, storing demodulized class name is supported only for STI type
-    by `store_full_sti_class` class attribute.
+    Currently, only `belongs_to`-related columns are checked for presence. It is possible to have orphaned records with
+    this approach. To avoid this problem, you need to use a foreign key.
 
-    Now `store_full_class_name` class attribute can handle both STI and polymorphic types.
+    This behavior can be controlled by configuration:
 
-    *Ryuta Kamizono*
+    ```ruby
+    config.active_record.belongs_to_required_validates_foreign_key = false
+    ```
 
-*   Deprecate `rails db:structure:{load, dump}` tasks and extend
-    `rails db:schema:{load, dump}` tasks to work with either `:ruby` or `:sql` format,
-    depending on `config.active_record.schema_format` configuration value.
+    and will be disabled by default with `config.load_defaults 7.1`.
 
     *fatkodima*
 
-*   Respect the `select` values for eager loading.
+*   `has_one` and `belongs_to` associations now define a `reset_association` method
+    on the owner model (where `association` is the name of the association). This
+    method unloads the cached associate record, if any, and causes the next access
+    to query it from the database.
 
-    ```ruby
-    post = Post.select("UPPER(title) AS title").first
-    post.title # => "WELCOME TO THE WEBLOG"
-    post.body  # => ActiveModel::MissingAttributeError
+    *George Claghorn*
 
-    # Rails 6.0 (ignore the `select` values)
-    post = Post.select("UPPER(title) AS title").eager_load(:comments).first
-    post.title # => "Welcome to the weblog"
-    post.body  # => "Such a lovely day"
+*   Allow per attribute setting of YAML permitted classes (safe load) and unsafe load.
 
-    # Rails 6.1 (respect the `select` values)
-    post = Post.select("UPPER(title) AS title").eager_load(:comments).first
-    post.title # => "WELCOME TO THE WEBLOG"
-    post.body  # => ActiveModel::MissingAttributeError
-    ```
+    *Carlos Palhares*
 
-    *Ryuta Kamizono*
+*   Add a build persistence method
+
+    Provides a wrapper for `new`, to provide feature parity with `create`s
+    ability to create multiple records from an array of hashes, using the
+    same notation as the `build` method on associations.
+
+    *Sean Denny*
 
-*   Allow attribute's default to be configured but keeping its own type.
+*   Raise on assignment to readonly attributes
 
     ```ruby
     class Post < ActiveRecord::Base
-      attribute :written_at, default: -> { Time.now.utc }
+      attr_readonly :content
     end
-
-    # Rails 6.0
-    Post.type_for_attribute(:written_at) # => #<Type::Value ... precision: nil, ...>
-
-    # Rails 6.1
-    Post.type_for_attribute(:written_at) # => #<Type::DateTime ... precision: 6, ...>
+    Post.create!(content: "cannot be updated")
+    post.content # "cannot be updated"
+    post.content = "something else" # => ActiveRecord::ReadonlyAttributeError
     ```
 
-    *Ryuta Kamizono*
+    Previously, assignment would succeed but silently not write to the database.
 
-*   Allow default to be configured for Enum.
+    This behavior can be controlled by configuration:
 
     ```ruby
-    class Book < ActiveRecord::Base
-      enum status: [:proposed, :written, :published], _default: :published
-    end
-
-    Book.new.status # => "published"
+    config.active_record.raise_on_assign_to_attr_readonly = true
     ```
 
-    *Ryuta Kamizono*
+    and will be enabled by default with `config.load_defaults 7.1`.
 
-*   Deprecate YAML loading from legacy format older than Rails 5.0.
+    *Alex Ghiculescu*, *Hartley McGuire*
 
-    *Ryuta Kamizono*
+*   Allow unscoping of preload and eager_load associations
 
-*   Added the setting `ActiveRecord::Base.immutable_strings_by_default`, which
-    allows you to specify that all string columns should be frozen unless
-    otherwise specified. This will reduce memory pressure for applications which
-    do not generally mutate string properties of Active Record objects.
+    Added the ability to unscope preload and eager_load associations just like
+    includes, joins, etc. See ActiveRecord::QueryMethods::VALID_UNSCOPING_VALUES
+    for the full list of supported unscopable scopes.
 
-    *Sean Griffin*, *Ryuta Kamizono*
+    ```ruby
+    query.unscope(:eager_load, :preload).group(:id).select(:id)
+    ```
 
-*   Deprecate `map!` and `collect!` on `ActiveRecord::Result`.
+    *David Morehouse*
 
-    *Ryuta Kamizono*
+*   Add automatic filtering of encrypted attributes on inspect
 
-*   Support `relation.and` for intersection as Set theory.
+    This feature is enabled by default but can be disabled with
 
     ```ruby
-    david_and_mary = Author.where(id: [david, mary])
-    mary_and_bob   = Author.where(id: [mary, bob])
-
-    david_and_mary.merge(mary_and_bob) # => [mary, bob]
-
-    david_and_mary.and(mary_and_bob) # => [mary]
-    david_and_mary.or(mary_and_bob)  # => [david, mary, bob]
+    config.active_record.encryption.add_to_filter_parameters = false
     ```
 
-    *Ryuta Kamizono*
-
-*   Merging conditions on the same column no longer maintain both conditions,
-    and will be consistently replaced by the latter condition in Rails 7.0.
-    To migrate to Rails 7.0's behavior, use `relation.merge(other, rewhere: true)`.
-
-    ```ruby
-    # Rails 6.1 (IN clause is replaced by merger side equality condition)
-    Author.where(id: [david.id, mary.id]).merge(Author.where(id: bob)) # => [bob]
+    *Hartley McGuire*
 
-    # Rails 6.1 (both conflict conditions exists, deprecated)
-    Author.where(id: david.id..mary.id).merge(Author.where(id: bob)) # => []
+*   Clear locking column on #dup
 
-    # Rails 6.1 with rewhere to migrate to Rails 7.0's behavior
-    Author.where(id: david.id..mary.id).merge(Author.where(id: bob), rewhere: true) # => [bob]
+    This change fixes not to duplicate locking_column like id and timestamps.
 
-    # Rails 7.0 (same behavior with IN clause, mergee side condition is consistently replaced)
-    Author.where(id: [david.id, mary.id]).merge(Author.where(id: bob)) # => [bob]
-    Author.where(id: david.id..mary.id).merge(Author.where(id: bob)) # => [bob]
+    ```
+    car = Car.create!
+    car.touch
+    car.lock_version #=> 1
+    car.dup.lock_version #=> 0
     ```
 
-    *Ryuta Kamizono*
+    *Shouichi Kamiya*, *Seonggi Yang*, *Ryohei UEDA*
 
-*   Do not mark Postgresql MAC address and UUID attributes as changed when the assigned value only varies by case.
+*   Invalidate transaction as early as possible
 
-    *Peter Fry*
+    After rescuing a `TransactionRollbackError` exception Rails invalidates transactions earlier in the flow
+    allowing the framework to skip issuing the `ROLLBACK` statement in more cases.
+    Only affects adapters that have `savepoint_errors_invalidate_transactions?` configured as `true`,
+    which at this point is only applicable to the `mysql2` adapter.
 
-*   Resolve issue with insert_all unique_by option when used with expression index.
+    *Nikita Vasilevsky*
 
-    When the `:unique_by` option of `ActiveRecord::Persistence.insert_all` and
-    `ActiveRecord::Persistence.upsert_all` was used with the name of an expression index, an error
-    was raised. Adding a guard around the formatting behavior for the `:unique_by` corrects this.
+*   Allow configuring columns list to be used in SQL queries issued by an `ActiveRecord::Base` object
 
-    Usage:
+    It is now possible to configure columns list that will be used to build an SQL query clauses when
+    updating, deleting or reloading an `ActiveRecord::Base` object
 
     ```ruby
-    create_table :books, id: :integer, force: true do |t|
-      t.column :name, :string
-      t.index "lower(name)", unique: true
+    class Developer < ActiveRecord::Base
+      query_constraints :company_id, :id
     end
-
-    Book.insert_all [{ name: "MyTest" }], unique_by: :index_books_on_lower_name
+    developer = Developer.first.update(name: "Bob")
+    # => UPDATE "developers" SET "name" = 'Bob' WHERE "developers"."company_id" = 1 AND "developers"."id" = 1
     ```
 
-    Fixes #39516.
+    *Nikita Vasilevsky*
 
-    *Austen Madden*
+*   Adds `validate` to foreign keys and check constraints in schema.rb
 
-*   Add basic support for CHECK constraints to database migrations.
+    Previously, `schema.rb` would not record if `validate: false` had been used when adding a foreign key or check
+    constraint, so restoring a database from the schema could result in foreign keys or check constraints being
+    incorrectly validated.
 
-    Usage:
+    *Tommy Graves*
 
-    ```ruby
-    add_check_constraint :products, "price > 0", name: "price_check"
-    remove_check_constraint :products, name: "price_check"
-    ```
+*   Adapter `#execute` methods now accept an `allow_retry` option. When set to `true`, the SQL statement will be
+    retried, up to the database's configured `connection_retries` value, upon encountering connection-related errors.
 
-    *fatkodima*
+    *Adrianna Chang*
 
-*   Add `ActiveRecord::Base.strict_loading_by_default` and `ActiveRecord::Base.strict_loading_by_default=`
-    to enable/disable strict_loading mode by default for a model. The configuration's value is
-    inheritable by subclasses, but they can override that value and it will not impact parent class.
+*   Only trigger `after_commit :destroy` callbacks when a database row is deleted.
 
-    Usage:
+    This prevents `after_commit :destroy` callbacks from being triggered again
+    when `destroy` is called multiple times on the same record.
 
-    ```ruby
-    class Developer < ApplicationRecord
-      self.strict_loading_by_default = true
+    *Ben Sheldon*
 
-      has_many :projects
-    end
+*   Fix `ciphertext_for` for yet-to-be-encrypted values.
 
-    dev = Developer.first
-    dev.projects.first
-    # => ActiveRecord::StrictLoadingViolationError Exception: Developer is marked as strict_loading and Project cannot be lazily loaded.
-    ```
+    Previously, `ciphertext_for` returned the cleartext of values that had not
+    yet been encrypted, such as with an unpersisted record:
 
-    *bogdanvlviv*
+      ```ruby
+      Post.encrypts :body
 
-*   Deprecate passing an Active Record object to `quote`/`type_cast` directly.
+      post = Post.create!(body: "Hello")
+      post.ciphertext_for(:body)
+      # => "{\"p\":\"abc..."
 
-    *Ryuta Kamizono*
+      post.body = "World"
+      post.ciphertext_for(:body)
+      # => "World"
+      ```
 
-*   Default engine `ENGINE=InnoDB` is no longer dumped to make schema more agnostic.
+    Now, `ciphertext_for` will always return the ciphertext of encrypted
+    attributes:
 
-    Before:
+      ```ruby
+      Post.encrypts :body
 
-    ```ruby
-    create_table "accounts", options: "ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci", force: :cascade do |t|
-    end
-    ```
+      post = Post.create!(body: "Hello")
+      post.ciphertext_for(:body)
+      # => "{\"p\":\"abc..."
 
-    After:
+      post.body = "World"
+      post.ciphertext_for(:body)
+      # => "{\"p\":\"xyz..."
+      ```
 
-    ```ruby
-    create_table "accounts", charset: "utf8mb4", collation: "utf8mb4_0900_ai_ci", force: :cascade do |t|
-    end
-    ```
+    *Jonathan Hefner*
 
-    *Ryuta Kamizono*
+*   Fix a bug where using groups and counts with long table names would return incorrect results.
 
-*   Added delegated type as an alternative to single-table inheritance for representing class hierarchies.
-    See ActiveRecord::DelegatedType for the full description.
+    *Shota Toguchi*, *Yusaku Ono*
 
-    *DHH*
+*   Fix encryption of column default values.
 
-*   Deprecate aggregations with group by duplicated fields.
+    Previously, encrypted attributes that used column default values appeared to
+    be encrypted on create, but were not:
 
-    To migrate to Rails 7.0's behavior, use `uniq!(:group)` to deduplicate group fields.
+      ```ruby
+      Book.encrypts :name
 
-    ```ruby
-    accounts = Account.group(:firm_id)
+      book = Book.create!
+      book.name
+      # => "<untitled>"
+      book.name_before_type_cast
+      # => "{\"p\":\"abc..."
+      book.reload.name_before_type_cast
+      # => "<untitled>"
+      ```
 
-    # duplicated group fields, deprecated.
-    accounts.merge(accounts.where.not(credit_limit: nil)).sum(:credit_limit)
-    # => {
-    #   [1, 1] => 50,
-    #   [2, 2] => 60
-    # }
+    Now, attributes with column default values are encrypted:
 
-    # use `uniq!(:group)` to deduplicate group fields.
-    accounts.merge(accounts.where.not(credit_limit: nil)).uniq!(:group).sum(:credit_limit)
-    # => {
-    #   1 => 50,
-    #   2 => 60
-    # }
-    ```
+      ```ruby
+      Book.encrypts :name
 
-    *Ryuta Kamizono*
+      book = Book.create!
+      book.name
+      # => "<untitled>"
+      book.name_before_type_cast
+      # => "{\"p\":\"abc..."
+      book.reload.name_before_type_cast
+      # => "{\"p\":\"abc..."
+      ```
 
-*   Deprecate duplicated query annotations.
+    *Jonathan Hefner*
 
-    To migrate to Rails 7.0's behavior, use `uniq!(:annotate)` to deduplicate query annotations.
+*   Deprecate delegation from `Base` to `connection_handler`.
 
-    ```ruby
-    accounts = Account.where(id: [1, 2]).annotate("david and mary")
+    Calling `Base.clear_all_connections!`, `Base.clear_active_connections!`, `Base.clear_reloadable_connections!` and `Base.flush_idle_connections!` is deprecated. Please call these methods on the connection handler directly. In future Rails versions, the delegation from `Base` to the `connection_handler` will be removed.
 
-    # duplicated annotations, deprecated.
-    accounts.merge(accounts.rewhere(id: 3))
-    # SELECT accounts.* FROM accounts WHERE accounts.id = 3 /* david and mary */ /* david and mary */
+    *Eileen M. Uchitelle*
 
-    # use `uniq!(:annotate)` to deduplicate annotations.
-    accounts.merge(accounts.rewhere(id: 3)).uniq!(:annotate)
-    # SELECT accounts.* FROM accounts WHERE accounts.id = 3 /* david and mary */
-    ```
+*   Allow ActiveRecord::QueryMethods#reselect to receive hash values, similar to ActiveRecord::QueryMethods#select
 
-    *Ryuta Kamizono*
+    *Sampat Badhe*
 
-*   Resolve conflict between counter cache and optimistic locking.
+*   Validate options when managing columns and tables in migrations.
 
-    Bump an Active Record instance's lock version after updating its counter
-    cache. This avoids raising an unnecessary `ActiveRecord::StaleObjectError`
-    upon subsequent transactions by maintaining parity with the corresponding
-    database record's `lock_version` column.
+    If an invalid option is passed to a migration method like `create_table` and `add_column`, an error will be raised
+    instead of the option being silently ignored. Validation of the options will only be applied for new migrations
+    that are created.
 
-    Fixes #16449.
+    *Guo Xiang Tan*, *George Wambold*
 
-    *Aaron Lipman*
+*   Update query log tags to use the [SQLCommenter](https://open-telemetry.github.io/opentelemetry-sqlcommenter/) format by default. See [#46179](https://github.com/rails/rails/issues/46179)
 
-*   Support merging option `:rewhere` to allow mergee side condition to be replaced exactly.
+    To opt out of SQLCommenter-formatted query log tags, set `config.active_record.query_log_tags_format = :legacy`. By default, this is set to `:sqlcommenter`.
 
-    ```ruby
-    david_and_mary = Author.where(id: david.id..mary.id)
+    *Modulitos* and *Iheanyi*
 
-    # both conflict conditions exists
-    david_and_mary.merge(Author.where(id: bob)) # => []
+*   Allow any ERB in the database.yml when creating rake tasks.
 
-    # mergee side condition is replaced by rewhere
-    david_and_mary.merge(Author.rewhere(id: bob)) # => [bob]
+    Any ERB can be used in `database.yml` even if it accesses environment
+    configurations.
 
-    # mergee side condition is replaced by rewhere option
-    david_and_mary.merge(Author.where(id: bob), rewhere: true) # => [bob]
-    ```
+    Deprecates `config.active_record.suppress_multiple_database_warning`.
 
-    *Ryuta Kamizono*
+    *Eike Send*
 
-*   Add support for finding records based on signed ids, which are tamper-proof, verified ids that can be
-    set to expire and scoped with a purpose. This is particularly useful for things like password reset
-    or email verification, where you want the bearer of the signed id to be able to interact with the
-    underlying record, but usually only within a certain time period.
+*   Add table to error for duplicate column definitions.
 
-    ```ruby
-    signed_id = User.first.signed_id expires_in: 15.minutes, purpose: :password_reset
+    If a migration defines duplicate columns for a table, the error message
+    shows which table it concerns.
 
-    User.find_signed signed_id # => nil, since the purpose does not match
+    *Petrik de Heus*
 
-    travel 16.minutes
-    User.find_signed signed_id, purpose: :password_reset # => nil, since the signed id has expired
+*   Fix erroneous nil default precision on virtual datetime columns.
 
-    travel_back
-    User.find_signed signed_id, purpose: :password_reset # => User.first
+    Prior to this change, virtual datetime columns did not have the same
+    default precision as regular datetime columns, resulting in the following
+    being erroneously equivalent:
 
-    User.find_signed! "bad data" # => ActiveSupport::MessageVerifier::InvalidSignature
-    ```
+        t.virtual :name, type: datetime,                 as: "expression"
+        t.virtual :name, type: datetime, precision: nil, as: "expression"
 
-    *DHH*
+    This change fixes the default precision lookup, so virtual and regular
+    datetime column default precisions match.
 
-*   Support `ALGORITHM = INSTANT` DDL option for index operations on MySQL.
+    *Sam Bostock*
 
-    *Ryuta Kamizono*
+*   Use connection from `#with_raw_connection` in `#quote_string`.
 
-*   Fix index creation to preserve index comment in bulk change table on MySQL.
+    This ensures that the string quoting is wrapped in the reconnect and retry logic
+    that `#with_raw_connection` offers.
 
-    *Ryuta Kamizono*
+    *Adrianna Chang*
 
-*   Allow `unscope` to be aware of table name qualified values.
+*   Add `expires_at` option to `signed_id`.
 
-    It is possible to unscope only the column in the specified table.
+    *Shouichi Kamiya*
 
-    ```ruby
-    posts = Post.joins(:comments).group(:"posts.hidden")
-    posts = posts.where("posts.hidden": false, "comments.hidden": false)
+*   Allow applications to set retry deadline for query retries.
 
-    posts.count
-    # => { false => 10 }
+    Building on the work done in #44576 and #44591, we extend the logic that automatically
+    reconnects database connections to take into account a timeout limit. We won't retry
+    a query if a given amount of time has elapsed since the query was first attempted. This
+    value defaults to nil, meaning that all retryable queries are retried regardless of time elapsed,
+    but this can be changed via the `retry_deadline` option in the database config.
 
-    # unscope both hidden columns
-    posts.unscope(where: :hidden).count
-    # => { false => 11, true => 1 }
+    *Adrianna Chang*
 
-    # unscope only comments.hidden column
-    posts.unscope(where: :"comments.hidden").count
-    # => { false => 11 }
-    ```
+*   Fix a case where the query cache can return wrong values. See #46044
 
-    *Ryuta Kamizono*, *Slava Korolev*
+    *Aaron Patterson*
 
-*   Fix `rewhere` to truly overwrite collided where clause by new where clause.
+*   Support MySQL's ssl-mode option for MySQLDatabaseTasks.
 
-    ```ruby
-    steve = Person.find_by(name: "Steve")
-    david = Author.find_by(name: "David")
+    Verifying the identity of the database server requires setting the ssl-mode
+    option to VERIFY_CA or VERIFY_IDENTITY. This option was previously ignored
+    for MySQL database tasks like creating a database and dumping the structure.
 
-    relation = Essay.where(writer: steve)
+    *Petrik de Heus*
 
-    # Before
-    relation.rewhere(writer: david).to_a # => []
+*   Move `ActiveRecord::InternalMetadata` to an independent object.
 
-    # After
-    relation.rewhere(writer: david).to_a # => [david]
-    ```
+    `ActiveRecord::InternalMetadata` no longer inherits from `ActiveRecord::Base` and is now an independent object that should be instantiated with a `connection`. This class is private and should not be used by applications directly. If you want to interact with the schema migrations table, please access it on the connection directly, for example: `ActiveRecord::Base.connection.schema_migration`.
 
-    *Ryuta Kamizono*
+    *Eileen M. Uchitelle*
 
-*   Inspect time attributes with subsec and time zone offset.
+*   Deprecate quoting `ActiveSupport::Duration` as an integer
 
-    ```ruby
-    p Knot.create
-    => #<Knot id: 1, created_at: "2016-05-05 01:29:47.116928000 +0000">
+    Using ActiveSupport::Duration as an interpolated bind parameter in a SQL
+    string template is deprecated. To avoid this warning, you should explicitly
+    convert the duration to a more specific database type. For example, if you
+    want to use a duration as an integer number of seconds:
+    ```
+    Record.where("duration = ?", 1.hour.to_i)
+    ```
+    If you want to use a duration as an ISO 8601 string:
+    ```
+    Record.where("duration = ?", 1.hour.iso8601)
     ```
 
-    *akinomaeni*, *Jonathan Hefner*
+    *Aram Greenman*
 
-*   Deprecate passing a column to `type_cast`.
+*   Allow `QueryMethods#in_order_of` to order by a string column name.
 
-    *Ryuta Kamizono*
+    ```ruby
+    Post.in_order_of("id", [4,2,3,1]).to_a
+    Post.joins(:author).in_order_of("authors.name", ["Bob", "Anna", "John"]).to_a
+    ```
 
-*   Deprecate `in_clause_length` and `allowed_index_name_length` in `DatabaseLimits`.
+    *Igor Kasyanchuk*
 
-    *Ryuta Kamizono*
+*   Move `ActiveRecord::SchemaMigration` to an independent object.
 
-*   Support bulk insert/upsert on relation to preserve scope values.
+    `ActiveRecord::SchemaMigration` no longer inherits from `ActiveRecord::Base` and is now an independent object that should be instantiated with a `connection`. This class is private and should not be used by applications directly. If you want to interact with the schema migrations table, please access it on the connection directly, for example: `ActiveRecord::Base.connection.schema_migration`.
 
-    *Josef Šimánek*, *Ryuta Kamizono*
+    *Eileen M. Uchitelle*
+
+*   Deprecate `all_connection_pools` and make `connection_pool_list` more explicit.
 
-*   Preserve column comment value on changing column name on MySQL.
+    Following on #45924 `all_connection_pools` is now deprecated. `connection_pool_list` will either take an explicit role or applications can opt into the new behavior by passing `:all`.
 
-    *Islam Taha*
+    *Eileen M. Uchitelle*
 
-*   Add support for `if_exists` option for removing an index.
+*   Fix connection handler methods to operate on all pools.
 
-    The `remove_index` method can take an `if_exists` option. If this is set to true an error won't be raised if the index doesn't exist.
+    `active_connections?`, `clear_active_connections!`, `clear_reloadable_connections!`, `clear_all_connections!`, and `flush_idle_connections!` now operate on all pools by default. Previously they would default to using the `current_role` or `:writing` role unless specified.
 
     *Eileen M. Uchitelle*
 
-*   Remove ibm_db, informix, mssql, oracle, and oracle12 Arel visitors which are not used in the code base.
 
-    *Ryuta Kamizono*
+*   Allow ActiveRecord::QueryMethods#select to receive hash values.
 
-*   Prevent `build_association` from `touching` a parent record if the record isn't persisted for `has_one` associations.
+    Currently, `select` might receive only raw sql and symbols to define columns and aliases to select.
 
-    Fixes #38219.
+    With this change we can provide `hash` as argument, for example:
 
-    *Josh Brody*
+    ```ruby
+    Post.joins(:comments).select(posts: [:id, :title, :created_at], comments: [:id, :body, :author_id])
+    #=> "SELECT \"posts\".\"id\", \"posts\".\"title\", \"posts\".\"created_at\", \"comments\".\"id\", \"comments\".\"body\", \"comments\".\"author_id\"
+    #   FROM \"posts\" INNER JOIN \"comments\" ON \"comments\".\"post_id\" = \"posts\".\"id\""
 
-*   Add support for `if_not_exists` option for adding index.
+    Post.joins(:comments).select(posts: { id: :post_id, title: :post_title }, comments: { id: :comment_id, body: :comment_body })
+    #=> "SELECT posts.id as post_id, posts.title as post_title, comments.id as comment_id, comments.body as comment_body
+    #    FROM \"posts\" INNER JOIN \"comments\" ON \"comments\".\"post_id\" = \"posts\".\"id\""
+    ```
+    *Oleksandr Holubenko*, *Josef Šimánek*, *Jean Boussier*
 
-    The `add_index` method respects `if_not_exists` option. If it is set to true
-    index won't be added.
+*   Adapts virtual attributes on `ActiveRecord::Persistence#becomes`.
 
-    Usage:
+    When source and target classes have a different set of attributes adapts
+    attributes such that the extra attributes from target are added.
 
     ```ruby
-      add_index :users, :account_id, if_not_exists: true
-    ```
+    class Person < ApplicationRecord
+    end
 
-    The `if_not_exists` option passed to `create_table` also gets propagated to indexes
-    created within that migration so that if table and its indexes exist then there is no
-    attempt to create them again.
+    class WebUser < Person
+      attribute :is_admin, :boolean
+      after_initialize :set_admin
 
-    *Prathamesh Sonpatki*
+      def set_admin
+        write_attribute(:is_admin, email =~ /@ourcompany\.com$/)
+      end
+    end
 
-*   Add `ActiveRecord::Base#previously_new_record?` to show if a record was new before the last save.
+    person = Person.find_by(email: "email@ourcompany.com")
+    person.respond_to? :is_admin
+    # => false
+    person.becomes(WebUser).is_admin?
+    # => true
+    ```
 
-    *Tom Ward*
+    *Jacopo Beschi*, *Sampson Crowley*
 
-*   Support descending order for `find_each`, `find_in_batches`, and `in_batches`.
+*   Fix `ActiveRecord::QueryMethods#in_order_of` to include `nil`s, to match the
+    behavior of `Enumerable#in_order_of`.
 
-    Batch processing methods allow you to work with the records in batches, greatly reducing memory consumption, but records are always batched from oldest id to newest.
+    For example, `Post.in_order_of(:title, [nil, "foo"])` will now include posts
+    with `nil` titles, the same as `Post.all.to_a.in_order_of(:title, [nil, "foo"])`.
 
-    This change allows reversing the order, batching from newest to oldest. This is useful when you need to process newer batches of records first.
+    *fatkodima*
 
-    Pass `order: :desc` to yield batches in descending order. The default remains `order: :asc`.
+*   Optimize `add_timestamps` to use a single SQL statement.
 
     ```ruby
-    Person.find_each(order: :desc) do |person|
-      person.party_all_night!
-    end
+    add_timestamps :my_table
     ```
 
-    *Alexey Vasiliev*
-
-*   Fix `insert_all` with enum values.
+    Now results in the following SQL:
 
-    Fixes #38716.
-
-    *Joel Blum*
+    ```sql
+    ALTER TABLE "my_table" ADD COLUMN "created_at" datetime(6) NOT NULL, ADD COLUMN "updated_at" datetime(6) NOT NULL
+    ```
 
-*   Add support for `db:rollback:name` for multiple database applications.
+    *Iliana Hadzhiatanasova*
 
-    Multiple database applications will now raise if `db:rollback` is call and recommend using the `db:rollback:[NAME]` to rollback migrations.
+*   Add `drop_enum` migration command for PostgreSQL
 
-    *Eileen M. Uchitelle*
+    This does the inverse of `create_enum`. Before dropping an enum, ensure you have
+    dropped columns that depend on it.
 
-*   `Relation#pick` now uses already loaded results instead of making another query.
+    *Alex Ghiculescu*
 
-    *Eugene Kenny*
+*   Adds support for `if_exists` option when removing a check constraint.
 
-*   Deprecate using `return`, `break` or `throw` to exit a transaction block after writes.
+    The `remove_check_constraint` method now accepts an `if_exists` option. If set
+    to true an error won't be raised if the check constraint doesn't exist.
 
-    *Dylan Thacker-Smith*
+    *Margaret Parsa* and *Aditya Bhutani*
 
-*   Dump the schema or structure of a database when calling `db:migrate:name`.
+*   `find_or_create_by` now try to find a second time if it hits a unicity constraint.
 
-    In previous versions of Rails, `rails db:migrate` would dump the schema of the database. In Rails 6, that holds true (`rails db:migrate` dumps all databases' schemas), but `rails db:migrate:name` does not share that behavior.
+    `find_or_create_by` always has been inherently racy, either creating multiple
+    duplicate records or failing with `ActiveRecord::RecordNotUnique` depending on
+    whether a proper unicity constraint was set.
 
-    Going forward, calls to `rails db:migrate:name` will dump the schema (or structure) of the database being migrated.
+    `create_or_find_by` was introduced for this use case, however it's quite wasteful
+    when the record is expected to exist most of the time, as INSERT require to send
+    more data than SELECT and require more work from the database. Also on some
+    databases it can actually consume a primary key increment which is undesirable.
 
-    *Kyle Thompson*
+    So for case where most of the time the record is expected to exist, `find_or_create_by`
+    can be made race-condition free by re-trying the `find` if the `create` failed
+    with `ActiveRecord::RecordNotUnique`. This assumes that the table has the proper
+    unicity constraints, if not, `find_or_create_by` will still lead to duplicated records.
 
-*   Reset the `ActiveRecord::Base` connection after `rails db:migrate:name`.
+    *Jean Boussier*, *Alex Kitchens*
 
-    When `rails db:migrate` has finished, it ensures the `ActiveRecord::Base` connection is reset to its original configuration. Going forward, `rails db:migrate:name` will have the same behavior.
+*   Introduce a simpler constructor API for ActiveRecord database adapters.
 
-    *Kyle Thompson*
+    Previously the adapter had to know how to build a new raw connection to
+    support reconnect, but also expected to be passed an initial already-
+    established connection.
 
-*   Disallow calling `connected_to` on subclasses of `ActiveRecord::Base`.
+    When manually creating an adapter instance, it will now accept a single
+    config hash, and only establish the real connection on demand.
 
-    Behavior has not changed here but the previous API could be misleading to people who thought it would switch connections for only that class. `connected_to` switches the context from which we are getting connections, not the connections themselves.
+    *Matthew Draper*
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+*   Avoid redundant `SELECT 1` connection-validation query during DB pool
+    checkout when possible.
 
-*   Add support for horizontal sharding to `connects_to` and `connected_to`.
+    If the first query run during a request is known to be idempotent, it can be
+    used directly to validate the connection, saving a network round-trip.
 
-    Applications can now connect to multiple shards and switch between their shards in an application. Note that the shard swapping is still a manual process as this change does not include an API for automatic shard swapping.
+    *Matthew Draper*
 
-    Usage:
+*   Automatically reconnect broken database connections when safe, even
+    mid-request.
 
-    Given the following configuration:
+    When an error occurs while attempting to run a known-idempotent query, and
+    not inside a transaction, it is safe to immediately reconnect to the
+    database server and try again, so this is now the default behavior.
 
-    ```yaml
-    # config/database.yml
-    production:
-      primary:
-        database: my_database
-      primary_shard_one:
-        database: my_database_shard_one
-    ```
+    This new default should always be safe -- to support that, it's consciously
+    conservative about which queries are considered idempotent -- but if
+    necessary it can be disabled by setting the `connection_retries` connection
+    option to `0`.
 
-    Connect to multiple shards:
+    *Matthew Draper*
 
-    ```ruby
-    class ApplicationRecord < ActiveRecord::Base
-      self.abstract_class = true
+*   Avoid removing a PostgreSQL extension when there are dependent objects.
 
-      connects_to shards: {
-        default: { writing: :primary },
-        shard_one: { writing: :primary_shard_one }
-      }
-    ```
+    Previously, removing an extension also implicitly removed dependent objects. Now, this will raise an error.
 
-    Swap between shards in your controller / model code:
+    You can force removing the extension:
 
     ```ruby
-    ActiveRecord::Base.connected_to(shard: :shard_one) do
-      # Read from shard one
-    end
+    disable_extension :citext, force: :cascade
     ```
 
-    The horizontal sharding API also supports read replicas. See guides for more details.
+    Fixes #29091.
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+    *fatkodima*
 
-*   Deprecate `spec_name` in favor of `name` on database configurations.
+*   Allow nested functions as safe SQL string
 
-    The accessors for `spec_name` on `configs_for` and `DatabaseConfig` are deprecated. Please use `name` instead.
+    *Michael Siegfried*
 
-    Deprecated behavior:
+*   Allow `destroy_association_async_job=` to be configured with a class string instead of a constant.
 
-    ```ruby
-    db_config = ActiveRecord::Base.configurations.configs_for(env_name: "development", spec_name: "primary")
-    db_config.spec_name
-    ```
+    Defers an autoloading dependency between `ActiveRecord::Base` and `ActiveJob::Base`
+    and moves the configuration of `ActiveRecord::DestroyAssociationAsyncJob`
+    from ActiveJob to ActiveRecord.
 
-    New behavior:
+    Deprecates `ActiveRecord::ActiveJobRequiredError` and now raises a `NameError`
+    if the job class is unloadable or an `ActiveRecord::ConfigurationError` if
+    `dependent: :destroy_async` is declared on an association but there is no job
+    class configured.
 
-    ```ruby
-    db_config = ActiveRecord::Base.configurations.configs_for(env_name: "development", name: "primary")
-    db_config.name
-    ```
+    *Ben Sheldon*
 
-    *Eileen M. Uchitelle*
+*   Fix `ActiveRecord::Store` to serialize as a regular Hash
+
+    Previously it would serialize as an `ActiveSupport::HashWithIndifferentAccess`
+    which is wasteful and cause problem with YAML safe_load.
 
-*   Add additional database-specific rake tasks for multi-database users.
+    *Jean Boussier*
 
-    Previously, `rails db:create`, `rails db:drop`, and `rails db:migrate` were the only rails tasks that could operate on a single
-    database. For example:
+*   Add `timestamptz` as a time zone aware type for PostgreSQL
 
-    ```
-    rails db:create
-    rails db:create:primary
-    rails db:create:animals
-    rails db:drop
-    rails db:drop:primary
-    rails db:drop:animals
-    rails db:migrate
-    rails db:migrate:primary
-    rails db:migrate:animals
-    ```
+    This is required for correctly parsing `timestamp with time zone` values in your database.
 
-    With these changes, `rails db:schema:dump`, `rails db:schema:load`, `rails db:structure:dump`, `rails db:structure:load` and
-    `rails db:test:prepare` can additionally operate on a single database. For example:
+    If you don't want this, you can opt out by adding this initializer:
 
-    ```
-    rails db:schema:dump
-    rails db:schema:dump:primary
-    rails db:schema:dump:animals
-    rails db:schema:load
-    rails db:schema:load:primary
-    rails db:schema:load:animals
-    rails db:structure:dump
-    rails db:structure:dump:primary
-    rails db:structure:dump:animals
-    rails db:structure:load
-    rails db:structure:load:primary
-    rails db:structure:load:animals
-    rails db:test:prepare
-    rails db:test:prepare:primary
-    rails db:test:prepare:animals
+    ```ruby
+    ActiveRecord::Base.time_zone_aware_types -= [:timestamptz]
     ```
 
-    *Kyle Thompson*
+    *Alex Ghiculescu*
 
-*   Add support for `strict_loading` mode on association declarations.
+*   Add new `ActiveRecord::Base.generates_token_for` API.
 
-    Raise an error if attempting to load a record from an association that has been marked as `strict_loading` unless it was explicitly eager loaded.
+    Currently, `signed_id` fulfills the role of generating tokens for e.g.
+    resetting a password.  However, signed IDs cannot reflect record state, so
+    if a token is intended to be single-use, it must be tracked in a database at
+    least until it expires.
 
-    Usage:
+    With `generates_token_for`, a token can embed data from a record.  When
+    using the token to fetch the record, the data from the token and the current
+    data from the record will be compared.  If the two do not match, the token
+    will be treated as invalid, the same as if it had expired.  For example:
 
     ```ruby
-    class Developer < ApplicationRecord
-      has_many :projects, strict_loading: true
+    class User < ActiveRecord::Base
+      has_secure_password
+
+      generates_token_for :password_reset, expires_in: 15.minutes do
+        # A password's BCrypt salt changes when the password is updated.
+        # By embedding (part of) the salt in a token, the token will
+        # expire when the password is updated.
+        BCrypt::Password.new(password_digest).salt[-10..]
+      end
     end
 
-    dev = Developer.first
-    dev.projects.first
-    # => ActiveRecord::StrictLoadingViolationError: The projects association is marked as strict_loading and cannot be lazily loaded.
+    user = User.first
+    token = user.generate_token_for(:password_reset)
+
+    User.find_by_token_for(:password_reset, token) # => user
+
+    user.update!(password: "new password")
+    User.find_by_token_for(:password_reset, token) # => nil
     ```
 
-    *Kevin Deisz*
+    *Jonathan Hefner*
 
-*   Add support for `strict_loading` mode to prevent lazy loading of records.
+*   Optimize Active Record batching for whole table iterations.
 
-    Raise an error if a parent record is marked as `strict_loading` and attempts to lazily load its associations. This is useful for finding places you may want to preload an association and avoid additional queries.
+    Previously, `in_batches` got all the ids and constructed an `IN`-based query for each batch.
+    When iterating over the whole tables, this approach is not optimal as it loads unneeded ids and
+    `IN` queries with lots of items are slow.
 
-    Usage:
+    Now, whole table iterations use range iteration (`id >= x AND id <= y`) by default which can make iteration
+    several times faster. E.g., tested on a PostgreSQL table with 10 million records: querying (`253s` vs `30s`),
+    updating (`288s` vs `124s`), deleting (`268s` vs `83s`).
+
+    Only whole table iterations use this style of iteration by default. You can disable this behavior by passing `use_ranges: false`.
+    If you iterate over the table and the only condition is, e.g., `archived_at: nil` (and only a tiny fraction
+    of the records are archived), it makes sense to opt in to this approach:
 
     ```ruby
-    dev = Developer.strict_loading.first
-    dev.audit_logs.to_a
-    # => ActiveRecord::StrictLoadingViolationError: Developer is marked as strict_loading and AuditLog cannot be lazily loaded.
+    Project.where(archived_at: nil).in_batches(use_ranges: true) do |relation|
+      # do something
+    end
     ```
 
-    *Eileen M. Uchitelle*, *Aaron Patterson*
+    See #45414 for more details.
 
-*   Add support for PostgreSQL 11+ partitioned indexes when using `upsert_all`.
+    *fatkodima*
 
-    *Sebastián Palma*
+*   `.with` query method added. Construct common table expressions with ease and get `ActiveRecord::Relation` back.
 
-*   Adds support for `if_not_exists` to `add_column` and `if_exists` to `remove_column`.
+    ```ruby
+    Post.with(posts_with_comments: Post.where("comments_count > ?", 0))
+    # => ActiveRecord::Relation
+    # WITH posts_with_comments AS (SELECT * FROM posts WHERE (comments_count > 0)) SELECT * FROM posts
+    ```
 
-    Applications can set their migrations to ignore exceptions raised when adding a column that already exists or when removing a column that does not exist.
+    *Vlado Cingel*
 
-    Example Usage:
+*   Don't establish a new connection if an identical pool exists already.
 
-    ```ruby
-    class AddColumnTitle < ActiveRecord::Migration[6.1]
-      def change
-        add_column :posts, :title, :string, if_not_exists: true
-      end
-    end
-    ```
+    Previously, if `establish_connection` was called on a class that already had an established connection, the existing connection would be removed regardless of whether it was the same config. Now if a pool is found with the same values as the new connection, the existing connection will be returned instead of creating a new one.
 
-    ```ruby
-    class RemoveColumnTitle < ActiveRecord::Migration[6.1]
-      def change
-        remove_column :posts, :title, if_exists: true
-      end
-    end
-    ```
+    This has a slight change in behavior if application code is depending on a new connection being established regardless of whether it's identical to an existing connection. If the old behavior is desirable, applications should call `ActiveRecord::Base#remove_connection` before establishing a new one. Calling `establish_connection` with a different config works the same way as it did previously.
 
     *Eileen M. Uchitelle*
 
-*   Regexp-escape table name for MS SQL Server.
+*   Update `db:prepare` task to load schema when an uninitialized database exists, and dump schema after migrations.
 
-    Add `Regexp.escape` to one method in ActiveRecord, so that table names with regular expression characters in them work as expected. Since MS SQL Server uses "[" and "]" to quote table and column names, and those characters are regular expression characters, methods like `pluck` and `select` fail in certain cases when used with the MS SQL Server adapter.
+    *Ben Sheldon*
 
-    *Larry Reid*
+*   Fix supporting timezone awareness for `tsrange` and `tstzrange` array columns.
 
-*   Store advisory locks on their own named connection.
+    ```ruby
+    # In database migrations
+    add_column :shops, :open_hours, :tsrange, array: true
+    # In app config
+    ActiveRecord::Base.time_zone_aware_types += [:tsrange]
+    # In the code times are properly converted to app time zone
+    Shop.create!(open_hours: [Time.current..8.hour.from_now])
+    ```
 
-    Previously advisory locks were taken out against a connection when a migration started. This works fine in single database applications but doesn't work well when migrations need to open new connections which results in the lock getting dropped.
+    *Wojciech Wnętrzak*
 
-    In order to fix this we are storing the advisory lock on a new connection with the connection specification name `AdvisoryLockBase`. The caveat is that we need to maintain at least 2 connections to a database while migrations are running in order to do this.
+*   Introduce strategy pattern for executing migrations.
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+    By default, migrations will use a strategy object that delegates the method
+    to the connection adapter. Consumers can implement custom strategy objects
+    to change how their migrations run.
 
-*   Allow schema cache path to be defined in the database configuration file.
+    *Adrianna Chang*
 
-    For example:
+*   Add adapter option disallowing foreign keys
+
+    This adds a new option to be added to `database.yml` which enables skipping
+    foreign key constraints usage even if the underlying database supports them.
 
+    Usage:
     ```yaml
     development:
-      adapter: postgresql
-      database: blog_development
-      pool: 5
-      schema_cache_path: tmp/schema/main.yml
+        <<: *default
+        database: storage/development.sqlite3
+        foreign_keys: false
     ```
 
-    *Katrina Owen*
+    *Paulo Barros*
 
-*   Deprecate `#remove_connection` in favor of `#remove_connection_pool` when called on the handler.
+*   Add configurable deprecation warning for singular associations
 
-    `#remove_connection` is deprecated in order to support returning a `DatabaseConfig` object instead of a `Hash`. Use `#remove_connection_pool`, `#remove_connection` will be removed in Rails 7.0.
+    This adds a deprecation warning when using the plural name of a singular associations in `where`.
+    It is possible to opt into the new more performant behavior with `config.active_record.allow_deprecated_singular_associations_name = false`
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+    *Adam Hess*
 
-*   Deprecate `#default_hash` and it's alias `#[]` on database configurations.
+*   Run transactional callbacks on the freshest instance to save a given
+    record within a transaction.
 
-    Applications should use `configs_for`. `#default_hash` and `#[]` will be removed in Rails 7.0.
+    When multiple Active Record instances change the same record within a
+    transaction, Rails runs `after_commit` or `after_rollback` callbacks for
+    only one of them. `config.active_record.run_commit_callbacks_on_first_saved_instances_in_transaction`
+    was added to specify how Rails chooses which instance receives the
+    callbacks. The framework defaults were changed to use the new logic.
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+    When `config.active_record.run_commit_callbacks_on_first_saved_instances_in_transaction`
+    is `true`, transactional callbacks are run on the first instance to save,
+    even though its instance state may be stale.
 
-*   Add scale support to `ActiveRecord::Validations::NumericalityValidator`.
+    When it is `false`, which is the new framework default starting with version
+    7.1, transactional callbacks are run on the instances with the freshest
+    instance state. Those instances are chosen as follows:
 
-    *Gannon McGibbon*
+    - In general, run transactional callbacks on the last instance to save a
+      given record within the transaction.
+    - There are two exceptions:
+        - If the record is created within the transaction, then updated by
+          another instance, `after_create_commit` callbacks will be run on the
+          second instance. This is instead of the `after_update_commit`
+          callbacks that would naively be run based on that instance’s state.
+        - If the record is destroyed within the transaction, then
+          `after_destroy_commit` callbacks will be fired on the last destroyed
+          instance, even if a stale instance subsequently performed an update
+          (which will have affected 0 rows).
 
-*   Find orphans by looking for missing relations through chaining `where.missing`:
+    *Cameron Bothner and Mitch Vollebregt*
 
-    Before:
+*   Enable strict strings mode for `SQLite3Adapter`.
+
+    Configures SQLite with a strict strings mode, which disables double-quoted string literals.
+
+    SQLite has some quirks around double-quoted string literals.
+    It first tries to consider double-quoted strings as identifier names, but if they don't exist
+    it then considers them as string literals. Because of this, typos can silently go unnoticed.
+    For example, it is possible to create an index for a non existing column.
+    See [SQLite documentation](https://www.sqlite.org/quirks.html#double_quoted_string_literals_are_accepted) for more details.
+
+    If you don't want this behavior, you can disable it via:
 
     ```ruby
-    Post.left_joins(:author).where(authors: { id: nil })
+    # config/application.rb
+    config.active_record.sqlite3_adapter_strict_strings_by_default = false
     ```
 
-    After:
+    Fixes #27782.
+
+    *fatkodima*, *Jean Boussier*
+
+*   Resolve issue where a relation cache_version could be left stale.
+
+    Previously, when `reset` was called on a relation object it did not reset the cache_versions
+    ivar. This led to a confusing situation where despite having the correct data the relation
+    still reported a stale cache_version.
+
+    Usage:
 
     ```ruby
-    Post.where.missing(:author)
+    developers = Developer.all
+    developers.cache_version
+
+    Developer.update_all(updated_at: Time.now.utc + 1.second)
+
+    developers.cache_version # Stale cache_version
+    developers.reset
+    developers.cache_version # Returns the current correct cache_version
     ```
 
-    *Tom Rossi*
+    Fixes #45341.
 
-*   Ensure `:reading` connections always raise if a write is attempted.
+    *Austen Madden*
 
-    Now Rails will raise an `ActiveRecord::ReadOnlyError` if any connection on the reading handler attempts to make a write. If your reading role needs to write you should name the role something other than `:reading`.
+*   Add support for exclusion constraints (PostgreSQL-only).
 
-    *Eileen M. Uchitelle*
+    ```ruby
+    add_exclusion_constraint :invoices, "daterange(start_date, end_date) WITH &&", using: :gist, name: "invoices_date_overlap"
+    remove_exclusion_constraint :invoices, name: "invoices_date_overlap"
+    ```
 
-*   Deprecate `"primary"` as the `connection_specification_name` for `ActiveRecord::Base`.
+    See PostgreSQL's [`CREATE TABLE ... EXCLUDE ...`](https://www.postgresql.org/docs/12/sql-createtable.html#SQL-CREATETABLE-EXCLUDE) documentation for more on exclusion constraints.
 
-    `"primary"` has been deprecated as the `connection_specification_name` for `ActiveRecord::Base` in favor of using `"ActiveRecord::Base"`. This change affects calls to `ActiveRecord::Base.connection_handler.retrieve_connection` and `ActiveRecord::Base.connection_handler.remove_connection`. If you're calling these methods with `"primary"`, please switch to `"ActiveRecord::Base"`.
+    *Alex Robbin*
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+*   `change_column_null` raises if a non-boolean argument is provided
 
-*   Add `ActiveRecord::Validations::NumericalityValidator` with
-    support for casting floats using a database columns' precision value.
+    Previously if you provided a non-boolean argument, `change_column_null` would
+    treat it as truthy and make your column nullable. This could be surprising, so now
+    the input must be either `true` or `false`.
 
-    *Gannon McGibbon*
+    ```ruby
+    change_column_null :table, :column, true # good
+    change_column_null :table, :column, false # good
+    change_column_null :table, :column, from: true, to: false # raises (previously this made the column nullable)
+    ```
+
+    *Alex Ghiculescu*
 
-*   Enforce fresh ETag header after a collection's contents change by adding
-    ActiveRecord::Relation#cache_key_with_version. This method will be used by
-    ActionController::ConditionalGet to ensure that when collection cache versioning
-    is enabled, requests using ConditionalGet don't return the same ETag header
-    after a collection is modified.
+*   Enforce limit on table names length.
 
-    Fixes #38078.
+    Fixes #45130.
 
-    *Aaron Lipman*
+    *fatkodima*
 
-*   Skip test database when running `db:create` or `db:drop` in development
-    with `DATABASE_URL` set.
+*   Adjust the minimum MariaDB version for check constraints support.
 
-    *Brian Buchalter*
+    *Eddie Lebow*
 
-*   Don't allow mutations on the database configurations hash.
+*   Fix Hstore deserialize regression.
 
-    Freeze the configurations hash to disallow directly changing it. If applications need to change the hash, for example to create databases for parallelization, they should use the `DatabaseConfig` object directly.
+    *edsharp*
 
-    Before:
+*   Add validity for PostgreSQL indexes.
 
     ```ruby
-    @db_config = ActiveRecord::Base.configurations.configs_for(env_name: "test", spec_name: "primary")
-    @db_config.configuration_hash.merge!(idle_timeout: "0.02")
+    connection.index_exists?(:users, :email, valid: true)
+    connection.indexes(:users).select(&:valid?)
     ```
 
-    After:
+    *fatkodima*
+
+*   Fix eager loading for models without primary keys.
+
+    *Anmol Chopra*, *Matt Lawrence*, and *Jonathan Hefner*
+
+*   Avoid validating a unique field if it has not changed and is backed by a unique index.
+
+    Previously, when saving a record, Active Record will perform an extra query to check for the
+    uniqueness of each attribute having a `uniqueness` validation, even if that attribute hasn't changed.
+    If the database has the corresponding unique index, then this validation can never fail for persisted
+    records, and we could safely skip it.
+
+    *fatkodima*
+
+*   Stop setting `sql_auto_is_null`
+
+    Since version 5.5 the default has been off, we no longer have to manually turn it off.
+
+    *Adam Hess*
+
+*   Fix `touch` to raise an error for readonly columns.
+
+    *fatkodima*
+
+*   Add ability to ignore tables by regexp for SQL schema dumps.
 
     ```ruby
-    @db_config = ActiveRecord::Base.configurations.configs_for(env_name: "test", spec_name: "primary")
-    config = @db_config.configuration_hash.merge(idle_timeout: "0.02")
-    db_config = ActiveRecord::DatabaseConfigurations::HashConfig.new(@db_config.env_name, @db_config.spec_name, config)
+    ActiveRecord::SchemaDumper.ignore_tables = [/^_/]
     ```
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
-
-*   Remove `:connection_id` from the `sql.active_record` notification.
+    *fatkodima*
 
-    *Aaron Patterson*, *Rafael Mendonça França*
+*   Avoid queries when performing calculations on contradictory relations.
 
-*   The `:name` key will no longer be returned as part of `DatabaseConfig#configuration_hash`. Please use `DatabaseConfig#owner_name` instead.
+    Previously calculations would make a query even when passed a
+    contradiction, such as `User.where(id: []).count`. We no longer perform a
+    query in that scenario.
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+    This applies to the following calculations: `count`, `sum`, `average`,
+    `minimum` and `maximum`
 
-*   ActiveRecord's `belongs_to_required_by_default` flag can now be set per model.
+    *Luan Vieira, John Hawthorn and Daniel Colson*
 
-    You can now opt-out/opt-in specific models from having their associations required
-    by default.
+*   Allow using aliased attributes with `insert_all`/`upsert_all`.
 
-    This change is meant to ease the process of migrating all your models to have
-    their association required.
+    ```ruby
+    class Book < ApplicationRecord
+      alias_attribute :title, :name
+    end
 
-    *Edouard Chin*
+    Book.insert_all [{ title: "Remote", author_id: 1 }], returning: :title
+    ```
 
-*   The `connection_config` method has been deprecated, please use `connection_db_config` instead which will return a `DatabaseConfigurations::DatabaseConfig` instead of a `Hash`.
+    *fatkodima*
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+*   Support encrypted attributes on columns with default db values.
 
-*   Retain explicit selections on the base model after applying `includes` and `joins`.
+    This adds support for encrypted attributes defined on columns with default values.
+    It will encrypt those values at creation time. Before, it would raise an
+    error unless `config.active_record.encryption.support_unencrypted_data` was true.
 
-    Resolves #34889.
+    *Jorge Manrubia* and *Dima Fatko*
 
-    *Patrick Rebsch*
+*   Allow overriding `reading_request?` in `DatabaseSelector::Resolver`
 
-*   The `database` kwarg is deprecated without replacement because it can't be used for sharding and creates an issue if it's used during a request. Applications that need to create new connections should use `connects_to` instead.
+    The default implementation checks if a request is a `get?` or `head?`,
+    but you can now change it to anything you like. If the method returns true,
+    `Resolver#read` gets called meaning the request could be served by the
+    replica database.
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+    *Alex Ghiculescu*
 
-*   Allow attributes to be fetched from Arel node groupings.
+*   Remove `ActiveRecord.legacy_connection_handling`.
 
-    *Jeff Emminger*, *Gannon McGibbon*
+    *Eileen M. Uchitelle*
 
-*   A database URL can now contain a querystring value that contains an equal sign. This is needed to support passing PostgreSQL `options`.
+*   `rails db:schema:{dump,load}` now checks `ENV["SCHEMA_FORMAT"]` before config
 
-    *Joshua Flanagan*
+    Since `rails db:structure:{dump,load}` was deprecated there wasn't a simple
+    way to dump a schema to both SQL and Ruby formats. You can now do this with
+    an environment variable. For example:
 
-*   Calling methods like `establish_connection` with a `Hash` which is invalid (eg: no `adapter`) will now raise an error the same way as connections defined in `config/database.yml`.
+    ```
+    SCHEMA_FORMAT=sql rake db:schema:dump
+    ```
 
-    *John Crepezzi*
+    *Alex Ghiculescu*
 
-*   Specifying `implicit_order_column` now subsorts the records by primary key if available to ensure deterministic results.
+*   Fixed MariaDB default function support.
 
-    *Paweł Urbanek*
+    Defaults would be written wrong in "db/schema.rb" and not work correctly
+    if using `db:schema:load`. Further more the function name would be
+    added as string content when saving new records.
 
-*   `where(attr => [])` now loads an empty result without making a query.
+    *kaspernj*
 
-    *John Hawthorn*
+*   Add `active_record.destroy_association_async_batch_size` configuration
 
-*   Fixed the performance regression for `primary_keys` introduced MySQL 8.0.
+    This allows applications to specify the maximum number of records that will
+    be destroyed in a single background job by the `dependent: :destroy_async`
+    association option. By default, the current behavior will remain the same:
+    when a parent record is destroyed, all dependent records will be destroyed
+    in a single background job. If the number of dependent records is greater
+    than this configuration, the records will be destroyed in multiple
+    background jobs.
 
-    *Hiroyuki Ishii*
+    *Nick Holden*
 
-*   Add support for `belongs_to` to `has_many` inversing.
+*   Fix `remove_foreign_key` with `:if_exists` option when foreign key actually exists.
 
-    *Gannon McGibbon*
+    *fatkodima*
 
-*   Allow length configuration for `has_secure_token` method. The minimum length
-    is set at 24 characters.
+*   Remove `--no-comments` flag in structure dumps for PostgreSQL
 
-    Before:
+    This broke some apps that used custom schema comments. If you don't want
+    comments in your structure dump, you can use:
 
     ```ruby
-    has_secure_token :auth_token
+    ActiveRecord::Tasks::DatabaseTasks.structure_dump_flags = ['--no-comments']
     ```
 
-    After:
+    *Alex Ghiculescu*
 
-    ```ruby
-    has_secure_token :default_token             # 24 characters
-    has_secure_token :auth_token, length: 36    # 36 characters
-    has_secure_token :invalid_token, length: 12 # => ActiveRecord::SecureToken::MinimumLengthError
-    ```
+*   Reduce the memory footprint of fixtures accessors.
 
-    *Bernardo de Araujo*
+    Until now fixtures accessors were eagerly defined using `define_method`.
+    So the memory usage was directly dependent of the number of fixtures and
+    test suites.
 
-*   Deprecate `DatabaseConfigurations#to_h`. These connection hashes are still available via `ActiveRecord::Base.configurations.configs_for`.
+    Instead fixtures accessors are now implemented with `method_missing`,
+    so they incur much less memory and CPU overhead.
 
-    *Eileen Uchitelle*, *John Crepezzi*
+    *Jean Boussier*
 
-*   Add `DatabaseConfig#configuration_hash` to return database configuration hashes with symbol keys, and use all symbol-key configuration hashes internally. Deprecate `DatabaseConfig#config` which returns a String-keyed `Hash` with the same values.
+*   Fix `config.active_record.destroy_association_async_job` configuration
 
-    *John Crepezzi*, *Eileen Uchitelle*
+    `config.active_record.destroy_association_async_job` should allow
+    applications to specify the job that will be used to destroy associated
+    records in the background for `has_many` associations with the
+    `dependent: :destroy_async` option. Previously, that was ignored, which
+    meant the default `ActiveRecord::DestroyAssociationAsyncJob` always
+    destroyed records in the background.
 
-*   Allow column names to be passed to `remove_index` positionally along with other options.
+    *Nick Holden*
 
-    Passing other options can be necessary to make `remove_index` correctly reversible.
+*   Fix `change_column_comment` to preserve column's AUTO_INCREMENT in the MySQL adapter
 
-    Before:
+    *fatkodima*
 
-        add_index    :reports, :report_id               # => works
-        add_index    :reports, :report_id, unique: true # => works
-        remove_index :reports, :report_id               # => works
-        remove_index :reports, :report_id, unique: true # => ArgumentError
+*   Fix quoting of `ActiveSupport::Duration` and `Rational` numbers in the MySQL adapter.
 
-    After:
+    *Kevin McPhillips*
 
-        remove_index :reports, :report_id, unique: true # => works
+*   Allow column name with COLLATE (e.g., title COLLATE "C") as safe SQL string
 
-    *Eugene Kenny*
+    *Shugo Maeda*
 
-*   Allow bulk `ALTER` statements to drop and recreate indexes with the same name.
+*   Permit underscores in the VERSION argument to database rake tasks.
 
-    *Eugene Kenny*
+    *Eddie Lebow*
 
-*   `insert`, `insert_all`, `upsert`, and `upsert_all` now clear the query cache.
+*   Reversed the order of `INSERT` statements in `structure.sql` dumps
 
-    *Eugene Kenny*
+    This should decrease the likelihood of merge conflicts. New migrations
+    will now be added at the top of the list.
 
-*   Call `while_preventing_writes` directly from `connected_to`.
+    For existing apps, there will be a large diff the next time `structure.sql`
+    is generated.
 
-    In some cases application authors want to use the database switching middleware and make explicit calls with `connected_to`. It's possible for an app to turn off writes and not turn them back on by the time we call `connected_to(role: :writing)`.
+    *Alex Ghiculescu*, *Matt Larraz*
 
-    This change allows apps to fix this by assuming if a role is writing we want to allow writes, except in the case it's explicitly turned off.
+*   Fix PG.connect keyword arguments deprecation warning on ruby 2.7
 
-    *Eileen M. Uchitelle*
+    Fixes #44307.
+
+    *Nikita Vasilevsky*
 
-*   Improve detection of ActiveRecord::StatementTimeout with mysql2 adapter in the edge case when the query is terminated during filesort.
+*   Fix dropping DB connections after serialization failures and deadlocks.
 
-    *Kir Shatrov*
+    Prior to 6.1.4, serialization failures and deadlocks caused rollbacks to be
+    issued for both real transactions and savepoints. This breaks MySQL which
+    disallows rollbacks of savepoints following a deadlock.
 
-*   Stop trying to read yaml file fixtures when loading Active Record fixtures.
+    6.1.4 removed these rollbacks, for both transactions and savepoints, causing
+    the DB connection to be left in an unknown state and thus discarded.
 
-    *Gannon McGibbon*
+    These rollbacks are now restored, except for savepoints on MySQL.
 
-*   Deprecate `.reorder(nil)` with `.first` / `.first!` taking non-deterministic result.
+    *Thomas Morgan*
 
-    To continue taking non-deterministic result, use `.take` / `.take!` instead.
+*   Make `ActiveRecord::ConnectionPool` Fiber-safe
 
-    *Ryuta Kamizono*
+    When `ActiveSupport::IsolatedExecutionState.isolation_level` is set to `:fiber`,
+    the connection pool now supports multiple Fibers from the same Thread checking
+    out connections from the pool.
 
-*   Preserve user supplied joins order as much as possible.
+    *Alex Matchneer*
 
-    Fixes #36761, #34328, #24281, #12953.
+*   Add `update_attribute!` to `ActiveRecord::Persistence`
 
-    *Ryuta Kamizono*
+    Similar to `update_attribute`, but raises `ActiveRecord::RecordNotSaved` when a `before_*` callback throws `:abort`.
 
-*   Allow `matches_regex` and `does_not_match_regexp` on the MySQL Arel visitor.
+    ```ruby
+    class Topic < ActiveRecord::Base
+      before_save :check_title
 
-    *James Pearson*
+      def check_title
+        throw(:abort) if title == "abort"
+      end
+    end
 
-*   Allow specifying fixtures to be ignored by setting `ignore` in YAML file's '_fixture' section.
+    topic = Topic.create(title: "Test Title")
+    # #=> #<Topic title: "Test Title">
+    topic.update_attribute!(:title, "Another Title")
+    # #=> #<Topic title: "Another Title">
+    topic.update_attribute!(:title, "abort")
+    # raises ActiveRecord::RecordNotSaved
+    ```
 
-    *Tongfei Gao*
+    *Drew Tempelmeyer*
 
-*   Make the DATABASE_URL env variable only affect the primary connection. Add new env variables for multiple databases.
+*   Avoid loading every record in `ActiveRecord::Relation#pretty_print`
 
-    *John Crepezzi*, *Eileen Uchitelle*
+    ```ruby
+    # Before
+    pp Foo.all # Loads the whole table.
 
-*   Add a warning for enum elements with 'not_' prefix.
+    # After
+    pp Foo.all # Shows 10 items and an ellipsis.
+    ```
 
-        class Foo
-          enum status: [:sent, :not_sent]
-        end
+    *Ulysse Buonomo*
 
-    *Edu Depetris*
+*   Change `QueryMethods#in_order_of` to drop records not listed in values.
 
-*   Make currency symbols optional for money column type in PostgreSQL.
+    `in_order_of` now filters down to the values provided, to match the behavior of the `Enumerable` version.
 
-    *Joel Schneider*
+    *Kevin Newton*
 
-*   Add support for beginless ranges, introduced in Ruby 2.7.
+*   Allow named expression indexes to be revertible.
 
-    *Josh Goodall*
+    Previously, the following code would raise an error in a reversible migration executed while rolling back, due to the index name not being used in the index removal.
 
-*   Add `database_exists?` method to connection adapters to check if a database exists.
+    ```ruby
+    add_index(:settings, "(data->'property')", using: :gin, name: :index_settings_data_property)
+    ```
 
-    *Guilherme Mansur*
+    Fixes #43331.
 
-*   Loading the schema for a model that has no `table_name` raises a `TableNotSpecified` error.
+    *Oliver Günther*
 
-    *Guilherme Mansur*, *Eugene Kenny*
+*   Fix incorrect argument in PostgreSQL structure dump tasks.
 
-*   PostgreSQL: Fix GROUP BY with ORDER BY virtual count attribute.
+    Updating the `--no-comment` argument added in Rails 7 to the correct `--no-comments` argument.
 
-    Fixes #36022.
+    *Alex Dent*
 
-    *Ryuta Kamizono*
+*   Fix migration compatibility to create SQLite references/belongs_to column as integer when migration version is 6.0.
 
-*   Make ActiveRecord `ConnectionPool.connections` method thread-safe.
+    Reference/belongs_to in migrations with version 6.0 were creating columns as
+    bigint instead of integer for the SQLite Adapter.
+
+    *Marcelo Lauxen*
+
+*   Fix `QueryMethods#in_order_of` to handle empty order list.
 
-    Fixes #36465.
+    ```ruby
+    Post.in_order_of(:id, []).to_a
+    ```
 
-    *Jeff Doering*
+    Also more explicitly set the column as secondary order, so that any other
+    value is still ordered.
+
+    *Jean Boussier*
 
-*   Add support for multiple databases to `rails db:abort_if_pending_migrations`.
+*   Fix quoting of column aliases generated by calculation methods.
 
-    *Mark Lee*
+    Since the alias is derived from the table name, we can't assume the result
+    is a valid identifier.
 
-*   Fix sqlite3 collation parsing when using decimal columns.
+    ```ruby
+    class Test < ActiveRecord::Base
+      self.table_name = '1abc'
+    end
+    Test.group(:id).count
+    # syntax error at or near "1" (ActiveRecord::StatementInvalid)
+    # LINE 1: SELECT COUNT(*) AS count_all, "1abc"."id" AS 1abc_id FROM "1...
+    ```
 
-    *Martin R. Schuster*
+    *Jean Boussier*
 
-*   Fix invalid schema when primary key column has a comment.
+*   Add `authenticate_by` when using `has_secure_password`.
 
-    Fixes #29966.
+    `authenticate_by` is intended to replace code like the following, which
+    returns early when a user with a matching email is not found:
 
-    *Guilherme Goettems Schneider*
+    ```ruby
+    User.find_by(email: "...")&.authenticate("...")
+    ```
 
-*   Fix table comment also being applied to the primary key column.
+    Such code is vulnerable to timing-based enumeration attacks, wherein an
+    attacker can determine if a user account with a given email exists. After
+    confirming that an account exists, the attacker can try passwords associated
+    with that email address from other leaked databases, in case the user
+    re-used a password across multiple sites (a common practice). Additionally,
+    knowing an account email address allows the attacker to attempt a targeted
+    phishing ("spear phishing") attack.
 
-    *Guilherme Goettems Schneider*
+    `authenticate_by` addresses the vulnerability by taking the same amount of
+    time regardless of whether a user with a matching email is found:
 
-*   Allow generated `create_table` migrations to include or skip timestamps.
+    ```ruby
+    User.authenticate_by(email: "...", password: "...")
+    ```
 
-    *Michael Duchemin*
+    *Jonathan Hefner*
 
 
-Please check [6-0-stable](https://github.com/rails/rails/blob/6-0-stable/activerecord/CHANGELOG.md) for previous changes.
+Please check [7-0-stable](https://github.com/rails/rails/blob/7-0-stable/activerecord/CHANGELOG.md) for previous changes.