activerecord 7.0.0 → 7.2.1

data/CHANGELOG.md

@@ -1,1697 +1,944 @@
-## Rails 7.0.0 (December 15, 2021) ##
+## Rails 7.2.1 (August 22, 2024) ##
 
-*   Better handle SQL queries with invalid encoding.
-
-    ```ruby
-    Post.create(name: "broken \xC8 UTF-8")
-    ```
-
-    Would cause all adapters to fail in a non controlled way in the code
-    responsible to detect write queries.
-
-    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.
-
-    *Jean Boussier*
-
-*   Move database and shard selection config options to a generator.
-
-    Rather than generating the config options in `production.rb` when applications are created, applications can now run a generator to create an initializer and uncomment / update options as needed. All multi-db configuration can be implemented in this initializer.
-
-    *Eileen M. Uchitelle*
-
-## Rails 7.0.0.rc3 (December 14, 2021) ##
-
-*   No changes.
-
-
-## Rails 7.0.0.rc2 (December 14, 2021) ##
-
-*   No changes.
-
-## Rails 7.0.0.rc1 (December 06, 2021) ##
-
-*   Remove deprecated `ActiveRecord::DatabaseConfigurations::DatabaseConfig#spec_name`.
-
-    *Rafael Mendonça França*
-
-*   Remove deprecated `ActiveRecord::Connection#in_clause_length`.
-
-    *Rafael Mendonça França*
-
-*   Remove deprecated `ActiveRecord::Connection#allowed_index_name_length`.
+*   Fix detection for `enum` columns with parallelized tests and PostgreSQL.
 
     *Rafael Mendonça França*
 
-*   Remove deprecated `ActiveRecord::Base#remove_connection`.
-
-    *Rafael Mendonça França*
-
-*   Load STI Models in fixtures
-
-    Data from Fixtures now loads based on the specific class for models with
-    Single Table Inheritance. This affects enums defined in subclasses, previously
-    the value of these fields was not parsed and remained `nil`
-
-    *Andres Howard*
-
-*   `#authenticate` returns false when the password is blank instead of raising an error.
-
-    *Muhammad Muhammad Ibrahim*
+*   Allow to eager load nested nil associations.
 
-*   Fix `ActiveRecord::QueryMethods#in_order_of` behavior for integer enums.
-
-    `ActiveRecord::QueryMethods#in_order_of` didn't work as expected for enums stored as integers in the database when passing an array of strings or symbols as the order argument. This unexpected behavior occurred because the string or symbol values were not casted to match the integers in the database.
-
-    The following example now works as expected:
-
-    ```ruby
-    class Book < ApplicationRecord
-      enum status: [:proposed, :written, :published]
-    end
-
-    Book.in_order_of(:status, %w[written published proposed])
-    ```
-
-    *Alexandre Ruban*
-
-*   Ignore persisted in-memory records when merging target lists.
-
-    *Kevin Sjöberg*
-
-*   Add a new option `:update_only` to `upsert_all` to configure the list of columns to update in case of conflict.
-
-    Before, you could only customize the update SQL sentence via `:on_duplicate`. There is now a new option `:update_only` that lets you provide a list of columns to update in case of conflict:
-
-    ```ruby
-    Commodity.upsert_all(
-      [
-        { id: 2, name: "Copper", price: 4.84 },
-        { id: 4, name: "Gold", price: 1380.87 },
-        { id: 6, name: "Aluminium", price: 0.35 }
-      ],
-      update_only: [:price] # Only prices will be updated
-    )
-    ```
+    *fatkodima*
 
-    *Jorge Manrubia*
+*   Fix swallowing ignore order warning when batching using `BatchEnumerator`.
 
-*   Remove deprecated `ActiveRecord::Result#map!` and `ActiveRecord::Result#collect!`.
+    *fatkodima*
 
-    *Rafael Mendonça França*
+*   Fix memory bloat on the connection pool when using the Fiber `IsolatedExecutionState`.
 
-*   Remove deprecated `ActiveRecord::Base.configurations.to_h`.
+    *Jean Boussier*
 
-    *Rafael Mendonça França*
+*   Restore inferred association class with the same modularized name.
 
-*   Remove deprecated `ActiveRecord::Base.configurations.default_hash`.
+    *Justin Ko*
 
-    *Rafael Mendonça França*
+*   Fix `ActiveRecord::Base.inspect` to properly explain how to load schema information.
 
-*   Remove deprecated `ActiveRecord::Base.arel_attribute`.
+    *Jean Boussier*
 
-    *Rafael Mendonça França*
+*   Check invalid `enum` options for the new syntax.
 
-*   Remove deprecated `ActiveRecord::Base.connection_config`.
+    The options using `_` prefix in the old syntax are invalid in the new syntax.
 
     *Rafael Mendonça França*
 
-*   Filter attributes in SQL logs
-
-    Previously, SQL queries in logs containing `ActiveRecord::Base.filter_attributes` were not filtered.
-
-    Now, the filter attributes will be masked `[FILTERED]` in the logs when `prepared_statement` is enabled.
+*   Fix `ActiveRecord::Encryption::EncryptedAttributeType#type` to return
+    actual cast type.
 
-    ```
-    # Before:
-      Foo Load (0.2ms)  SELECT "foos".* FROM "foos" WHERE "foos"."passw" = ? LIMIT ?  [["passw", "hello"], ["LIMIT", 1]]
-
-    # After:
-      Foo Load (0.5ms)  SELECT "foos".* FROM "foos" WHERE "foos"."passw" = ? LIMIT ?  [["passw", "[FILTERED]"], ["LIMIT", 1]]
-    ```
+    *Vasiliy Ermolovich*
 
-    *Aishwarya Subramanian*
+*   Fix `create_table` with `:auto_increment` option for MySQL adapter.
 
-*   Remove deprecated `Tasks::DatabaseTasks.spec`.
-
-    *Rafael Mendonça França*
+    *fatkodima*
 
-*   Remove deprecated `Tasks::DatabaseTasks.current_config`.
 
-    *Rafael Mendonça França*
+## Rails 7.2.0 (August 09, 2024) ##
 
-*   Deprecate `Tasks::DatabaseTasks.schema_file_type`.
+*   Handle commas in Sqlite3 default function definitions.
 
-    *Rafael Mendonça França*
+    *Stephen Margheim*
 
-*   Remove deprecated `Tasks::DatabaseTasks.dump_filename`.
+*   Fixes `validates_associated` raising an exception when configured with a
+    singular association and having `index_nested_attribute_errors` enabled.
 
-    *Rafael Mendonça França*
+    *Martin Spickermann*
 
-*   Remove deprecated `Tasks::DatabaseTasks.schema_file`.
+*   The constant `ActiveRecord::ImmutableRelation` has been deprecated because
+    we want to reserve that name for a stronger sense of "immutable relation".
+    Please use `ActiveRecord::UnmodifiableRelation` instead.
 
-    *Rafael Mendonça França*
+    *Xavier Noria*
 
-*   Remove deprecated `environment` and `name` arguments from `Tasks::DatabaseTasks.schema_up_to_date?`.
+*   Add condensed `#inspect` for `ConnectionPool`, `AbstractAdapter`, and
+    `DatabaseConfig`.
 
-    *Rafael Mendonça França*
+    *Hartley McGuire*
 
-*   Merging conditions on the same column no longer maintain both conditions,
-    and will be consistently replaced by the latter condition.
+*   Fixed a memory performance issue in Active Record attribute methods definition.
 
-    ```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]
-    # Rails 6.1 (both conflict conditions exists, deprecated)
-    Author.where(id: david.id..mary.id).merge(Author.where(id: bob)) # => []
-    # 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]
-    # 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]
+    *Jean Boussier*
 
-    *Rafael Mendonça França*
+*   Define the new Active Support notification event `start_transaction.active_record`.
 
-*   Remove deprecated support to `Model.reorder(nil).first` to search using non-deterministic order.
+    This event is fired when database transactions or savepoints start, and
+    complements `transaction.active_record`, which is emitted when they finish.
 
-    *Rafael Mendonça França*
+    The payload has the transaction (`:transaction`) and the connection (`:connection`).
 
-*   Remove deprecated rake tasks:
+    *Xavier Noria*
 
-    * `db:schema:load_if_ruby`
-    * `db:structure:dump`
-    * `db:structure:load`
-    * `db:structure:load_if_sql`
-    * `db:structure:dump:#{name}`
-    * `db:structure:load:#{name}`
-    * `db:test:load_structure`
-    * `db:test:load_structure:#{name}`
+*   Fix an issue where the IDs reader method did not return expected results
+    for preloaded associations in models using composite primary keys.
 
-    *Rafael Mendonça França*
+    *Jay Ang*
 
-*   Remove deprecated `DatabaseConfig#config` method.
+*   The payload of `sql.active_record` Active Support notifications now has the current transaction in the `:transaction` key.
 
-    *Rafael Mendonça França*
+    *Xavier Noria*
 
-*   Rollback transactions when the block returns earlier than expected.
+*   The payload of `transaction.active_record` Active Support notifications now has the transaction the event is related to in the `:transaction` key.
 
-    Before this change, when a transaction block returned early, the transaction would be committed.
+    *Xavier Noria*
 
-    The problem is that timeouts triggered inside the transaction block was also making the incomplete transaction
-    to be committed, so in order to avoid this mistake, the transaction block is rolled back.
+*   Define `ActiveRecord::Transaction#uuid`, which returns a UUID for the database transaction. This may be helpful when tracing database activity. These UUIDs are generated only on demand.
 
-    *Rafael Mendonça França*
+    *Xavier Noria*
 
-*   Add middleware for automatic shard swapping.
+*   Fix inference of association model on nested models with the same demodularized name.
 
-    Provides a basic middleware to perform automatic shard swapping. Applications will provide a resolver which will determine for an individual request which shard should be used. Example:
+    E.g. with the following setup:
 
     ```ruby
-    config.active_record.shard_resolver = ->(request) {
-      subdomain = request.subdomain
-      tenant = Tenant.find_by_subdomain!(subdomain)
-      tenant.shard
-    }
+    class Nested::Post < ApplicationRecord
+      has_one :post, through: :other
+    end
     ```
 
-    See guides for more details.
-
-    *Eileen M. Uchitelle*, *John Crepezzi*
-
-*   Remove deprecated support to pass a column to `type_cast`.
-
-    *Rafael Mendonça França*
-
-*   Remove deprecated support to type cast to database values `ActiveRecord::Base` objects.
-
-    *Rafael Mendonça França*
+    Before, `#post` would infer the model as `Nested::Post`, but now it correctly infers `Post`.
 
-*   Remove deprecated support to quote `ActiveRecord::Base` objects.
+    *Joshua Young*
 
-    *Rafael Mendonça França*
+*   PostgreSQL `Cidr#change?` detects the address prefix change.
 
-*   Remove deprecacated support to resolve connection using `"primary"` as connection specification name.
+    *Taketo Takashima*
 
-    *Rafael Mendonça França*
+*   Change `BatchEnumerator#destroy_all` to return the total number of affected rows.
 
-*   Remove deprecation warning when using `:interval` column is used in PostgreSQL database.
+    Previously, it always returned `nil`.
 
-    Now, interval columns will return `ActiveSupport::Duration` objects instead of strings.
+    *fatkodima*
 
-    To keep the old behavior, you can add this line to your model:
+*   Support `touch_all` in batches.
 
     ```ruby
-    attribute :column, :string
+    Post.in_batches.touch_all
     ```
 
-    *Rafael Mendonça França*
+    *fatkodima*
 
-*   Remove deprecated support to YAML load `ActiveRecord::Base` instance in the Rails 4.2 and 4.1 formats.
+*   Add support for `:if_not_exists` and `:force` options to `create_schema`.
 
-    *Rafael Mendonça França*
+    *fatkodima*
 
-*   Remove deprecated option `:spec_name` in the `configs_for` method.
+*   Fix `index_errors` having incorrect index in association validation errors.
 
-    *Rafael Mendonça França*
+    *lulalala*
 
-*   Remove deprecated  `ActiveRecord::Base.allow_unsafe_raw_sql`.
+*   Add `index_errors: :nested_attributes_order` mode.
 
-    *Rafael Mendonça França*
+    This indexes the association validation errors based on the order received by nested attributes setter, and respects the `reject_if` configuration. This enables API to provide enough information to the frontend to map the validation errors back to their respective form fields.
 
-*   Fix regression bug that caused ignoring additional conditions for preloading has_many-through relations.
+    *lulalala*
 
-    Fixes #43132
+*   Add `Rails.application.config.active_record.postgresql_adapter_decode_dates` to opt out of decoding dates automatically with the postgresql adapter. Defaults to true.
 
-    *Alexander Pauly*
+    *Joé Dupuis*
 
-*   Fix `has_many` inversing recursion on models with recursive associations.
+*   Association option `query_constraints` is deprecated in favor of `foreign_key`.
 
-    *Gannon McGibbon*
+    *Nikita Vasilevsky*
 
-*   Add `accepts_nested_attributes_for` support for `delegated_type`
+*   Add `ENV["SKIP_TEST_DATABASE_TRUNCATE"]` flag to speed up multi-process test runs on large DBs when all tests run within default transaction.
 
-    ```ruby
-    class Entry < ApplicationRecord
-      delegated_type :entryable, types: %w[ Message Comment ]
-      accepts_nested_attributes_for :entryable
-    end
+    This cuts ~10s from the test run of HEY when run by 24 processes against the 178 tables, since ~4,000 table truncates can then be skipped.
 
-    entry = Entry.create(entryable_type: 'Message', entryable_attributes: { content: 'Hello world' })
-    # => #<Entry:0x00>
-    # id: 1
-    # entryable_id: 1,
-    # entryable_type: 'Message'
-    # ...>
-
-    entry.entryable
-    # => #<Message:0x01>
-    # id: 1
-    # content: 'Hello world'
-    # ...>
-    ```
+    *DHH*
 
-    Previously it would raise an error:
+*   Added support for recursive common table expressions.
 
     ```ruby
-    Entry.create(entryable_type: 'Message', entryable_attributes: { content: 'Hello world' })
-    # ArgumentError: Cannot build association `entryable'. Are you trying to build a polymorphic one-to-one association?
-    ```
-
-    *Sjors Baltus*
-
-*   Use subquery for DELETE with GROUP_BY and HAVING clauses.
-
-    Prior to this change, deletes with GROUP_BY and HAVING were returning an error.
-
-    After this change, GROUP_BY and HAVING are valid clauses in DELETE queries, generating the following query:
-
-    ```sql
-    DELETE FROM "posts" WHERE "posts"."id" IN (
-        SELECT "posts"."id" FROM "posts" INNER JOIN "comments" ON "comments"."post_id" = "posts"."id" GROUP BY "posts"."id" HAVING (count(comments.id) >= 2))
-    )  [["flagged", "t"]]
-    ```
-
-    *Ignacio Chiazzo Cardarello*
-
-*   Use subquery for UPDATE with GROUP_BY and HAVING clauses.
-
-    Prior to this change, updates with GROUP_BY and HAVING were being ignored, generating a SQL like this:
-
-    ```sql
-    UPDATE "posts" SET "flagged" = ? WHERE "posts"."id" IN (
-        SELECT "posts"."id" FROM "posts" INNER JOIN "comments" ON "comments"."post_id" = "posts"."id"
-    )  [["flagged", "t"]]
+    Post.with_recursive(
+      post_and_replies: [
+        Post.where(id: 42),
+        Post.joins('JOIN post_and_replies ON posts.in_reply_to_id = post_and_replies.id'),
+      ]
+    )
     ```
 
-    After this change, GROUP_BY and HAVING clauses are used as a subquery in updates, like this:
+    Generates the following SQL:
 
     ```sql
-    UPDATE "posts" SET "flagged" = ? WHERE "posts"."id" IN (
-        SELECT "posts"."id" FROM "posts" INNER JOIN "comments" ON "comments"."post_id" = "posts"."id"
-        GROUP BY posts.id HAVING (count(comments.id) >= 2)
-    )  [["flagged", "t"]]
-    ```
-
-    *Ignacio Chiazzo Cardarello*
-
-*   Add support for setting the filename of the schema or structure dump in the database config.
-
-    Applications may now set their the filename or path of the schema / structure dump file in their database configuration.
-
-    ```yaml
-    production:
-      primary:
-        database: my_db
-        schema_dump: my_schema_dump_filename.rb
-      animals:
-        database: animals_db
-        schema_dump: false
+    WITH RECURSIVE "post_and_replies" AS (
+      (SELECT "posts".* FROM "posts" WHERE "posts"."id" = 42)
+      UNION ALL
+      (SELECT "posts".* FROM "posts" JOIN post_and_replies ON posts.in_reply_to_id = post_and_replies.id)
+    )
+    SELECT "posts".* FROM "posts"
     ```
 
-    The filename set in `schema_dump` will be used by the application. If set to `false` the schema will not be dumped. The database tasks are responsible for adding the database directory to the filename. If a full path is provided, the Rails tasks will use that instead of `ActiveRecord::DatabaseTasks.db_dir`.
-
-    *Eileen M. Uchitelle*, *Ryan Kerr*
-
-*   Add `ActiveRecord::Base.prohibit_shard_swapping` to prevent attempts to change the shard within a block.
+    *ClearlyClaire*
 
-    *John Crepezzi*, *Eileen M. Uchitelle*
-
-*   Filter unchanged attributes with default function from insert query when `partial_inserts` is disabled.
-
-    *Akshay Birajdar*, *Jacopo Beschi*
-
-*   Add support for FILTER clause (SQL:2003) to Arel.
-
-    Currently supported by PostgreSQL 9.4+ and SQLite 3.30+.
-
-    *Andrey Novikov*
-
-*   Automatically set timestamps on record creation during bulk insert/upsert
-
-    Prior to this change, only updates during an upsert operation (e.g. `upsert_all`) would touch timestamps (`updated_{at,on}`). Now, record creations also touch timestamp columns (`{created,updated}_{at,on}`).
-
-    This behaviour is controlled by the `<model>.record_timestamps` config, matching the behaviour of `create`, `update`, etc. It can also be overridden by using the `record_timestamps:` keyword argument.
-
-    Note that this means `upsert_all` on models with `record_timestamps = false` will no longer touch `updated_{at,on}` automatically.
-
-    *Sam Bostock*
-
-*   Don't require `role` when passing `shard` to `connected_to`.
-
-    `connected_to` can now be called with a `shard` only. Note that `role` is still inherited if `connected_to` calls are nested.
-
-    *Eileen M. Uchitelle*
-
-*   Add option to lazily load the schema cache on the connection.
-
-    Previously, the only way to load the schema cache in Active Record was through the Railtie on boot. This option provides the ability to load the schema cache on the connection after it's been established. Loading the cache lazily on the connection can be beneficial for Rails applications that use multiple databases because it will load the cache at the time the connection is established. Currently Railties doesn't have access to the connections before boot.
-
-    To use the cache, set `config.active_record.lazily_load_schema_cache = true` in your application configuration. In addition a `schema_cache_path` should be set in your database configuration if you don't want to use the default "db/schema_cache.yml" path.
-
-    *Eileen M. Uchitelle*
-
-*   Allow automatic `inverse_of` detection for associations with scopes.
-
-    Automatic `inverse_of` detection now works for associations with scopes. For
-    example, the `comments` association here now automatically detects
-    `inverse_of: :post`, so we don't need to pass that option:
+*   `validate_constraint` can be called in a `change_table` block.
 
+    ex:
     ```ruby
-    class Post < ActiveRecord::Base
-      has_many :comments, -> { visible }
-    end
-
-    class Comment < ActiveRecord::Base
-      belongs_to :post
+    change_table :products do |t|
+      t.check_constraint "price > discounted_price", name: "price_check", validate: false
+      t.validate_check_constraint "price_check"
     end
     ```
 
-    Note that the automatic detection still won't work if the inverse
-    association has a scope. In this example a scope on the `post` association
-    would still prevent Rails from finding the inverse for the `comments`
-    association.
+    *Cody Cutrer*
 
-    This will be the default for new apps in Rails 7. To opt in:
+*   `PostgreSQLAdapter` now decodes columns of type date to `Date` instead of string.
 
+    Ex:
     ```ruby
-    config.active_record.automatic_scope_inversing = true
+    ActiveRecord::Base.connection
+         .select_value("select '2024-01-01'::date").class #=> Date
     ```
 
-    *Daniel Colson*, *Chris Bloom*
-
-*   Accept optional transaction args to `ActiveRecord::Locking::Pessimistic#with_lock`
+    *Joé Dupuis*
 
-    `#with_lock` now accepts transaction options like `requires_new:`,
-    `isolation:`, and `joinable:`
+*   Strict loading using `:n_plus_one_only` does not eagerly load child associations.
 
-    *John Mileham*
+    With this change, child associations are no longer eagerly loaded, to
+    match intended behavior and to prevent non-deterministic order issues caused
+    by calling methods like `first` or `last`. As `first` and `last` don't cause
+    an N+1 by themselves, calling child associations will no longer raise.
+    Fixes #49473.
 
-*   Adds support for deferrable foreign key constraints in PostgreSQL.
-
-    By default, foreign key constraints in PostgreSQL are checked after each statement. This works for most use cases,
-    but becomes a major limitation when creating related records before the parent record is inserted into the database.
-    One example of this is looking up / creating a person via one or more unique alias.
+    Before:
 
     ```ruby
-    Person.transaction do
-      alias = Alias
-        .create_with(user_id: SecureRandom.uuid)
-        .create_or_find_by(name: "DHH")
-
-      person = Person
-        .create_with(name: "David Heinemeier Hansson")
-        .create_or_find_by(id: alias.user_id)
-    end
+    person = Person.find(1)
+    person.strict_loading!(mode: :n_plus_one_only)
+    person.posts.first
+    # SELECT * FROM posts WHERE person_id = 1; -- non-deterministic order
+    person.posts.first.firm # raises ActiveRecord::StrictLoadingViolationError
     ```
 
-    Using the default behavior, the transaction would fail when executing the first `INSERT` statement.
-
-    By passing the `:deferrable` option to the `add_foreign_key` statement in migrations, it's possible to defer this
-    check.
+    After:
 
     ```ruby
-    add_foreign_key :aliases, :person, deferrable: true
+    person = Person.find(1)
+    person.strict_loading!(mode: :n_plus_one_only)
+    person.posts.first # this is 1+1, not N+1
+    # SELECT * FROM posts WHERE person_id = 1 ORDER BY id LIMIT 1;
+    person.posts.first.firm # no longer raises
     ```
 
-    Passing `deferrable: true` doesn't change the default behavior, but allows manually deferring the check using
-    `SET CONSTRAINTS ALL DEFERRED` within a transaction. This will cause the foreign keys to be checked after the
-    transaction.
-
-    It's also possible to adjust the default behavior from an immediate check (after the statement), to a deferred check
-    (after the transaction):
+    *Reid Lynch*
 
-    ```ruby
-    add_foreign_key :aliases, :person, deferrable: :deferred
-    ```
+*   Allow `Sqlite3Adapter` to use `sqlite3` gem version `2.x`.
 
-    *Benedikt Deicke*
+    *Mike Dalessio*
 
-*   Allow configuring Postgres password through the socket URL.
+*   Allow `ActiveRecord::Base#pluck` to accept hash values.
 
-    For example:
     ```ruby
-    ActiveRecord::DatabaseConfigurations::UrlConfig.new(
-      :production, :production, 'postgres:///?user=user&password=secret&dbname=app', {}
-    ).configuration_hash
+    # Before
+    Post.joins(:comments).pluck("posts.id", "comments.id", "comments.body")
+
+    # After
+    Post.joins(:comments).pluck(posts: [:id], comments: [:id, :body])
     ```
 
-    will now return,
+    *fatkodima*
 
-    ```ruby
-    { :user=>"user", :password=>"secret", :dbname=>"app", :adapter=>"postgresql" }
-    ```
+*   Raise an `ActiveRecord::ActiveRecordError` error when the MySQL database returns an invalid version string.
 
-    *Abeid Ahmed*
+    *Kevin McPhillips*
 
-*   PostgreSQL: support custom enum types
+*   `ActiveRecord::Base.transaction` now yields an `ActiveRecord::Transaction` object.
 
-    In migrations, use `create_enum` to add a new enum type, and `t.enum` to add a column.
+    This allows to register callbacks on it.
 
     ```ruby
-    def up
-      create_enum :mood, ["happy", "sad"]
-
-      change_table :cats do |t|
-        t.enum :current_mood, enum_type: "mood", default: "happy", null: false
+    Article.transaction do |transaction|
+      article.update(published: true)
+      transaction.after_commit do
+        PublishNotificationMailer.with(article: article).deliver_later
       end
     end
     ```
 
-    Enums will be presented correctly in `schema.rb`. Note that this is only supported by
-    the PostgreSQL adapter.
-
-    *Alex Ghiculescu*
-
-*   Avoid COMMENT statements in PostgreSQL structure dumps
-
-    COMMENT statements are now omitted from the output of `db:structure:dump` when using PostgreSQL >= 11.
-    This allows loading the dump without a pgsql superuser account.
-
-    Fixes #36816, #43107.
-
-    *Janosch Müller*
+    *Jean Boussier*
 
-*   Add support for generated columns in PostgreSQL adapter
+*   Add `ActiveRecord::Base.current_transaction`.
 
-    Generated columns are supported since version 12.0 of PostgreSQL. This adds
-    support of those to the PostgreSQL adapter.
+    Returns the current transaction, to allow registering callbacks on it.
 
     ```ruby
-    create_table :users do |t|
-      t.string :name
-      t.virtual :name_upcased, type: :string, as: 'upper(name)', stored: true
+    Article.current_transaction.after_commit do
+      PublishNotificationMailer.with(article: article).deliver_later
     end
     ```
 
-    *Michał Begejowicz*
-
-
-## Rails 7.0.0.alpha2 (September 15, 2021) ##
-
-*   No changes.
-
-
-## Rails 7.0.0.alpha1 (September 15, 2021) ##
-
-*   Remove warning when overwriting existing scopes
-
-    Removes the following unnecessary warning message that appeared when overwriting existing scopes
-
-    ```
-    Creating scope :my_scope_name. Overwriting existing method "MyClass.my_scope_name" when overwriting existing scopes
-    ```
-
-     *Weston Ganger*
-
-*   Use full precision for `updated_at` in `insert_all`/`upsert_all`
-
-    `CURRENT_TIMESTAMP` provides differing precision depending on the database,
-    and not all databases support explicitly specifying additional precision.
-
-    Instead, we delegate to the new `connection.high_precision_current_timestamp`
-    for the SQL to produce a high precision timestamp on the current database.
-
-    Fixes #42992
-
-    *Sam Bostock*
-
-*   Add ssl support for postgresql database tasks
-
-    Add `PGSSLMODE`, `PGSSLCERT`, `PGSSLKEY` and `PGSSLROOTCERT` to pg_env from database config
-    when running postgresql database tasks.
-
-    ```yaml
-    # config/database.yml
-
-    production:
-      sslmode: verify-full
-      sslcert: client.crt
-      sslkey: client.key
-      sslrootcert: ca.crt
-    ```
-
-    Environment variables
-
-    ```
-    PGSSLMODE=verify-full
-    PGSSLCERT=client.crt
-    PGSSLKEY=client.key
-    PGSSLROOTCERT=ca.crt
-    ```
-
-    Fixes #42994
-
-    *Michael Bayucot*
-
-*   Avoid scoping update callbacks in `ActiveRecord::Relation#update!`.
-
-    Making it consistent with how scoping is applied only to the query in `ActiveRecord::Relation#update`
-    and not also to the callbacks from the update itself.
-
-    *Dylan Thacker-Smith*
-
-*   Fix 2 cases that inferred polymorphic class from the association's `foreign_type`
-    using `String#constantize` instead of the model's `polymorphic_class_for`.
-
-    When updating a polymorphic association, the old `foreign_type` was not inferred correctly when:
-    1. `touch`ing the previously associated record
-    2. updating the previously associated record's `counter_cache`
-
-    *Jimmy Bourassa*
-
-*   Add config option for ignoring tables when dumping the schema cache.
+    *Jean Boussier*
 
-    Applications can now be configured to ignore certain tables when dumping the schema cache.
+*   Add `ActiveRecord.after_all_transactions_commit` callback.
 
-    The configuration option can table an array of tables:
+    Useful for code that may run either inside or outside a transaction and needs
+    to perform work after the state changes have been properly persisted.
 
     ```ruby
-    config.active_record.schema_cache_ignored_tables = ["ignored_table", "another_ignored_table"]
-    ```
-
-    Or a regex:
-
-    ```ruby
-    config.active_record.schema_cache_ignored_tables = [/^_/]
-    ```
-
-    *Eileen M. Uchitelle*
-
-*   Make schema cache methods return consistent results.
-
-    Previously the schema cache methods `primary_keys`, `columns`, `columns_hash`, and `indexes`
-    would behave differently than one another when a table didn't exist and differently across
-    database adapters. This change unifies the behavior so each method behaves the same regardless
-    of adapter.
-
-    The behavior now is:
-
-    `columns`: (unchanged) raises a db error if the table does not exist.
-    `columns_hash`: (unchanged) raises a db error if the table does not exist.
-    `primary_keys`: (unchanged) returns `nil` if the table does not exist.
-    `indexes`: (changed for mysql2) returns `[]` if the table does not exist.
-
-    *Eileen M. Uchitelle*
-
-*   Reestablish connection to previous database after after running `db:schema:load:name`
-
-    After running `db:schema:load:name` the previous connection is restored.
-
-    *Jacopo Beschi*
-
-*   Add database config option `database_tasks`
-
-    If you would like to connect to an external database without any database
-    management tasks such as schema management, migrations, seeds, etc. you can set
-    the per database config option `database_tasks: false`
-
-    ```yaml
-    # config/database.yml
-
-    production:
-      primary:
-        database: my_database
-        adapter: mysql2
-      animals:
-        database: my_animals_database
-        adapter: mysql2
-        database_tasks: false
+    def publish_article(article)
+      article.update(published: true)
+      ActiveRecord.after_all_transactions_commit do
+        PublishNotificationMailer.with(article: article).deliver_later
+      end
+    end
     ```
 
-    *Weston Ganger*
-
-*   Fix `ActiveRecord::InternalMetadata` to not be broken by `config.active_record.record_timestamps = false`
+    In the above example, the block is either executed immediately if called outside
+    of a transaction, or called after the open transaction is committed.
 
-    Since the model always create the timestamp columns, it has to set them, otherwise it breaks
-    various DB management tasks.
+    If the transaction is rolled back, the block isn't called.
 
-    Fixes #42983
+    *Jean Boussier*
 
-*   Add `ActiveRecord::QueryLogs`.
+*   Add the ability to ignore counter cache columns until they are backfilled.
 
-    Configurable tags can be automatically added to all SQL queries generated by Active Record.
+    Starting to use counter caches on existing large tables can be troublesome, because the column
+    values must be backfilled separately of the column addition (to not lock the table for too long)
+    and before the use of `:counter_cache` (otherwise methods like `size`/`any?`/etc, which use
+    counter caches internally, can produce incorrect results). People usually use database triggers
+    or callbacks on child associations while backfilling before introducing a counter cache
+    configuration to the association.
 
-    ```ruby
-    # config/application.rb
-    module MyApp
-      class Application < Rails::Application
-        config.active_record.query_log_tags_enabled = true
-      end
-    end
-    ```
-
-    By default the application, controller and action details are added to the query tags:
+    Now, to safely backfill the column, while keeping the column updated with child records added/removed, use:
 
     ```ruby
-    class BooksController < ApplicationController
-      def index
-        @books = Book.all
-      end
+    class Comment < ApplicationRecord
+      belongs_to :post, counter_cache: { active: false }
     end
     ```
 
-    ```ruby
-    GET /books
-    # SELECT * FROM books /*application:MyApp;controller:books;action:index*/
-    ```
+    While the counter cache is not "active", the methods like `size`/`any?`/etc will not use it,
+    but get the results directly from the database. After the counter cache column is backfilled, simply
+    remove the `{ active: false }` part from the counter cache definition, and it will now be used by the
+    mentioned methods.
 
-    Custom tags containing static values and Procs can be defined in the application configuration:
-
-    ```ruby
-    config.active_record.query_log_tags = [
-      :application,
-      :controller,
-      :action,
-      {
-        custom_static: "foo",
-        custom_dynamic: -> { Time.now }
-      }
-    ]
-    ```
-
-    *Keeran Raj Hawoldar*, *Eileen M. Uchitelle*, *Kasper Timm Hansen*
+    *fatkodima*
 
-*   Added support for multiple databases to `rails db:setup` and `rails db:reset`.
+*   Retry known idempotent SELECT queries on connection-related exceptions.
 
-    *Ryan Hall*
+    SELECT queries we construct by walking the Arel tree and / or with known model attributes
+    are idempotent and can safely be retried in the case of a connection error. Previously,
+    adapters such as `TrilogyAdapter` would raise `ActiveRecord::ConnectionFailed: Trilogy::EOFError`
+    when encountering a connection error mid-request.
 
-*   Add `ActiveRecord::Relation#structurally_compatible?`.
+    *Adrianna Chang*
 
-    Adds a query method by which a user can tell if the relation that they're
-    about to use for `#or` or `#and` is structurally compatible with the
-    receiver.
+*   Allow association's `foreign_key` to be composite.
 
-    *Kevin Newton*
+    `query_constraints` option was the only way to configure a composite foreign key by passing an `Array`.
+    Now it's possible to pass an Array value as `foreign_key` to achieve the same behavior of an association.
 
-*   Add `ActiveRecord::QueryMethods#in_order_of`.
+    *Nikita Vasilevsky*
 
-    This allows you to specify an explicit order that you'd like records
-    returned in based on a SQL expression. By default, this will be accomplished
-    using a case statement, as in:
+*   Allow association's `primary_key` to be composite.
 
-    ```ruby
-    Post.in_order_of(:id, [3, 5, 1])
-    ```
+    Association's `primary_key` can be composite when derived from associated model `primary_key` or `query_constraints`.
+    Now it's possible to explicitly set it as composite on the association.
 
-    will generate the SQL:
+    *Nikita Vasilevsky*
 
-    ```sql
-    SELECT "posts".* FROM "posts" ORDER BY CASE "posts"."id" WHEN 3 THEN 1 WHEN 5 THEN 2 WHEN 1 THEN 3 ELSE 4 END ASC
-    ```
+*   Add `config.active_record.permanent_connection_checkout` setting.
 
-    However, because this functionality is built into MySQL in the form of the
-    `FIELD` function, that connection adapter will generate the following SQL
-    instead:
+    Controls whether `ActiveRecord::Base.connection` raises an error, emits a deprecation warning, or neither.
 
-    ```sql
-    SELECT "posts".* FROM "posts" ORDER BY FIELD("posts"."id", 1, 5, 3) DESC
-    ```
+    `ActiveRecord::Base.connection` checkouts a database connection from the pool and keeps it leased until the end of
+    the request or job. This behavior can be undesirable in environments that use many more threads or fibers than there
+    is available connections.
 
-    *Kevin Newton*
+    This configuration can be used to track down and eliminate code that calls `ActiveRecord::Base.connection` and
+    migrate it to use `ActiveRecord::Base.with_connection` instead.
 
-*   Fix `eager_loading?` when ordering with `Symbol`.
+    The default behavior remains unchanged, and there is currently no plans to change the default.
 
-    `eager_loading?` is triggered correctly when using `order` with symbols.
+    *Jean Boussier*
 
-    ```ruby
-    scope = Post.includes(:comments).order(:"comments.label")
-    => true
-    ```
+*   Add dirties option to uncached.
 
-    *Jacopo Beschi*
+    This adds a `dirties` option to `ActiveRecord::Base.uncached` and
+    `ActiveRecord::ConnectionAdapters::ConnectionPool#uncached`.
 
-*   Two change tracking methods are added for `belongs_to` associations.
+    When set to `true` (the default), writes will clear all query caches belonging to the current thread.
+    When set to `false`, writes to the affected connection pool will not clear any query cache.
 
-    The `association_changed?` method (assuming an association named `:association`) returns true
-    if a different associated object has been assigned and the foreign key will be updated in the
-    next save.
+    This is needed by Solid Cache so that cache writes do not clear query caches.
 
-    The `association_previously_changed?` method returns true if the previous save updated the
-    association to reference a different associated object.
+    *Donal McBreen*
 
-    *George Claghorn*
+*   Deprecate `ActiveRecord::Base.connection` in favor of `.lease_connection`.
 
-*   Add option to disable schema dump per-database.
+    The method has been renamed as `lease_connection` to better reflect that the returned
+    connection will be held for the duration of the request or job.
 
-    Dumping the schema is on by default for all databases in an application. To turn it off for a
-    specific database, use the `schema_dump` option:
+    This deprecation is a soft deprecation, no warnings will be issued and there is no
+    current plan to remove the method.
 
-    ```yaml
-    # config/database.yml
+    *Jean Boussier*
 
-    production:
-      schema_dump: false
-    ```
+*   Deprecate `ActiveRecord::ConnectionAdapters::ConnectionPool#connection`.
 
-    *Luis Vasconcellos*, *Eileen M. Uchitelle*
+    The method has been renamed as `lease_connection` to better reflect that the returned
+    connection will be held for the duration of the request or job.
 
-*   Fix `eager_loading?` when ordering with `Hash` syntax.
+    *Jean Boussier*
 
-    `eager_loading?` is triggered correctly when using `order` with hash syntax
-    on an outer table.
+*   Expose a generic fixture accessor for fixture names that may conflict with Minitest.
 
     ```ruby
-    Post.includes(:comments).order({ "comments.label": :ASC }).eager_loading?
-    # => true
+    assert_equal "Ruby on Rails", web_sites(:rubyonrails).name
+    assert_equal "Ruby on Rails", fixture(:web_sites, :rubyonrails).name
     ```
 
-    *Jacopo Beschi*
-
-*   Move the forcing of clear text encoding to the `ActiveRecord::Encryption::Encryptor`.
+    *Jean Boussier*
 
-    Fixes #42699.
+*   Using `Model.query_constraints` with a single non-primary-key column used to raise as expected, but with an
+    incorrect error message.
 
-    *J Smith*
+    This has been fixed to raise with a more appropriate error message.
 
-*   `partial_inserts` is now disabled by default in new apps.
+    *Joshua Young*
 
-    This will be the default for new apps in Rails 7. To opt in:
+*   Fix `has_one` association autosave setting the foreign key attribute when it is unchanged.
 
-    ```ruby
-    config.active_record.partial_inserts = true
-    ```
+    This behavior is also inconsistent with autosaving `belongs_to` and can have unintended side effects like raising
+    an `ActiveRecord::ReadonlyAttributeError` when the foreign key attribute is marked as read-only.
 
-    If a migration removes the default value of a column, this option
-    would cause old processes to no longer be able to create new records.
+    *Joshua Young*
 
-    If you need to remove a column, you should first use `ignored_columns`
-    to stop using it.
+*   Remove deprecated behavior that would rollback a transaction block when exited using `return`, `break` or `throw`.
 
-    *Jean Boussier*
+    *Rafael Mendonça França*
 
-*   Rails can now verify foreign keys after loading fixtures in tests.
+*   Deprecate `Rails.application.config.active_record.commit_transaction_on_non_local_return`.
 
-    This will be the default for new apps in Rails 7. To opt in:
+    *Rafael Mendonça França*
 
-    ```ruby
-    config.active_record.verify_foreign_keys_for_fixtures = true
-    ```
+*   Remove deprecated support to pass `rewhere` to `ActiveRecord::Relation#merge`.
 
-    Tests will not run if there is a foreign key constraint violation in your fixture data.
+    *Rafael Mendonça França*
 
-    The feature is supported by SQLite and PostgreSQL, other adapters can also add support for it.
+*   Remove deprecated support to pass `deferrable: true` to `add_foreign_key`.
 
-    *Alex Ghiculescu*
+    *Rafael Mendonça França*
 
-*   Clear cached `has_one` association after setting `belongs_to` association to `nil`.
+*   Remove deprecated support to quote `ActiveSupport::Duration`.
 
-    After setting a `belongs_to` relation to `nil` and updating an unrelated attribute on the owner,
-    the owner should still return `nil` on the `has_one` relation.
+    *Rafael Mendonça França*
 
-    Fixes #42597.
+*   Remove deprecated `#quote_bound_value`.
 
-    *Michiel de Mare*
+    *Rafael Mendonça França*
 
-*   OpenSSL constants are now used for Digest computations.
+*   Remove deprecated `ActiveRecord::ConnectionAdapters::ConnectionPool#connection_klass`.
 
-    *Dirkjan Bussink*
+    *Rafael Mendonça França*
 
-*   Adds support for `if_not_exists` to `add_foreign_key` and `if_exists` to `remove_foreign_key`.
+*   Remove deprecated support to apply `#connection_pool_list`, `#active_connections?`, `#clear_active_connections!`,
+    `#clear_reloadable_connections!`, `#clear_all_connections!` and `#flush_idle_connections!` to the connections pools
+    for the current role when the `role` argument isn't provided.
 
-    Applications can set their migrations to ignore exceptions raised when adding a foreign key
-    that already exists or when removing a foreign key that does not exist.
+    *Rafael Mendonça França*
 
-    Example Usage:
+*   Remove deprecated `#all_connection_pools`.
 
-    ```ruby
-    class AddAuthorsForeignKeyToArticles < ActiveRecord::Migration[7.0]
-      def change
-        add_foreign_key :articles, :authors, if_not_exists: true
-      end
-    end
-    ```
+    *Rafael Mendonça França*
 
-    ```ruby
-    class RemoveAuthorsForeignKeyFromArticles < ActiveRecord::Migration[7.0]
-      def change
-        remove_foreign_key :articles, :authors, if_exists: true
-      end
-    end
-    ```
+*   Remove deprecated `ActiveRecord::ConnectionAdapters::SchemaCache#data_sources`.
 
-    *Roberto Miranda*
+    *Rafael Mendonça França*
 
-*   Prevent polluting ENV during postgresql structure dump/load.
+*   Remove deprecated `ActiveRecord::ConnectionAdapters::SchemaCache.load_from`.
 
-    Some configuration parameters were provided to pg_dump / psql via
-    environment variables which persisted beyond the command being run, and may
-    have caused subsequent commands and connections to fail. Tasks running
-    across multiple postgresql databases like `rails db:test:prepare` may have
-    been affected.
+    *Rafael Mendonça França*
 
-    *Samuel Cochran*
+*   Remove deprecated `#all_foreign_keys_valid?` from database adapters.
 
-*   Set precision 6 by default for `datetime` columns.
+    *Rafael Mendonça França*
 
-    By default, datetime columns will have microseconds precision instead of seconds precision.
+*   Remove deprecated support to passing coder and class as second argument to `serialize`.
 
-    *Roberto Miranda*
+    *Rafael Mendonça França*
 
-*   Allow preloading of associations with instance dependent scopes.
+*   Remove deprecated support to `ActiveRecord::Base#read_attribute(:id)` to return the custom primary key value.
 
-    *John Hawthorn*, *John Crepezzi*, *Adam Hess*, *Eileen M. Uchitelle*, *Dinah Shi*
+    *Rafael Mendonça França*
 
-*   Do not try to rollback transactions that failed due to a `ActiveRecord::TransactionRollbackError`.
+*   Remove deprecated `TestFixtures.fixture_path`.
 
-    *Jamie McCarthy*
+    *Rafael Mendonça França*
 
-*   Active Record Encryption will now encode values as UTF-8 when using deterministic
-    encryption. The encoding is part of the encrypted payload, so different encodings for
-    different values result in different ciphertexts. This can break unique constraints and
-    queries.
+*   Remove deprecated behavior to support referring to a singular association by its plural name.
 
-    The new behavior is configurable via `active_record.encryption.forced_encoding_for_deterministic_encryption`
-    that is `Encoding::UTF_8` by default. It can be disabled by setting it to `nil`.
+    *Rafael Mendonça França*
 
-    *Jorge Manrubia*
+*   Deprecate `Rails.application.config.active_record.allow_deprecated_singular_associations_name`.
 
-*   The MySQL adapter now cast numbers and booleans bind parameters to string for safety reasons.
+    *Rafael Mendonça França*
 
-    When comparing a string and a number in a query, MySQL converts the string to a number. So for
-    instance `"foo" = 0`, will implicitly cast `"foo"` to `0` and will evaluate to `TRUE` which can
-    lead to security vulnerabilities.
+*   Remove deprecated support to passing `SchemaMigration` and `InternalMetadata` classes as arguments to
+    `ActiveRecord::MigrationContext`.
 
-    Active Record already protect against that vulnerability when it knows the type of the column
-    being compared, however until now it was still vulnerable when using bind parameters:
+    *Rafael Mendonça França*
 
-    ```ruby
-    User.where("login_token = ?", 0).first
-    ```
+*   Remove deprecated `ActiveRecord::Migration.check_pending!` method.
 
-    Would perform:
+    *Rafael Mendonça França*
 
-    ```sql
-    SELECT * FROM `users` WHERE `login_token` = 0 LIMIT 1;
-    ```
+*   Remove deprecated `ActiveRecord::LogSubscriber.runtime` method.
 
-    Now it will perform:
+    *Rafael Mendonça França*
 
-    ```sql
-    SELECT * FROM `users` WHERE `login_token` = '0' LIMIT 1;
-    ```
+*   Remove deprecated `ActiveRecord::LogSubscriber.runtime=` method.
 
-    *Jean Boussier*
+    *Rafael Mendonça França*
 
-*   Fixture configurations (`_fixture`) are now strictly validated.
+*   Remove deprecated `ActiveRecord::LogSubscriber.reset_runtime` method.
 
-    If an error will be raised if that entry contains unknown keys while previously it
-    would silently have no effects.
+    *Rafael Mendonça França*
 
-    *Jean Boussier*
+*   Remove deprecated support to define `explain` in the connection adapter with 2 arguments.
 
-*   Add `ActiveRecord::Base.update!` that works like `ActiveRecord::Base.update` but raises exceptions.
+    *Rafael Mendonça França*
 
-    This allows for the same behavior as the instance method `#update!` at a class level.
+*   Remove deprecated `ActiveRecord::ActiveJobRequiredError`.
 
-    ```ruby
-    Person.update!(:all, state: "confirmed")
-    ```
+    *Rafael Mendonça França*
 
-    *Dorian Marié*
+*   Remove deprecated `ActiveRecord::Base.clear_active_connections!`.
 
-*   Add `ActiveRecord::Base#attributes_for_database`.
+    *Rafael Mendonça França*
 
-    Returns attributes with values for assignment to the database.
+*   Remove deprecated `ActiveRecord::Base.clear_reloadable_connections!`.
 
-    *Chris Salzberg*
+    *Rafael Mendonça França*
 
-*   Use an empty query to check if the PostgreSQL connection is still active.
+*   Remove deprecated `ActiveRecord::Base.clear_all_connections!`.
 
-    An empty query is faster than `SELECT 1`.
+    *Rafael Mendonça França*
 
-    *Heinrich Lee Yu*
+*   Remove deprecated `ActiveRecord::Base.flush_idle_connections!`.
 
-*   Add `ActiveRecord::Base#previously_persisted?`.
+    *Rafael Mendonça França*
 
-    Returns `true` if the object has been previously persisted but now it has been deleted.
+*   Remove deprecated `name` argument from `ActiveRecord::Base.remove_connection`.
 
-*   Deprecate `partial_writes` in favor of `partial_inserts` and `partial_updates`.
+    *Rafael Mendonça França*
 
-    This allows to have a different behavior on update and create.
+*   Remove deprecated support to call `alias_attribute` with non-existent attribute names.
 
-    *Jean Boussier*
+    *Rafael Mendonça França*
 
-*   Fix compatibility with `psych >= 4`.
+*   Remove deprecated `Rails.application.config.active_record.suppress_multiple_database_warning`.
 
-    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.
+    *Rafael Mendonça França*
 
-    *Jean Boussier*
+*   Add `ActiveRecord::Encryption::MessagePackMessageSerializer`.
 
-*   `ActiveRecord::Base.logger` is now a `class_attribute`.
+    Serialize data to the MessagePack format, for efficient storage in binary columns.
 
-    This means it can no longer be accessed directly through `@@logger`, and that setting `logger =`
-    on a subclass won't change the parent's logger.
+    The binary encoding requires around 30% less space than the base64 encoding
+    used by the default serializer.
 
-    *Jean Boussier*
+    *Donal McBreen*
 
-*   Add `.asc.nulls_first` for all databases. Unfortunately MySQL still doesn't like `nulls_last`.
+*   Add support for encrypting binary columns.
 
-    *Keenan Brock*
+    Ensure encryption and decryption pass `Type::Binary::Data` around for binary data.
 
-*   Improve performance of `one?` and `many?` by limiting the generated count query to 2 results.
+    Previously encrypting binary columns with the `ActiveRecord::Encryption::MessageSerializer`
+    incidentally worked for MySQL and SQLite, but not PostgreSQL.
 
-    *Gonzalo Riestra*
+    *Donal McBreen*
 
-*   Don't check type when using `if_not_exists` on `add_column`.
+*   Deprecated `ENV["SCHEMA_CACHE"]` in favor of `schema_cache_path` in the database configuration.
 
-    Previously, if a migration called `add_column` with the `if_not_exists` option set to true
-    the `column_exists?` check would look for a column with the same name and type as the migration.
+    *Rafael Mendonça França*
 
-    Recently it was discovered that the type passed to the migration is not always the same type
-    as the column after migration. For example a column set to `:mediumblob` in the migration will
-    be casted to `binary` when calling `column.type`. Since there is no straightforward way to cast
-    the type to the database type without running the migration, we opted to drop the type check from
-    `add_column`. This means that migrations adding a duplicate column with a different type will no
-    longer raise an error.
+*   Add `ActiveRecord::Base.with_connection` as a shortcut for leasing a connection for a short duration.
 
-    *Eileen M. Uchitelle*
+    The leased connection is yielded, and for the duration of the block, any call to `ActiveRecord::Base.connection`
+    will yield that same connection.
 
-*   Log a warning message when running SQLite in production.
+    This is useful to perform a few database operations without causing a connection to be leased for the
+    entire duration of the request or job.
 
-    Using SQLite in production ENV is generally discouraged. SQLite is also the default adapter
-    in a new Rails application.
-    For the above reasons log a warning message when running SQLite in production.
+    *Jean Boussier*
 
-    The warning can be disabled by setting `config.active_record.sqlite3_production_warning=false`.
+*   Deprecate `config.active_record.warn_on_records_fetched_greater_than` now that `sql.active_record`
+    notification includes `:row_count` field.
 
-    *Jacopo Beschi*
+    *Jason Nochlin*
 
-*   Add option to disable joins for `has_one` associations.
+*   The fix ensures that the association is joined using the appropriate join type
+    (either inner join or left outer join) based on the existing joins in the scope.
 
-    In a multiple database application, associations can't join across
-    databases. When set, this option instructs Rails to generate 2 or
-    more queries rather than generating joins for `has_one` associations.
+    This prevents unintentional overrides of existing join types and ensures consistency in the generated SQL queries.
 
-    Set the option on a has one through association:
+    Example:
 
-    ```ruby
-    class Person
-      has_one :dog
-      has_one :veterinarian, through: :dog, disable_joins: true
-    end
-    ```
 
-    Then instead of generating join SQL, two queries are used for `@person.veterinarian`:
 
+    ```ruby
+    # `associated` will use `LEFT JOIN` instead of using `JOIN`
+    Post.left_joins(:author).where.associated(:author)
     ```
-    SELECT "dogs"."id" FROM "dogs" WHERE "dogs"."person_id" = ?  [["person_id", 1]]
-    SELECT "veterinarians".* FROM "veterinarians" WHERE "veterinarians"."dog_id" = ?  [["dog_id", 1]]
-    ```
-
-    *Sarah Vessels*, *Eileen M. Uchitelle*
-
-*   `Arel::Visitors::Dot` now renders a complete set of properties when visiting
-    `Arel::Nodes::SelectCore`, `SelectStatement`, `InsertStatement`, `UpdateStatement`, and
-    `DeleteStatement`, which fixes #42026. Previously, some properties were omitted.
 
-    *Mike Dalessio*
+    *Saleh Alhaddad*
 
-*   `Arel::Visitors::Dot` now supports `Arel::Nodes::Bin`, `Case`, `CurrentRow`, `Distinct`,
-    `DistinctOn`, `Else`, `Except`, `InfixOperation`, `Intersect`, `Lock`, `NotRegexp`, `Quoted`,
-    `Regexp`, `UnaryOperation`, `Union`, `UnionAll`, `When`, and `With`. Previously, these node
-    types caused an exception to be raised by `Arel::Visitors::Dot#accept`.
+*   Fix an issue where `ActiveRecord::Encryption` configurations are not ready before the loading
+    of Active Record models, when an application is eager loaded. As a result, encrypted attributes
+    could be misconfigured in some cases.
 
-    *Mike Dalessio*
+    *Maxime Réty*
 
-*   Optimize `remove_columns` to use a single SQL statement.
+*   Deprecate defining an `enum` with keyword arguments.
 
     ```ruby
-    remove_columns :my_table, :col_one, :col_two
-    ```
-
-    Now results in the following SQL:
+    class Function > ApplicationRecord
+      # BAD
+      enum color: [:red, :blue],
+           type: [:instance, :class]
 
-    ```sql
-    ALTER TABLE "my_table" DROP COLUMN "col_one", DROP COLUMN "col_two"
+      # GOOD
+      enum :color, [:red, :blue]
+      enum :type, [:instance, :class]
+    end
     ```
 
-    *Jon Dufresne*
+    *Hartley McGuire*
 
-*   Ensure `has_one` autosave association callbacks get called once.
+*   Add `config.active_record.validate_migration_timestamps` option for validating migration timestamps.
 
-    Change the `has_one` autosave callback to be non cyclic as well.
-    By doing this the autosave callback are made more consistent for
-    all 3 cases: `has_many`, `has_one`, and `belongs_to`.
+    When set, validates that the timestamp prefix for a migration is no more than a day ahead of
+    the timestamp associated with the current time. This is designed to prevent migrations prefixes
+    from being hand-edited to future timestamps, which impacts migration generation and other
+    migration commands.
 
-    *Petrik de Heus*
+    *Adrianna Chang*
 
-*   Add option to disable joins for associations.
+*   Properly synchronize `Mysql2Adapter#active?` and `TrilogyAdapter#active?`.
 
-    In a multiple database application, associations can't join across
-    databases. When set, this option instructs Rails to generate 2 or
-    more queries rather than generating joins for associations.
+    As well as `disconnect!` and `verify!`.
 
-    Set the option on a has many through association:
+    This generally isn't a big problem as connections must not be shared between
+    threads, but is required when running transactional tests or system tests
+    and could lead to a SEGV.
 
-    ```ruby
-    class Dog
-      has_many :treats, through: :humans, disable_joins: true
-      has_many :humans
-    end
-    ```
+    *Jean Boussier*
 
-    Then instead of generating join SQL, two queries are used for `@dog.treats`:
+*   Support `:source_location` tag option for query log tags.
 
+    ```ruby
+    config.active_record.query_log_tags << :source_location
     ```
-    SELECT "humans"."id" FROM "humans" WHERE "humans"."dog_id" = ?  [["dog_id", 1]]
-    SELECT "treats".* FROM "treats" WHERE "treats"."human_id" IN (?, ?, ?)  [["human_id", 1], ["human_id", 2], ["human_id", 3]]
-    ```
-
-    *Eileen M. Uchitelle*, *Aaron Patterson*, *Lee Quarella*
-
-*   Add setting for enumerating column names in SELECT statements.
 
-    Adding a column to a PostgreSQL database, for example, while the application is running can
-    change the result of wildcard `SELECT *` queries, which invalidates the result
-    of cached prepared statements and raises a `PreparedStatementCacheExpired` error.
+    Calculating the caller location is a costly operation and should be used primarily in development
+    (note, there is also a `config.active_record.verbose_query_logs` that serves the same purpose)
+    or occasionally on production for debugging purposes.
 
-    When enabled, Active Record will avoid wildcards and always include column names
-    in `SELECT` queries, which will return consistent results and avoid prepared
-    statement errors.
+    *fatkodima*
 
-    Before:
+*   Add an option to `ActiveRecord::Encryption::Encryptor` to disable compression.
 
-    ```ruby
-    Book.limit(5)
-    # SELECT * FROM books LIMIT 5
-    ```
-
-    After:
+    Allow compression to be disabled by setting `compress: false`
 
     ```ruby
-    # config/application.rb
-    module MyApp
-      class Application < Rails::Application
-        config.active_record.enumerate_columns_in_select_statements = true
+      class User
+        encrypts :name, encryptor: ActiveRecord::Encryption::Encryptor.new(compress: false)
       end
-    end
-
-    # or, configure per-model
-    class Book < ApplicationRecord
-      self.enumerate_columns_in_select_statements = true
-    end
     ```
 
-    ```ruby
-    Book.limit(5)
-    # SELECT id, author_id, name, format, status, language, etc FROM books LIMIT 5
-    ```
+    *Donal McBreen*
 
-    *Matt Duszynski*
+*   Deprecate passing strings to `ActiveRecord::Tasks::DatabaseTasks.cache_dump_filename`.
 
-*   Allow passing SQL as `on_duplicate` value to `#upsert_all` to make it possible to use raw SQL to update columns on conflict:
+    A `ActiveRecord::DatabaseConfigurations::DatabaseConfig` object should be passed instead.
 
-    ```ruby
-    Book.upsert_all(
-      [{ id: 1, status: 1 }, { id: 2, status: 1 }],
-      on_duplicate: Arel.sql("status = GREATEST(books.status, EXCLUDED.status)")
-    )
-    ```
+    *Rafael Mendonça França*
 
-    *Vladimir Dementyev*
+*   Add `row_count` field to `sql.active_record` notification.
 
-*   Allow passing SQL as `returning` statement to `#upsert_all`:
+    This field returns the amount of rows returned by the query that emitted the notification.
 
-    ```ruby
-    Article.insert_all(
-      [
-        { title: "Article 1", slug: "article-1", published: false },
-        { title: "Article 2", slug: "article-2", published: false }
-      ],
-      returning: Arel.sql("id, (xmax = '0') as inserted, name as new_name")
-    )
-    ```
+    This metric is useful in cases where one wants to detect queries with big result sets.
 
-    *Vladimir Dementyev*
+    *Marvin Bitterlich*
 
-*   Deprecate `legacy_connection_handling`.
+*   Consistently raise an `ArgumentError` when passing an invalid argument to a nested attributes association writer.
 
-    *Eileen M. Uchitelle*
+    Previously, this would only raise on collection associations and produce a generic error on singular associations.
 
-*   Add attribute encryption support.
+    Now, it will raise on both collection and singular associations.
 
-    Encrypted attributes are declared at the model level. These
-    are regular Active Record attributes backed by a column with
-    the same name. The system will transparently encrypt these
-    attributes before saving them into the database and will
-    decrypt them when retrieving their values.
+    *Joshua Young*
 
+*   Fix single quote escapes on default generated MySQL columns.
 
-    ```ruby
-    class Person < ApplicationRecord
-      encrypts :name
-      encrypts :email_address, deterministic: true
-    end
-    ```
+    MySQL 5.7.5+ supports generated columns, which can be used to create a column that is computed from an expression.
 
-    You can learn more in the [Active Record Encryption
-    guide](https://edgeguides.rubyonrails.org/active_record_encryption.html).
+    Previously, the schema dump would output a string with double escapes for generated columns with single quotes in the default expression.
 
-    *Jorge Manrubia*
+    This would result in issues when importing the schema on a fresh instance of a MySQL database.
 
-*   Changed Arel predications `contains` and `overlaps` to use
-    `quoted_node` so that PostgreSQL arrays are quoted properly.
+    Now, the string will not be escaped and will be valid Ruby upon importing of the schema.
 
-    *Bradley Priest*
+    *Yash Kapadia*
 
-*   Add mode argument to record level `strict_loading!`.
+*   Fix Migrations with versions older than 7.1 validating options given to
+    `add_reference` and `t.references`.
 
-    This argument can be used when enabling strict loading for a single record
-    to specify that we only want to raise on n plus one queries.
+    *Hartley McGuire*
 
-    ```ruby
-    developer.strict_loading!(mode: :n_plus_one_only)
+*   Add `<role>_types` class method to `ActiveRecord::DelegatedType` so that the delegated types can be introspected.
 
-    developer.projects.to_a # Does not raise
-    developer.projects.first.client # Raises StrictLoadingViolationError
-    ```
+    *JP Rosevear*
 
-    Previously, enabling strict loading would cause any lazily loaded
-    association to raise an error. Using `n_plus_one_only` mode allows us to
-    lazily load belongs_to, has_many, and other associations that are fetched
-    through a single query.
+*   Make `schema_dump`, `query_cache`, `replica` and `database_tasks` configurable via `DATABASE_URL`.
 
-    *Dinah Shi*
+    This wouldn't always work previously because boolean values would be interpreted as strings.
 
-*   Fix Float::INFINITY assignment to datetime column with postgresql adapter.
+    e.g. `DATABASE_URL=postgres://localhost/foo?schema_dump=false` now properly disable dumping the schema
+    cache.
 
-    Before:
+    *Mike Coutermarsh*, *Jean Boussier*
 
-    ```ruby
-    # With this config
-    ActiveRecord::Base.time_zone_aware_attributes = true
+*   Introduce `ActiveRecord::Transactions::ClassMethods#set_callback`.
 
-    # and the following schema:
-    create_table "postgresql_infinities" do |t|
-      t.datetime "datetime"
-    end
+     It is identical to `ActiveSupport::Callbacks::ClassMethods#set_callback`
+     but with support for `after_commit` and `after_rollback` callback options.
 
-    # This test fails
-    record = PostgresqlInfinity.create!(datetime: Float::INFINITY)
-    assert_equal Float::INFINITY, record.datetime # record.datetime gets nil
-    ```
+    *Joshua Young*
 
-    After this commit, `record.datetime` gets `Float::INFINITY` as expected.
+*   Make `ActiveRecord::Encryption::Encryptor` agnostic of the serialization format used for encrypted data.
 
-    *Shunichi Ikegami*
+    Previously, the encryptor instance only allowed an encrypted value serialized as a `String` to be passed to the message serializer.
 
-*   Type cast enum values by the original attribute type.
+    Now, the encryptor lets the configured `message_serializer` decide which types of serialized encrypted values are supported. A custom serialiser is therefore allowed to serialize `ActiveRecord::Encryption::Message` objects using a type other than `String`.
 
-    The notable thing about this change is that unknown labels will no longer match 0 on MySQL.
+    The default `ActiveRecord::Encryption::MessageSerializer` already ensures that only `String` objects are passed for deserialization.
 
-    ```ruby
-    class Book < ActiveRecord::Base
-      enum :status, { proposed: 0, written: 1, published: 2 }
-    end
-    ```
+    *Maxime Réty*
 
-    Before:
+*   Fix `encrypted_attribute?` to take into account context properties passed to `encrypts`.
 
-    ```ruby
-    # SELECT `books`.* FROM `books` WHERE `books`.`status` = 'prohibited' LIMIT 1
-    Book.find_by(status: :prohibited)
-    # => #<Book id: 1, status: "proposed", ...> (for mysql2 adapter)
-    # => ActiveRecord::StatementInvalid: PG::InvalidTextRepresentation: ERROR:  invalid input syntax for type integer: "prohibited" (for postgresql adapter)
-    # => nil (for sqlite3 adapter)
-    ```
+    *Maxime Réty*
 
-    After:
+*   The object returned by `explain` now responds to `pluck`, `first`,
+    `last`, `average`, `count`, `maximum`, `minimum`, and `sum`. Those
+    new methods run `EXPLAIN` on the corresponding queries:
 
     ```ruby
-    # SELECT `books`.* FROM `books` WHERE `books`.`status` IS NULL LIMIT 1
-    Book.find_by(status: :prohibited)
-    # => nil (for all adapters)
-    ```
-
-    *Ryuta Kamizono*
+    User.all.explain.count
+    # EXPLAIN SELECT COUNT(*) FROM `users`
+    # ...
 
-*   Fixtures for `has_many :through` associations now load timestamps on join tables.
-
-    Given this fixture:
-
-    ```yml
-    ### monkeys.yml
-    george:
-      name: George the Monkey
-      fruits: apple
-
-    ### fruits.yml
-    apple:
-      name: apple
+    User.all.explain.maximum(:id)
+    # EXPLAIN SELECT MAX(`users`.`id`) FROM `users`
+    # ...
     ```
 
-    If the join table (`fruit_monkeys`) contains `created_at` or `updated_at` columns,
-    these will now be populated when loading the fixture. Previously, fixture loading
-    would crash if these columns were required, and leave them as null otherwise.
-
-    *Alex Ghiculescu*
-
-*   Allow applications to configure the thread pool for async queries.
-
-    Some applications may want one thread pool per database whereas others want to use
-    a single global thread pool for all queries. By default, Rails will set `async_query_executor`
-    to `nil` which will not initialize any executor. If `load_async` is called and no executor
-    has been configured, the query will be executed in the foreground.
+    *Petrik de Heus*
 
-    To create one thread pool for all database connections to use applications can set
-    `config.active_record.async_query_executor` to `:global_thread_pool` and optionally define
-    `config.active_record.global_executor_concurrency`. This defaults to 4. For applications that want
-    to have a thread pool for each database connection, `config.active_record.async_query_executor` can
-    be set to `:multi_thread_pool`. The configuration for each thread pool is set in the database
-    configuration.
+*   Fixes an issue where `validates_associated` `:on`  option wasn't respected
+    when validating associated records.
 
-    *Eileen M. Uchitelle*
+    *Austen Madden*, *Alex Ghiculescu*, *Rafał Brize*
 
-*   Allow new syntax for `enum` to avoid leading `_` from reserved options.
+*   Allow overriding SQLite defaults from `database.yml`.
 
-    Before:
+    Any PRAGMA configuration set under the `pragmas` key in the configuration
+    file takes precedence over Rails' defaults, and additional PRAGMAs can be
+    set as well.
 
-    ```ruby
-    class Book < ActiveRecord::Base
-      enum status: [ :proposed, :written ], _prefix: true, _scopes: false
-      enum cover: [ :hard, :soft ], _suffix: true, _default: :hard
-    end
+    ```yaml
+    database: storage/development.sqlite3
+    timeout: 5000
+    pragmas:
+      journal_mode: off
+      temp_store: memory
     ```
 
-    After:
-
-    ```ruby
-    class Book < ActiveRecord::Base
-      enum :status, [ :proposed, :written ], prefix: true, scopes: false
-      enum :cover, [ :hard, :soft ], suffix: true, default: :hard
-    end
-    ```
+    *Stephen Margheim*
 
-    *Ryuta Kamizono*
+*   Remove warning message when running SQLite in production, but leave it unconfigured.
 
-*   Add `ActiveRecord::Relation#load_async`.
+    There are valid use cases for running SQLite in production. However, it must be done
+    with care, so instead of a warning most users won't see anyway, it's preferable to
+    leave the configuration commented out to force them to think about having the database
+    on a persistent volume etc.
 
-    This method schedules the query to be performed asynchronously from a thread pool.
+    *Jacopo Beschi*, *Jean Boussier*
 
-    If the result is accessed before a background thread had the opportunity to perform
-    the query, it will be performed in the foreground.
+*   Add support for generated columns to the SQLite3 adapter.
 
-    This is useful for queries that can be performed long enough before their result will be
-    needed, or for controllers which need to perform several independent queries.
+    Generated columns (both stored and dynamic) are supported since version 3.31.0 of SQLite.
+    This adds support for those to the SQLite3 adapter.
 
     ```ruby
-    def index
-      @categories = Category.some_complex_scope.load_async
-      @posts = Post.some_complex_scope.load_async
+    create_table :users do |t|
+      t.string :name
+      t.virtual :name_upper, type: :string, as: 'UPPER(name)'
+      t.virtual :name_lower, type: :string, as: 'LOWER(name)', stored: true
     end
     ```
 
-    Active Record logs will also include timing info for the duration of how long
-    the main thread had to wait to access the result. This timing is useful to know
-    whether or not it's worth to load the query asynchronously.
+    *Stephen Margheim*
 
-    ```
-    DEBUG -- :   Category Load (62.1ms)  SELECT * FROM `categories` LIMIT 50
-    DEBUG -- :   ASYNC Post Load (64ms) (db time 126.1ms)  SELECT * FROM `posts` LIMIT 100
-    ```
+*   TrilogyAdapter: ignore `host` if `socket` parameter is set.
 
-    The duration in the first set of parens is how long the main thread was blocked
-    waiting for the results, and the second set of parens with "db time" is how long
-    the entire query took to execute.
-
-    *Jean Boussier*
+    This allows to configure a connection on a UNIX socket via `DATABASE_URL`:
 
-*   Implemented `ActiveRecord::Relation#excluding` method.
-
-    This method excludes the specified record (or collection of records) from
-    the resulting relation:
-
-    ```ruby
-    Post.excluding(post)
-    Post.excluding(post_one, post_two)
     ```
-
-    Also works on associations:
-
-    ```ruby
-    post.comments.excluding(comment)
-    post.comments.excluding(comment_one, comment_two)
+    DATABASE_URL=trilogy://does-not-matter/my_db_production?socket=/var/run/mysql.sock
     ```
 
-    This is short-hand for `Post.where.not(id: post.id)` (for a single record)
-    and `Post.where.not(id: [post_one.id, post_two.id])` (for a collection).
-
-    *Glen Crawford*
-
-*   Skip optimised #exist? query when #include? is called on a relation
-    with a having clause.
+    *Jean Boussier*
 
-    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.
+*   Make `assert_queries_count`, `assert_no_queries`, `assert_queries_match`, and
+    `assert_no_queries_match` assertions public.
 
-    A sample query affected by this problem:
+    To assert the expected number of queries are made, Rails internally uses `assert_queries_count` and
+    `assert_no_queries`. To assert that specific SQL queries are made, `assert_queries_match` and
+    `assert_no_queries_match` are used. These assertions can now be used in applications as well.
 
     ```ruby
-    Author.select('COUNT(*) as total_posts', 'authors.*')
-          .joins(:posts)
-          .group(:id)
-          .having('total_posts > 2')
-          .include?(Author.first)
-    ```
-
-    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.
-
-    Fixes #41417.
-
-    *Michael Smart*
-
-*   Increment postgres prepared statement counter before making a prepared statement, so if the statement is aborted
-    without Rails knowledge (e.g., if app gets killed during long-running query or due to Rack::Timeout), app won't end
-    up in perpetual crash state for being inconsistent with PostgreSQL.
-
-    *wbharding*, *Martin Tepper*
-
-*   Add ability to apply `scoping` to `all_queries`.
-
-    Some applications may want to use the `scoping` method but previously it only
-    worked on certain types of queries. This change allows the `scoping` method to apply
-    to all queries for a model in a block.
+    class ArticleTest < ActiveSupport::TestCase
+      test "queries are made" do
+        assert_queries_count(1) { Article.first }
+      end
 
-    ```ruby
-    Post.where(blog_id: post.blog_id).scoping(all_queries: true) do
-      post.update(title: "a post title") # adds `posts.blog_id = 1` to the query
+      test "creates a foreign key" do
+        assert_queries_match(/ADD FOREIGN KEY/i, include_schema: true) do
+          @connection.add_foreign_key(:comments, :posts)
+        end
+      end
     end
     ```
 
-    *Eileen M. Uchitelle*
-
-*   `ActiveRecord::Calculations.calculate` called with `:average`
-    (aliased as `ActiveRecord::Calculations.average`) will now use column-based
-    type casting. This means that floating-point number columns will now be
-    aggregated as `Float` and decimal columns will be aggregated as `BigDecimal`.
+    *Petrik de Heus*, *fatkodima*
 
-    Integers are handled as a special case returning `BigDecimal` always
-    (this was the case before already).
+*   Fix `has_secure_token` calls the setter method on initialize.
 
-    ```ruby
-    # With the following schema:
-    create_table "measurements" do |t|
-      t.float "temperature"
-    end
+    *Abeid Ahmed*
 
-    # Before:
-    Measurement.average(:temperature).class
-    # => BigDecimal
+*   When using a `DATABASE_URL`, allow for a configuration to map the protocol in the URL to a specific database
+    adapter. This allows decoupling the adapter the application chooses to use from the database connection details
+    set in the deployment environment.
 
-    # After:
-    Measurement.average(:temperature).class
-    # => Float
+    ```ruby
+    # ENV['DATABASE_URL'] = "mysql://localhost/example_database"
+    config.active_record.protocol_adapters.mysql = "trilogy"
+    # will connect to MySQL using the trilogy adapter
     ```
 
-    Before this change, Rails just called `to_d` on average aggregates from the
-    database adapter. This is not the case anymore. If you relied on that kind
-    of magic, you now need to register your own `ActiveRecord::Type`
-    (see `ActiveRecord::Attributes::ClassMethods` for documentation).
-
-    *Josua Schmid*
-
-*   PostgreSQL: introduce `ActiveRecord::ConnectionAdapters::PostgreSQLAdapter.datetime_type`.
-
-    This setting controls what native type Active Record should use when you call `datetime` in
-    a migration or schema. It takes a symbol which must correspond to one of the configured
-    `NATIVE_DATABASE_TYPES`. The default is `:timestamp`, meaning `t.datetime` in a migration
-    will create a "timestamp without time zone" column. To use "timestamp with time zone",
-    change this to `:timestamptz` in an initializer.
-
-    You should run `bin/rails db:migrate` to rebuild your schema.rb if you change this.
+    *Jean Boussier*, *Kevin McPhillips*
 
-    *Alex Ghiculescu*
+*   In cases where MySQL returns `warning_count` greater than zero, but returns no warnings when
+    the `SHOW WARNINGS` query is executed, `ActiveRecord.db_warnings_action` proc will still be
+    called with a generic warning message rather than silently ignoring the warning(s).
 
-*   PostgreSQL: handle `timestamp with time zone` columns correctly in `schema.rb`.
+    *Kevin McPhillips*
 
-    Previously they dumped as `t.datetime :column_name`, now they dump as `t.timestamptz :column_name`,
-    and are created as `timestamptz` columns when the schema is loaded.
+*   `DatabaseConfigurations#configs_for` accepts a symbol in the `name` parameter.
 
-    *Alex Ghiculescu*
+    *Andrew Novoselac*
 
-*   Removing trailing whitespace when matching columns in
-    `ActiveRecord::Sanitization.disallow_raw_sql!`.
+*   Fix `where(field: values)` queries when `field` is a serialized attribute
+    (for example, when `field` uses `ActiveRecord::Base.serialize` or is a JSON
+    column).
 
-    *Gannon McGibbon*, *Adrian Hirt*
+    *João Alves*
 
-*   Expose a way for applications to set a `primary_abstract_class`.
+*   Make the output of `ActiveRecord::Core#inspect` configurable.
 
-    Multiple database applications that use a primary abstract class that is not
-    named `ApplicationRecord` can now set a specific class to be the `primary_abstract_class`.
+    By default, calling `inspect` on a record will yield a formatted string including just the `id`.
 
     ```ruby
-    class PrimaryApplicationRecord
-      self.primary_abstract_class
-    end
+    Post.first.inspect #=> "#<Post id: 1>"
     ```
 
-    When an application boots it automatically connects to the primary or first database in the
-    database configuration file. In a multiple database application that then call `connects_to`
-    needs to know that the default connection is the same as the `ApplicationRecord` connection.
-    However, some applications have a differently named `ApplicationRecord`. This prevents Active
-    Record from opening duplicate connections to the same database.
-
-    *Eileen M. Uchitelle*, *John Crepezzi*
-
-*   Support hash config for `structure_dump_flags` and `structure_load_flags` flags.
-    Now that Active Record supports multiple databases configuration,
-    we need a way to pass specific flags for dump/load databases since
-    the options are not the same for different adapters.
-    We can use in the original way:
+    The attributes to be included in the output of `inspect` can be configured with
+    `ActiveRecord::Core#attributes_for_inspect`.
 
     ```ruby
-    ActiveRecord::Tasks::DatabaseTasks.structure_dump_flags = ['--no-defaults', '--skip-add-drop-table']
-    # or
-    ActiveRecord::Tasks::DatabaseTasks.structure_dump_flags = '--no-defaults --skip-add-drop-table'
+    Post.attributes_for_inspect = [:id, :title]
+    Post.first.inspect #=> "#<Post id: 1, title: "Hello, World!">"
     ```
 
-    And also use it passing a hash, with one or more keys, where the key
-    is the adapter
+    With `attributes_for_inspect` set to `:all`, `inspect` will list all the record's attributes.
 
     ```ruby
-    ActiveRecord::Tasks::DatabaseTasks.structure_dump_flags = {
-      mysql2: ['--no-defaults', '--skip-add-drop-table'],
-      postgres: '--no-tablespaces'
-    }
+    Post.attributes_for_inspect = :all
+    Post.first.inspect #=> "#<Post id: 1, title: "Hello, World!", published_at: "2023-10-23 14:28:11 +0000">"
     ```
 
-    *Gustavo Gonzalez*
+    In `development` and `test` mode, `attributes_for_inspect` will be set to `:all` by default.
 
-*   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.
+    You can also call `full_inspect` to get an inspection with all the attributes.
 
-    Fixes #41137.
+    The attributes in `attribute_for_inspect` will also be used for `pretty_print`.
 
-    *Jonathan Bracy*
+    *Andrew Novoselac*
 
-*   Allow to opt-out of `strict_loading` mode on a per-record base.
+*   Don't mark attributes as changed when reassigned to `Float::INFINITY` or
+    `-Float::INFINITY`.
 
-    This is useful when strict loading is enabled application wide or on a
-    model level.
+    *Maicol Bentancor*
 
-    ```ruby
-    class User < ApplicationRecord
-      has_many :bookmarks
-      has_many :articles, strict_loading: true
-    end
-
-    user = User.first
-    user.articles                        # => ActiveRecord::StrictLoadingViolationError
-    user.bookmarks                       # => #<ActiveRecord::Associations::CollectionProxy>
+*   Support the `RETURNING` clause for MariaDB.
 
-    user.strict_loading!(true)           # => true
-    user.bookmarks                       # => ActiveRecord::StrictLoadingViolationError
+    *fatkodima*, *Nikolay Kondratyev*
 
-    user.strict_loading!(false)          # => false
-    user.bookmarks                       # => #<ActiveRecord::Associations::CollectionProxy>
-    user.articles.strict_loading!(false) # => #<ActiveRecord::Associations::CollectionProxy>
-    ```
+*   The SQLite3 adapter now implements the `supports_deferrable_constraints?` contract.
 
-    *Ayrton De Craene*
-
-*   Add `FinderMethods#sole` and `#find_sole_by` to find and assert the
-    presence of exactly one record.
-
-    Used when you need a single row, but also want to assert that there aren't
-    multiple rows matching the condition; especially for when database
-    constraints aren't enough or are impractical.
+    Allows foreign keys to be deferred by adding the `:deferrable` key to the `foreign_key` options.
 
     ```ruby
-    Product.where(["price = %?", price]).sole
-    # => ActiveRecord::RecordNotFound      (if no Product with given price)
-    # => #<Product ...>                    (if one Product with given price)
-    # => ActiveRecord::SoleRecordExceeded  (if more than one Product with given price)
-
-    user.api_keys.find_sole_by(key: key)
-    # as above
+    add_reference :person, :alias, foreign_key: { deferrable: :deferred }
+    add_reference :alias, :person, foreign_key: { deferrable: :deferred }
     ```
 
-    *Asherah Connor*
+    *Stephen Margheim*
 
-*   Makes `ActiveRecord::AttributeMethods::Query` respect the getter overrides defined in the model.
-
-    Before:
+*   Add the `set_constraints` helper to PostgreSQL connections.
 
     ```ruby
-    class User
-      def admin
-        false # Overriding the getter to always return false
-      end
-    end
-
-    user = User.first
-    user.update(admin: true)
-
-    user.admin # false (as expected, due to the getter overwrite)
-    user.admin? # true (not expected, returned the DB column value)
-    ```
-
-    After this commit, `user.admin?` above returns false, as expected.
-
-    Fixes #40771.
-
-    *Felipe*
-
-*   Allow delegated_type to be specified primary_key and foreign_key.
+    Post.create!(user_id: -1) # => ActiveRecord::InvalidForeignKey
 
-    Since delegated_type assumes that the foreign_key ends with `_id`,
-    `singular_id` defined by it does not work when the foreign_key does
-    not end with `id`. This change fixes it by taking into account
-    `primary_key` and `foreign_key` in the options.
-
-    *Ryota Egusa*
-
-*   Expose an `invert_where` method that will invert all scope conditions.
-
-    ```ruby
-    class User
-      scope :active, -> { where(accepted: true, locked: false) }
+    Post.transaction do
+      Post.connection.set_constraints(:deferred)
+      p = Post.create!(user_id: -1)
+      u = User.create!
+      p.user = u
+      p.save!
     end
-
-    User.active
-    # ... WHERE `accepted` = 1 AND `locked` = 0
-
-    User.active.invert_where
-    # ... WHERE NOT (`accepted` = 1 AND `locked` = 0)
     ```
 
-    *Kevin Deisz*
+    *Cody Cutrer*
 
-*   Restore possibility of passing `false` to :polymorphic option of `belongs_to`.
+*   Include `ActiveModel::API` in `ActiveRecord::Base`.
 
-    Previously, passing `false` would trigger the option validation logic
-    to throw an error saying :polymorphic would not be a valid option.
+    *Sean Doyle*
 
-    *glaszig*
+*   Ensure `#signed_id` outputs `url_safe` strings.
 
-*   Remove deprecated `database` kwarg from `connected_to`.
+    *Jason Meller*
 
-    *Eileen M. Uchitelle*, *John Crepezzi*
+*   Add `nulls_last` and working `desc.nulls_first` for MySQL.
 
-*   Allow adding nonnamed expression indexes to be revertible.
+    *Tristan Fellows*
 
-    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.
+*   Allow for more complex hash arguments for `order` which mimics `where` in `ActiveRecord::Relation`.
 
     ```ruby
-    add_index(:items, "to_tsvector('english', description)")
+    Topic.includes(:posts).order(posts: { created_at: :desc })
     ```
 
-    Fixes #40732.
-
-    *fatkodima*
-
-*   Only warn about negative enums if a positive form that would cause conflicts exists.
-
-    Fixes #39065.
-
-    *Alex Ghiculescu*
-
-*   Add option to run `default_scope` on all queries.
-
-    Previously, a `default_scope` would only run on select or insert queries. In some cases, like non-Rails tenant sharding solutions, it may be desirable to run `default_scope` on all queries in order to ensure queries are including a foreign key for the shard (i.e. `blog_id`).
-
-    Now applications can add an option to run on all queries including select, insert, delete, and update by adding an `all_queries` option to the default scope definition.
-
-    ```ruby
-    class Article < ApplicationRecord
-      default_scope -> { where(blog_id: Current.blog.id) }, all_queries: true
-    end
-    ```
-
-    *Eileen M. Uchitelle*
-
-*   Add `where.associated` to check for the presence of an association.
-
-    ```ruby
-    # Before:
-    account.users.joins(:contact).where.not(contact_id: nil)
-
-    # After:
-    account.users.where.associated(:contact)
-    ```
-
-    Also mirrors `where.missing`.
-
-    *Kasper Timm Hansen*
-
-*   Allow constructors (`build_association` and `create_association`) on
-    `has_one :through` associations.
-
-    *Santiago Perez Perret*
-
+    *Myles Boone*
 
-Please check [6-1-stable](https://github.com/rails/rails/blob/6-1-stable/activerecord/CHANGELOG.md) for previous changes.
+Please check [7-1-stable](https://github.com/rails/rails/blob/7-1-stable/activerecord/CHANGELOG.md) for previous changes.