activerecord 5.2.8.1 → 6.1.0

data/CHANGELOG.md

@@ -1,1084 +1,1303 @@
-## Rails 5.2.8.1 (July 12, 2022) ##
-
-*   Change ActiveRecord::Coders::YAMLColumn default to safe_load
-
-    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:
-    
-    ```
-    config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]
-    ```
+## Rails 6.1.0 (December 09, 2020) ##
 
-    [CVE-2022-32224]
+*   Only warn about negative enums if a positive form that would cause conflicts exists.
 
+    Fixes #39065.
 
-## Rails 5.2.8 (May 09, 2022) ##
+    *Alex Ghiculescu*
 
-*   No changes.
+*   Change `attribute_for_inspect` to take `filter_attributes` in consideration.
 
+    *Rafael Mendonça França*
 
-## Rails 5.2.7.1 (April 26, 2022) ##
+*   Fix odd behavior of inverse_of with multiple belongs_to to same class.
 
-*   No changes.
+    Fixes #35204.
 
+    *Tomoyuki Kai*
 
-## Rails 5.2.7 (March 10, 2022) ##
+*   Build predicate conditions with objects that delegate `#id` and primary key:
 
-*   No changes.
+    ```ruby
+    class AdminAuthor
+      delegate_missing_to :@author
 
+      def initialize(author)
+        @author = author
+      end
+    end
 
-## Rails 5.2.6.3 (March 08, 2022) ##
+    Post.where(author: AdminAuthor.new(author))
+    ```
 
-*   No changes.
+    *Sean Doyle*
 
+*   Add `connected_to_many` API.
 
-## Rails 5.2.6.2 (February 11, 2022) ##
+    This API allows applications to connect to multiple databases at once without switching all of them or implementing a deeply nested stack.
 
-*   No changes.
+    Before:
 
+      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
 
-## Rails 5.2.6.1 (February 11, 2022) ##
+    After:
 
-*   No changes.
+      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
 
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-## Rails 5.2.6 (May 05, 2021) ##
+*   Add option to raise or log for `ActiveRecord::StrictLoadingViolationError`.
 
-*   No changes.
+    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.
 
+    Set `config.active_record.action_on_strict_loading_violation` to `:log` errors instead of raising.
 
-## Rails 5.2.5 (March 26, 2021) ##
+    *Eileen M. Uchitelle*
 
-*   No changes.
+*   Allow the inverse of a `has_one` association that was previously autosaved to be loaded.
 
+    Fixes #34255.
 
-## Rails 5.2.4.6 (May 05, 2021) ##
+    *Steven Weber*
 
-*   No changes.
+*   Optimise the length of index names for polymorphic references by using the reference name rather than the type and id column names.
 
+    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.
 
-## Rails 5.2.4.5 (February 10, 2021) ##
+    This change reduces the chance of that happening by using the reference name, e.g. `index_my_table_on_my_reference`.
 
-*   Fix possible DoS vector in PostgreSQL money type
+    Fixes #38655.
 
-    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.
+    *Luke Redpath*
 
-    Thanks to @dee-see from Hackerone for this patch!
+*   MySQL: Uniqueness validator now respects default database collation,
+    no longer enforce case sensitive comparison by default.
 
-    [CVE-2021-22880]
+    *Ryuta Kamizono*
 
-    *Aaron Patterson*
+*   Remove deprecated methods from `ActiveRecord::ConnectionAdapters::DatabaseLimits`.
 
+    `column_name_length`
+    `table_name_length`
+    `columns_per_table`
+    `indexes_per_table`
+    `columns_per_multicolumn_index`
+    `sql_query_length`
+    `joins_per_query`
 
-## Rails 5.2.4.4 (September 09, 2020) ##
+    *Rafael Mendonça França*
 
-*   No changes.
+*   Remove deprecated `ActiveRecord::ConnectionAdapters::AbstractAdapter#supports_multi_insert?`.
 
+    *Rafael Mendonça França*
 
-## Rails 5.2.4.3 (May 18, 2020) ##
+*   Remove deprecated `ActiveRecord::ConnectionAdapters::AbstractAdapter#supports_foreign_keys_in_create?`.
 
-*   No changes.
+    *Rafael Mendonça França*
 
-## Rails 5.2.4.2 (March 19, 2020) ##
+*   Remove deprecated `ActiveRecord::ConnectionAdapters::PostgreSQLAdapter#supports_ranges?`.
 
-*   No changes.
+    *Rafael Mendonça França*
 
+*   Remove deprecated `ActiveRecord::Base#update_attributes` and `ActiveRecord::Base#update_attributes!`.
 
-## Rails 5.2.4.1 (December 18, 2019) ##
+    *Rafael Mendonça França*
 
-*   No changes.
+*   Remove deprecated `migrations_path` argument in `ActiveRecord::ConnectionAdapter::SchemaStatements#assume_migrated_upto_version`.
 
+    *Rafael Mendonça França*
 
-## Rails 5.2.4 (November 27, 2019) ##
+*   Remove deprecated `config.active_record.sqlite3.represent_boolean_as_integer`.
 
-*   Fix circular `autosave: true` causes invalid records to be saved.
+    *Rafael Mendonça França*
 
-    Prior to the fix, when there was a circular series of `autosave: true`
-    associations, the callback for a `has_many` association was run while
-    another instance of the same callback on the same association hadn't
-    finished running. When control returned to the first instance of the
-    callback, the instance variable had changed, and subsequent associated
-    records weren't saved correctly. Specifically, the ID field for the
-    `belongs_to` corresponding to the `has_many` was `nil`.
+*   `relation.create` does no longer leak scope to class level querying methods
+    in initialization block and callbacks.
 
-    Fixes #28080.
+    Before:
 
-    *Larry Reid*
+        User.where(name: "John").create do |john|
+          User.find_by(name: "David") # => nil
+        end
 
-*   PostgreSQL: Fix GROUP BY with ORDER BY virtual count attribute.
+    After:
 
-    Fixes #36022.
+        User.where(name: "John").create do |john|
+          User.find_by(name: "David") # => #<User name: "David", ...>
+        end
 
     *Ryuta Kamizono*
 
-*   Fix sqlite3 collation parsing when using decimal columns.
+*   Named scope chain does no longer leak scope to class level querying methods.
 
-    *Martin R. Schuster*
-
-*   Make ActiveRecord `ConnectionPool.connections` method thread-safe.
+        class User < ActiveRecord::Base
+          scope :david, -> { User.where(name: "David") }
+        end
 
-    Fixes #36465.
+    Before:
 
-    *Jeff Doering*
+        User.where(name: "John").david
+        # SELECT * FROM users WHERE name = 'John' AND name = 'David'
 
-*   Assign all attributes before calling `build` to ensure the child record is visible in
-    `before_add` and `after_add` callbacks for `has_many :through` associations.
+    After:
 
-    Fixes #33249.
+        User.where(name: "John").david
+        # SELECT * FROM users WHERE name = 'David'
 
-    *Ryan H. Kerr*
+    *Ryuta Kamizono*
 
+*   Remove deprecated methods from `ActiveRecord::DatabaseConfigurations`.
 
-## Rails 5.2.3 (March 27, 2019) ##
+    `fetch`
+    `each`
+    `first`
+    `values`
+    `[]=`
 
-*   Fix different `count` calculation when using `size` with manual `select` with DISTINCT.
+    *Rafael Mendonça França*
 
-    Fixes #35214.
+*   `where.not` now generates NAND predicates instead of NOR.
 
-    *Juani Villarejo*
+     Before:
 
-*   Fix prepared statements caching to be enabled even when query caching is enabled.
+         User.where.not(name: "Jon", role: "admin")
+         # SELECT * FROM users WHERE name != 'Jon' AND role != 'admin'
 
-    *Ryuta Kamizono*
+     After:
 
-*   Don't allow `where` with invalid value matches to nil values.
+         User.where.not(name: "Jon", role: "admin")
+         # SELECT * FROM users WHERE NOT (name == 'Jon' AND role == 'admin')
 
-    Fixes #33624.
+    *Rafael Mendonça França*
 
-    *Ryuta Kamizono*
+*   Remove deprecated `ActiveRecord::Result#to_hash` method.
 
-*   Restore an ability that class level `update` without giving ids.
+    *Rafael Mendonça França*
 
-    Fixes #34743.
+*   Deprecate `ActiveRecord::Base.allow_unsafe_raw_sql`.
 
-    *Ryuta Kamizono*
+    *Rafael Mendonça França*
 
-*   Fix join table column quoting with SQLite.
+*   Remove deprecated support for using unsafe raw SQL in `ActiveRecord::Relation` methods.
 
-    *Gannon McGibbon*
+    *Rafael Mendonça França*
 
-*   Ensure that `delete_all` on collection proxy returns affected count.
+*   Allow users to silence the "Rails couldn't infer whether you are using multiple databases..."
+    message using `config.active_record.suppress_multiple_database_warning`.
 
-    *Ryuta Kamizono*
+    *Omri Gabay*
 
-*   Reset scope after delete on collection association to clear stale offsets of removed records.
+*   Connections can be granularly switched for abstract classes when `connected_to` is called.
 
-    *Gannon McGibbon*
+    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.
 
+    Example usage:
 
-## Rails 5.2.2.1 (March 11, 2019) ##
+    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`.
 
-*   No changes.
+    ```ruby
+    ActiveRecord::Base.connected_to(role: :reading) do
+      User.first # reads from default replica
+      Dog.first # reads from default replica
 
+      AnimalsRecord.connected_to(role: :writing, shard: :one) do
+        User.first # reads from default replica
+        Dog.first # reads from shard one primary
+      end
 
-## Rails 5.2.2 (December 04, 2018) ##
+      User.first # reads from default replica
+      Dog.first # reads from default replica
 
-*   Do not ignore the scoping with query methods in the scope block.
+      ApplicationRecord.connected_to(role: :writing, shard: :two) do
+        User.first # reads from shard two primary
+        Dog.first # reads from default replica
+      end
+    end
+    ```
 
-    *Ryuta Kamizono*
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-*   Allow aliased attributes to be used in `#update_columns` and `#update`.
+*   Allow double-dash comment syntax when querying read-only databases
 
-    *Gannon McGibbon*
+    *James Adam*
 
-*   Allow spaces in postgres table names.
+*   Add `values_at` method.
 
-    Fixes issue where "user post" is misinterpreted as "\"user\".\"post\"" when quoting table names with the postgres
-    adapter.
+    Returns an array containing the values associated with the given methods.
 
-    *Gannon McGibbon*
+    ```ruby
+    topic = Topic.first
+    topic.values_at(:title, :author_name)
+    # => ["Budget", "Jason"]
+    ```
 
-*   Cached columns_hash fields should be excluded from ResultSet#column_types
+    Similar to `Hash#values_at` but on an Active Record instance.
 
-    PR #34528 addresses the inconsistent behaviour when attribute is defined for an ignored column. The following test
-    was passing for SQLite and MySQL, but failed for PostgreSQL:
+    *Guillaume Briday*
 
-    ```ruby
-    class DeveloperName < ActiveRecord::Type::String
-      def deserialize(value)
-        "Developer: #{value}"
-      end
-    end
+*   Fix `read_attribute_before_type_cast` to consider attribute aliases.
 
-    class AttributedDeveloper < ActiveRecord::Base
-      self.table_name = "developers"
+    *Marcelo Lauxen*
 
-      attribute :name, DeveloperName.new
+*   Support passing record to uniqueness validator `:conditions` callable:
 
-      self.ignored_columns += ["name"]
+    ```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
+    ```
+
+    *Eliot Sykes*
 
-    developer = AttributedDeveloper.create
-    developer.update_column :name, "name"
+*   `BatchEnumerator#update_all` and `BatchEnumerator#delete_all` now return the
+    total number of rows affected, just like their non-batched counterparts.
 
-    loaded_developer = AttributedDeveloper.where(id: developer.id).select("*").first
-    puts loaded_developer.name # should be "Developer: name" but it's just "name"
+    ```ruby
+    Person.in_batches.update_all("first_name = 'Eugene'") # => 42
+    Person.in_batches.delete_all # => 42
     ```
 
-    *Dmitry Tsepelev*
+    Fixes #40287.
 
-*   Values of enum are frozen, raising an error when attempting to modify them.
+    *Eugene Kenny*
 
-    *Emmanuel Byrd*
+*   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.
 
-*   `update_columns` now correctly raises `ActiveModel::MissingAttributeError`
-    if the attribute does not exist.
+    To use this in 6.1, you need to place the next string to your model file:
 
-    *Sean Griffin*
+        attribute :duration, :interval
 
-*   Do not use prepared statement in queries that have a large number of binds.
+    To keep old behavior until 6.2 is released:
 
-    *Ryuta Kamizono*
+        attribute :duration, :string
 
-*   Fix query cache to load before first request.
+    Example:
 
-    *Eileen M. Uchitelle*
+        create_table :events do |t|
+          t.string   :name
+          t.interval :duration
+        end
 
-*   Fix collection cache key with limit and custom select to avoid ambiguous timestamp column error.
+        class Event < ApplicationRecord
+          attribute :duration, :interval
+        end
 
-    Fixes #33056.
+        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
 
-    *Federico Martinez*
+    *Andrey Novikov*
 
-*   Fix duplicated record creation when using nested attributes with `create_with`.
+*   Allow associations supporting the `dependent:` key to take `dependent: :destroy_async`.
 
-    *Darwin Wu*
+    ```ruby
+    class Account < ActiveRecord::Base
+        belongs_to :supplier, dependent: :destroy_async
+    end
+    ```
 
-*   Fix regression setting children record in parent `before_save` callback.
+    `:destroy_async` will enqueue a job to destroy associated records in the background.
 
-    *Guo Xiang Tan*
+    *DHH*, *George Claghorn*, *Cory Gwin*, *Rafael Mendonça França*, *Adrianna Chang*
 
-*   Prevent leaking of user's DB credentials on `rails db:create` failure.
+*   Add `SKIP_TEST_DATABASE` environment variable to disable modifying the test database when `rails db:create` and `rails db:drop` are called.
 
-    *bogdanvlviv*
+    *Jason Schweier*
 
-*   Clear mutation tracker before continuing the around callbacks.
+*   `connects_to` can only be called on `ActiveRecord::Base` or abstract classes.
 
-    *Yuya Tanaka*
+    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.
 
-*   Prevent deadlocks when waiting for connection from pool.
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-    *Brent Wheeldon*
+*   All connection adapters `execute` now raises `ActiveRecord::ConnectionNotEstablished` rather than
+    `ActiveRecord::StatementInvalid` when they encounter a connection error.
 
-*   Avoid extra scoping when using `Relation#update` that was causing this method to change the current scope.
+    *Jean Boussier*
 
-    *Ryuta Kamizono*
+*   `Mysql2Adapter#quote_string` now raises `ActiveRecord::ConnectionNotEstablished` rather than
+    `ActiveRecord::StatementInvalid` when it can't connect to the MySQL server.
 
-*   Fix numericality validator not to be affected by custom getter.
+    *Jean Boussier*
 
-    *Ryuta Kamizono*
+*   Add support for check constraints that are `NOT VALID` via `validate: false` (PostgreSQL-only).
 
-*   Fix bulk change table ignores comment option on PostgreSQL.
+    *Alex Robbin*
 
-    *Yoshiyuki Kinjo*
+*   Ensure the default configuration is considered primary or first for an environment
 
+    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.
 
-## Rails 5.2.1.1 (November 27, 2018) ##
+    *Eileen M. Uchitelle*
 
-*   No changes.
+*   Allow `where` references association names as joined table name aliases.
 
+    ```ruby
+    class Comment < ActiveRecord::Base
+      enum label: [:default, :child]
+      has_many :children, class_name: "Comment", foreign_key: :parent_id
+    end
 
-## Rails 5.2.1 (August 07, 2018) ##
+    # ... FROM comments LEFT OUTER JOIN comments children ON ... WHERE children.label = 1
+    Comment.includes(:children).where("children.label": "child")
+    ```
 
-*   PostgreSQL: Support new relkind for partitioned tables.
+    *Ryuta Kamizono*
 
-    Fixes #33008.
+*   Support storing demodulized class name for polymorphic type.
 
-    *Yannick Schutz*
+    Before Rails 6.1, storing demodulized class name is supported only for STI type
+    by `store_full_sti_class` class attribute.
 
-*   Rollback parent transaction when children fails to update.
+    Now `store_full_class_name` class attribute can handle both STI and polymorphic types.
 
-    *Guillaume Malette*
+    *Ryuta Kamizono*
 
-*   Fix default value for MySQL time types with specified precision.
+*   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.
 
-    *Nikolay Kondratyev*
+    *fatkodima*
+
+*   Respect the `select` values for eager loading.
 
-*   Fix `touch` option to behave consistently with `Persistence#touch` method.
+    ```ruby
+    post = Post.select("UPPER(title) AS title").first
+    post.title # => "WELCOME TO THE WEBLOG"
+    post.body  # => ActiveModel::MissingAttributeError
+
+    # 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"
+
+    # 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
+    ```
 
     *Ryuta Kamizono*
 
-*   Fix `save` in `after_create_commit` won't invoke extra `after_create_commit`.
+*   Allow attribute's default to be configured but keeping its own type.
 
-    Fixes #32831.
+    ```ruby
+    class Post < ActiveRecord::Base
+      attribute :written_at, default: -> { Time.now.utc }
+    end
 
-    *Ryuta Kamizono*
+    # Rails 6.0
+    Post.type_for_attribute(:written_at) # => #<Type::Value ... precision: nil, ...>
 
-*   Fix logic on disabling commit callbacks so they are not called unexpectedly when errors occur.
+    # Rails 6.1
+    Post.type_for_attribute(:written_at) # => #<Type::DateTime ... precision: 6, ...>
+    ```
 
-    *Brian Durand*
+    *Ryuta Kamizono*
 
-*   Fix parent record should not get saved with duplicate children records.
+*   Allow default to be configured for Enum.
 
-    Fixes #32940.
+    ```ruby
+    class Book < ActiveRecord::Base
+      enum status: [:proposed, :written, :published], _default: :published
+    end
 
-    *Santosh Wadghule*
+    Book.new.status # => "published"
+    ```
 
-*   Fix that association's after_touch is not called with counter cache.
+    *Ryuta Kamizono*
 
-    Fixes #31559.
+*   Deprecate YAML loading from legacy format older than Rails 5.0.
 
     *Ryuta Kamizono*
 
-*   `becomes` should clear the mutation tracker which is created in `after_initialize`.
+*   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.
+
+    *Sean Griffin*, *Ryuta Kamizono*
 
-    Fixes #32867.
+*   Deprecate `map!` and `collect!` on `ActiveRecord::Result`.
 
     *Ryuta Kamizono*
 
-*   Allow a belonging to parent object to be created from a new record.
+*   Support `relation.and` for intersection as Set theory.
 
-    *Jolyon Pawlyn*
+    ```ruby
+    david_and_mary = Author.where(id: [david, mary])
+    mary_and_bob   = Author.where(id: [mary, bob])
 
-*   Fix that building record with assigning multiple has_one associations
-    wrongly persists through record.
+    david_and_mary.merge(mary_and_bob) # => [mary, bob]
 
-    Fixes #32511.
+    david_and_mary.and(mary_and_bob) # => [mary]
+    david_and_mary.or(mary_and_bob)  # => [david, mary, bob]
+    ```
 
-    *Sam DeCesare*
+    *Ryuta Kamizono*
 
-*   Fix relation merging when one of the relations is going to skip the
-    query cache.
+*   Merging conditions on the same column no longer maintain both conditions,
+    and will be consistently replaced by the latter condition in Rails 6.2.
+    To migrate to Rails 6.2's behavior, use `relation.merge(other, rewhere: true)`.
 
-    *James Williams*
+    ```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 5.2.0 (April 09, 2018) ##
+    # Rails 6.1 with rewhere to migrate to Rails 6.2's behavior
+    Author.where(id: david.id..mary.id).merge(Author.where(id: bob), rewhere: true) # => [bob]
 
-*   MySQL: Support mysql2 0.5.x.
+    # Rails 6.2 (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]
+    ```
 
-    *Aaron Stone*
+    *Ryuta Kamizono*
 
-*   Apply time column precision on assignment.
+*   Do not mark Postgresql MAC address and UUID attributes as changed when the assigned value only varies by case.
 
-    PR #20317 changed the behavior of datetime columns so that when they
-    have a specified precision then on assignment the value is rounded to
-    that precision. This behavior is now applied to time columns as well.
+    *Peter Fry*
 
-    Fixes #30301.
+*   Resolve issue with insert_all unique_by option when used with expression index.
 
-    *Andrew White*
+    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.
 
-*   Normalize time column values for SQLite database.
+    Usage:
 
-    For legacy reasons, time columns in SQLite are stored as full datetimes
-    because until #24542 the quoting for time columns didn't remove the date
-    component. To ensure that values are consistent we now normalize the
-    date component to 2001-01-01 on reading and writing.
+    ```ruby
+    create_table :books, id: :integer, force: true do |t|
+      t.column :name, :string
+      t.index "lower(name)", unique: true
+    end
 
-    *Andrew White*
+    Book.insert_all [{ name: "MyTest" }], unique_by: :index_books_on_lower_name
+    ```
 
-*   Ensure that the date component is removed when quoting times.
+    Fixes #39516.
 
-    PR #24542 altered the quoting for time columns so that the date component
-    was removed however it only removed it when it was 2001-01-01. Now the
-    date component is removed irrespective of what the date is.
+    *Austen Madden*
 
-    *Andrew White*
+*   Add basic support for CHECK constraints to database migrations.
 
-*   Fix `dependent: :destroy` issue for has_one/belongs_to relationship where
-    the parent class was getting deleted when the child was not.
+    Usage:
 
-    Fixes #32022.
+    ```ruby
+    add_check_constraint :products, "price > 0", name: "price_check"
+    remove_check_constraint :products, name: "price_check"
+    ```
 
-    *Fernando Gorodscy*
+    *fatkodima*
 
-*   Whitelist `NULLS FIRST` and `NULLS LAST` in order clauses too.
+*   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.
 
-    *Xavier Noria*
+    Usage:
 
-*   Fix that after commit callbacks on update does not triggered when optimistic locking is enabled.
+    ```ruby
+    class Developer < ApplicationRecord
+      self.strict_loading_by_default = true
 
-    *Ryuta Kamizono*
+      has_many :projects
+    end
 
-*   Fix `#columns_for_distinct` of MySQL and PostgreSQL to make
-    `ActiveRecord::FinderMethods#limited_ids_for` use correct primary key values
-    even if `ORDER BY` columns include other table's primary key.
+    dev = Developer.first
+    dev.projects.first
+    # => ActiveRecord::StrictLoadingViolationError Exception: Developer is marked as strict_loading and Project cannot be lazily loaded.
+    ```
 
-    Fixes #28364.
+    *bogdanvlviv*
 
-    *Takumi Kagiyama*
+*   Deprecate passing an Active Record object to `quote`/`type_cast` directly.
 
-*   Make `reflection.klass` raise if `polymorphic?` not to be misused.
+    *Ryuta Kamizono*
 
-    Fixes #31876.
+*   Default engine `ENGINE=InnoDB` is no longer dumped to make schema more agnostic.
 
-    *Ryuta Kamizono*
+    Before:
 
-*   PostgreSQL: Allow pg-1.0 gem to be used with Active Record.
+    ```ruby
+    create_table "accounts", options: "ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci", force: :cascade do |t|
+    end
+    ```
 
-    *Lars Kanis*
+    After:
 
-*   Deprecate `expand_hash_conditions_for_aggregates` without replacement.
-    Using a `Relation` for performing queries is the prefered API.
+    ```ruby
+    create_table "accounts", charset: "utf8mb4", collation: "utf8mb4_0900_ai_ci", force: :cascade do |t|
+    end
+    ```
 
     *Ryuta Kamizono*
 
-*   Fix not expanded problem when passing an Array object as argument to the where method using `composed_of` column.
+*   Added delegated type as an alternative to single-table inheritance for representing class hierarchies.
+    See ActiveRecord::DelegatedType for the full description.
 
-    ```
-    david_balance = customers(:david).balance
-    Customer.where(balance: [david_balance]).to_sql
+    *DHH*
+
+*   Deprecate aggregations with group by duplicated fields.
+
+    To migrate to Rails 6.2's behavior, use `uniq!(:group)` to deduplicate group fields.
 
-    # Before: WHERE `customers`.`balance` = NULL
-    # After : WHERE `customers`.`balance` = 50
+    ```ruby
+    accounts = Account.group(:firm_id)
+
+    # duplicated group fields, deprecated.
+    accounts.merge(accounts.where.not(credit_limit: nil)).sum(:credit_limit)
+    # => {
+    #   [1, 1] => 50,
+    #   [2, 2] => 60
+    # }
+
+    # use `uniq!(:group)` to deduplicate group fields.
+    accounts.merge(accounts.where.not(credit_limit: nil)).uniq!(:group).sum(:credit_limit)
+    # => {
+    #   1 => 50,
+    #   2 => 60
+    # }
     ```
 
-    Fixes #31723.
+    *Ryuta Kamizono*
 
-    *Yutaro Kanagawa*
+*   Deprecate duplicated query annotations.
 
-*   Fix `count(:all)` with eager loading and having an order other than the driving table.
+    To migrate to Rails 6.2's behavior, use `uniq!(:annotate)` to deduplicate query annotations.
 
-    Fixes #31783.
+    ```ruby
+    accounts = Account.where(id: [1, 2]).annotate("david and mary")
+
+    # duplicated annotations, deprecated.
+    accounts.merge(accounts.rewhere(id: 3))
+    # SELECT accounts.* FROM accounts WHERE accounts.id = 3 /* david and mary */ /* david and mary */
+
+    # 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 */
+    ```
 
     *Ryuta Kamizono*
 
-*   Clear the transaction state when an Active Record object is duped.
+*   Resolve conflict between counter cache and optimistic locking.
 
-    Fixes #31670.
+    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.
 
-    *Yuriy Ustushenko*
+    Fixes #16449.
 
-*   Support for PostgreSQL foreign tables.
+    *Aaron Lipman*
 
-    *fatkodima*
+*   Support merging option `:rewhere` to allow mergee side condition to be replaced exactly.
 
-*   Fix relation merger issue with `left_outer_joins`.
+    ```ruby
+    david_and_mary = Author.where(id: david.id..mary.id)
 
-    *Mehmet Emin İNAÇ*
+    # both conflict conditions exists
+    david_and_mary.merge(Author.where(id: bob)) # => []
 
-*   Don't allow destroyed object mutation after `save` or `save!` is called.
+    # mergee side condition is replaced by rewhere
+    david_and_mary.merge(Author.rewhere(id: bob)) # => [bob]
+
+    # mergee side condition is replaced by rewhere option
+    david_and_mary.merge(Author.where(id: bob), rewhere: true) # => [bob]
+    ```
 
     *Ryuta Kamizono*
 
-*   Take into account association conditions when deleting through records.
+*   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.
 
-    Fixes #18424.
+    ```ruby
+    signed_id = User.first.signed_id expires_in: 15.minutes, purpose: :password_reset
 
-    *Piotr Jakubowski*
+    User.find_signed signed_id # => nil, since the purpose does not match
 
-*   Fix nested `has_many :through` associations on unpersisted parent instances.
+    travel 16.minutes
+    User.find_signed signed_id, purpose: :password_reset # => nil, since the signed id has expired
 
-    For example, if you have
+    travel_back
+    User.find_signed signed_id, purpose: :password_reset # => User.first
 
-        class Post < ActiveRecord::Base
-          belongs_to :author
-          has_many :books, through: :author
-          has_many :subscriptions, through: :books
-        end
+    User.find_signed! "bad data" # => ActiveSupport::MessageVerifier::InvalidSignature
+    ```
 
-        class Author < ActiveRecord::Base
-          has_one :post
-          has_many :books
-          has_many :subscriptions, through: :books
-        end
+    *DHH*
 
-        class Book < ActiveRecord::Base
-          belongs_to :author
-          has_many :subscriptions
-        end
+*   Support `ALGORITHM = INSTANT` DDL option for index operations on MySQL.
 
-        class Subscription < ActiveRecord::Base
-          belongs_to :book
-        end
+    *Ryuta Kamizono*
 
-    Before:
+*   Fix index creation to preserve index comment in bulk change table on MySQL.
 
-    If `post` is not persisted, then `post.subscriptions` will be empty.
+    *Ryuta Kamizono*
 
-    After:
+*   Allow `unscope` to be aware of table name qualified values.
 
-    If `post` is not persisted, then `post.subscriptions` can be set and used
-    just like it would if `post` were persisted.
+    It is possible to unscope only the column in the specified table.
 
-    Fixes #16313.
+    ```ruby
+    posts = Post.joins(:comments).group(:"posts.hidden")
+    posts = posts.where("posts.hidden": false, "comments.hidden": false)
 
-    *Zoltan Kiss*
+    posts.count
+    # => { false => 10 }
 
-*   Fixed inconsistency with `first(n)` when used with `limit()`.
-    The `first(n)` finder now respects the `limit()`, making it consistent
-    with `relation.to_a.first(n)`, and also with the behavior of `last(n)`.
+    # unscope both hidden columns
+    posts.unscope(where: :hidden).count
+    # => { false => 11, true => 1 }
 
-    Fixes #23979.
+    # unscope only comments.hidden column
+    posts.unscope(where: :"comments.hidden").count
+    # => { false => 11 }
+    ```
 
-    *Brian Christian*
+    *Ryuta Kamizono*, *Slava Korolev*
 
-*   Use `count(:all)` in `HasManyAssociation#count_records` to prevent invalid
-    SQL queries for association counting.
+*   Fix `rewhere` to truly overwrite collided where clause by new where clause.
 
-    *Klas Eskilson*
+    ```ruby
+    steve = Person.find_by(name: "Steve")
+    david = Author.find_by(name: "David")
 
-*   Fix to invoke callbacks when using `update_attribute`.
+    relation = Essay.where(writer: steve)
 
-    *Mike Busch*
+    # Before
+    relation.rewhere(writer: david).to_a # => []
 
-*   Fix `count(:all)` to correctly work `distinct` with custom SELECT list.
+    # After
+    relation.rewhere(writer: david).to_a # => [david]
+    ```
 
     *Ryuta Kamizono*
 
-*   Using subselect for `delete_all` with `limit` or `offset`.
+*   Inspect time attributes with subsec and time zone offset.
+
+    ```ruby
+    p Knot.create
+    => #<Knot id: 1, created_at: "2016-05-05 01:29:47.116928000 +0000">
+    ```
+
+    *akinomaeni*, *Jonathan Hefner*
+
+*   Deprecate passing a column to `type_cast`.
 
     *Ryuta Kamizono*
 
-*   Undefine attribute methods on descendants when resetting column
-    information.
+*   Deprecate `in_clause_length` and `allowed_index_name_length` in `DatabaseLimits`.
 
-    *Chris Salzberg*
+    *Ryuta Kamizono*
 
-*   Log database query callers.
+*   Support bulk insert/upsert on relation to preserve scope values.
 
-    Add `verbose_query_logs` configuration option to display the caller
-    of database queries in the log to facilitate N+1 query resolution
-    and other debugging.
+    *Josef Šimánek*, *Ryuta Kamizono*
 
-    Enabled in development only for new and upgraded applications. Not
-    recommended for use in the production environment since it relies
-    on Ruby's `Kernel#caller_locations` which is fairly slow.
+*   Preserve column comment value on changing column name on MySQL.
 
-    *Olivier Lacan*
+    *Islam Taha*
 
-*   Fix conflicts `counter_cache` with `touch: true` by optimistic locking.
+*   Add support for `if_exists` option for removing an index.
 
-    ```
-    # create_table :posts do |t|
-    #   t.integer :comments_count, default: 0
-    #   t.integer :lock_version
-    #   t.timestamps
-    # end
-    class Post < ApplicationRecord
-    end
+    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.
 
-    # create_table :comments do |t|
-    #   t.belongs_to :post
-    # end
-    class Comment < ApplicationRecord
-      belongs_to :post, touch: true, counter_cache: true
-    end
-    ```
+    *Eileen M. Uchitelle*
 
-    Before:
-    ```
-    post = Post.create!
-    # => begin transaction
-         INSERT INTO "posts" ("created_at", "updated_at", "lock_version")
-         VALUES ("2017-12-11 21:27:11.387397", "2017-12-11 21:27:11.387397", 0)
-         commit transaction
-
-    comment = Comment.create!(post: post)
-    # => begin transaction
-         INSERT INTO "comments" ("post_id") VALUES (1)
-
-         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) + 1,
-         "lock_version" = COALESCE("lock_version", 0) + 1 WHERE "posts"."id" = 1
-
-         UPDATE "posts" SET "updated_at" = '2017-12-11 21:27:11.398330',
-         "lock_version" = 1 WHERE "posts"."id" = 1 AND "posts"."lock_version" = 0
-         rollback transaction
-    # => ActiveRecord::StaleObjectError: Attempted to touch a stale object: Post.
-
-    Comment.take.destroy!
-    # => begin transaction
-         DELETE FROM "comments" WHERE "comments"."id" = 1
-
-         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) - 1,
-         "lock_version" = COALESCE("lock_version", 0) + 1 WHERE "posts"."id" = 1
-
-         UPDATE "posts" SET "updated_at" = '2017-12-11 21:42:47.785901',
-         "lock_version" = 1 WHERE "posts"."id" = 1 AND "posts"."lock_version" = 0
-         rollback transaction
-    # => ActiveRecord::StaleObjectError: Attempted to touch a stale object: Post.
-    ```
+*   Remove ibm_db, informix, mssql, oracle, and oracle12 Arel visitors which are not used in the code base.
 
-    After:
-    ```
-    post = Post.create!
-    # => begin transaction
-         INSERT INTO "posts" ("created_at", "updated_at", "lock_version")
-         VALUES ("2017-12-11 21:27:11.387397", "2017-12-11 21:27:11.387397", 0)
-         commit transaction
-
-    comment = Comment.create!(post: post)
-    # => begin transaction
-         INSERT INTO "comments" ("post_id") VALUES (1)
-
-         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) + 1,
-         "lock_version" = COALESCE("lock_version", 0) + 1,
-         "updated_at" = '2017-12-11 21:37:09.802642' WHERE "posts"."id" = 1
-         commit transaction
-
-    comment.destroy!
-    # => begin transaction
-         DELETE FROM "comments" WHERE "comments"."id" = 1
-
-         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) - 1,
-         "lock_version" = COALESCE("lock_version", 0) + 1,
-         "updated_at" = '2017-12-11 21:39:02.685520' WHERE "posts"."id" = 1
-         commit transaction
-    ```
+    *Ryuta Kamizono*
 
-    Fixes #31199.
+*   Prevent `build_association` from `touching` a parent record if the record isn't persisted for `has_one` associations.
 
-    *bogdanvlviv*
+    Fixes #38219.
 
-*   Add support for PostgreSQL operator classes to `add_index`.
+    *Josh Brody*
 
-    Example:
+*   Add support for `if_not_exists` option for adding index.
 
-        add_index :users, :name, using: :gist, opclass: { name: :gist_trgm_ops }
+    The `add_index` method respects `if_not_exists` option. If it is set to true
+    index won't be added.
 
-    *Greg Navis*
+    Usage:
 
-*   Don't allow scopes to be defined which conflict with instance methods on `Relation`.
+    ```ruby
+      add_index :users, :account_id, if_not_exists: true
+    ```
 
-    Fixes #31120.
+    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.
 
-    *kinnrot*
+    *Prathamesh Sonpatki*
 
-*   Add new error class `QueryCanceled` which will be raised
-    when canceling statement due to user request.
+*   Add `ActiveRecord::Base#previously_new_record?` to show if a record was new before the last save.
 
-    *Ryuta Kamizono*
+    *Tom Ward*
 
-*   Add `#up_only` to database migrations for code that is only relevant when
-    migrating up, e.g. populating a new column.
+*   Support descending order for `find_each`, `find_in_batches`, and `in_batches`.
 
-    *Rich Daley*
+    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.
 
-*   Require raw SQL fragments to be explicitly marked when used in
-    relation query methods.
+    This change allows reversing the order, batching from newest to oldest. This is useful when you need to process newer batches of records first.
 
-    Before:
-    ```
-    Article.order("LENGTH(title)")
-    ```
+    Pass `order: :desc` to yield batches in descending order. The default remains `order: :asc`.
 
-    After:
-    ```
-    Article.order(Arel.sql("LENGTH(title)"))
+    ```ruby
+    Person.find_each(order: :desc) do |person|
+      person.party_all_night!
+    end
     ```
 
-    This prevents SQL injection if applications use the [strongly
-    discouraged] form `Article.order(params[:my_order])`, under the
-    mistaken belief that only column names will be accepted.
+    *Alexey Vasiliev*
 
-    Raw SQL strings will now cause a deprecation warning, which will
-    become an UnknownAttributeReference error in Rails 6.0. Applications
-    can opt in to the future behavior by setting `allow_unsafe_raw_sql`
-    to `:disabled`.
+*   Fix `insert_all` with enum values.
 
-    Common and judged-safe string values (such as simple column
-    references) are unaffected:
-    ```
-    Article.order("title DESC")
-    ```
+    Fixes #38716.
 
-    *Ben Toews*
+    *Joel Blum*
 
-*   `update_all` will now pass its values to `Type#cast` before passing them to
-    `Type#serialize`. This means that `update_all(foo: 'true')` will properly
-    persist a boolean.
+*   Add support for `db:rollback:name` for multiple database applications.
 
-    *Sean Griffin*
+    Multiple database applications will now raise if `db:rollback` is call and recommend using the `db:rollback:[NAME]` to rollback migrations.
 
-*   Add new error class `StatementTimeout` which will be raised
-    when statement timeout exceeded.
+    *Eileen M. Uchitelle*
 
-    *Ryuta Kamizono*
+*   `Relation#pick` now uses already loaded results instead of making another query.
 
-*   Fix `bin/rails db:migrate` with specified `VERSION`.
-    `bin/rails db:migrate` with empty VERSION behaves as without `VERSION`.
-    Check a format of `VERSION`: Allow a migration version number
-    or name of a migration file. Raise error if format of `VERSION` is invalid.
-    Raise error if target migration doesn't exist.
+    *Eugene Kenny*
 
-    *bogdanvlviv*
+*   Deprecate using `return`, `break` or `throw` to exit a transaction block after writes.
 
-*   Fixed a bug where column orders for an index weren't written to
-    `db/schema.rb` when using the sqlite adapter.
+    *Dylan Thacker-Smith*
 
-    Fixes #30902.
+*   Dump the schema or structure of a database when calling `db:migrate:name`.
 
-    *Paul Kuruvilla*
+    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.
 
-*   Remove deprecated method `#sanitize_conditions`.
+    Going forward, calls to `rails db:migrate:name` will dump the schema (or structure) of the database being migrated.
 
-    *Rafael Mendonça França*
+    *Kyle Thompson*
 
-*   Remove deprecated method `#scope_chain`.
+*   Reset the `ActiveRecord::Base` connection after `rails db:migrate:name`.
 
-    *Rafael Mendonça França*
+    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.
 
-*   Remove deprecated configuration `.error_on_ignored_order_or_limit`.
+    *Kyle Thompson*
 
-    *Rafael Mendonça França*
+*   Disallow calling `connected_to` on subclasses of `ActiveRecord::Base`.
 
-*   Remove deprecated arguments from `#verify!`.
+    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.
 
-    *Rafael Mendonça França*
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-*   Remove deprecated argument `name` from `#indexes`.
+*   Add support for horizontal sharding to `connects_to` and `connected_to`.
 
-    *Rafael Mendonça França*
+    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.
 
-*   Remove deprecated method `ActiveRecord::Migrator.schema_migrations_table_name`.
+    Usage:
 
-    *Rafael Mendonça França*
+    Given the following configuration:
 
-*   Remove deprecated method `supports_primary_key?`.
+    ```yaml
+    # config/database.yml
+    production:
+      primary:
+        database: my_database
+      primary_shard_one:
+        database: my_database_shard_one
+    ```
 
-    *Rafael Mendonça França*
+    Connect to multiple shards:
 
-*   Remove deprecated method `supports_migrations?`.
+    ```ruby
+    class ApplicationRecord < ActiveRecord::Base
+      self.abstract_class = true
 
-    *Rafael Mendonça França*
+      connects_to shards: {
+        default: { writing: :primary },
+        shard_one: { writing: :primary_shard_one }
+      }
+    ```
 
-*   Remove deprecated methods `initialize_schema_migrations_table` and `initialize_internal_metadata_table`.
+    Swap between shards in your controller / model code:
 
-    *Rafael Mendonça França*
+    ```ruby
+    ActiveRecord::Base.connected_to(shard: :shard_one) do
+      # Read from shard one
+    end
+    ```
 
-*   Raises when calling `lock!` in a dirty record.
+    The horizontal sharding API also supports read replicas. See guides for more details.
 
-    *Rafael Mendonça França*
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-*   Remove deprecated support to passing a class to `:class_name` on associations.
+*   Deprecate `spec_name` in favor of `name` on database configurations.
 
-    *Rafael Mendonça França*
+    The accessors for `spec_name` on `configs_for` and `DatabaseConfig` are deprecated. Please use `name` instead.
 
-*   Remove deprecated argument `default` from `index_name_exists?`.
+    Deprecated behavior:
 
-    *Rafael Mendonça França*
+    ```ruby
+    db_config = ActiveRecord::Base.configs_for(env_name: "development", spec_name: "primary")
+    db_config.spec_name
+    ```
 
-*   Remove deprecated support to `quoted_id` when typecasting an Active Record object.
+    New behavior:
 
-    *Rafael Mendonça França*
+    ```ruby
+    db_config = ActiveRecord::Base.configs_for(env_name: "development", name: "primary")
+    db_config.name
+    ```
 
-*   Fix `bin/rails db:setup` and `bin/rails db:test:prepare` create wrong
-    ar_internal_metadata's data for a test database.
+    *Eileen M. Uchitelle*
+
+*   Add additional database-specific rake tasks for multi-database users.
+
+    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:
 
-    Before:
     ```
-    $ RAILS_ENV=test rails dbconsole
-    > SELECT * FROM ar_internal_metadata;
-    key|value|created_at|updated_at
-    environment|development|2017-09-11 23:14:10.815679|2017-09-11 23:14:10.815679
+    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
     ```
 
-    After:
+    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:
+
     ```
-    $ RAILS_ENV=test rails dbconsole
-    > SELECT * FROM ar_internal_metadata;
-    key|value|created_at|updated_at
-    environment|test|2017-09-11 23:14:10.815679|2017-09-11 23:14:10.815679
+    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
     ```
 
-    Fixes #26731.
+    *Kyle Thompson*
 
-    *bogdanvlviv*
+*   Add support for `strict_loading` mode on association declarations.
 
-*   Fix longer sequence name detection for serial columns.
+    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.
 
-    Fixes #28332.
+    Usage:
 
-    *Ryuta Kamizono*
+    ```ruby
+    class Developer < ApplicationRecord
+      has_many :projects, strict_loading: true
+    end
 
-*   MySQL: Don't lose `auto_increment: true` in the `db/schema.rb`.
+    dev = Developer.first
+    dev.projects.first
+    # => ActiveRecord::StrictLoadingViolationError: The projects association is marked as strict_loading and cannot be lazily loaded.
+    ```
 
-    Fixes #30894.
+    *Kevin Deisz*
 
-    *Ryuta Kamizono*
+*   Add support for `strict_loading` mode to prevent lazy loading of records.
 
-*   Fix `COUNT(DISTINCT ...)` for `GROUP BY` with `ORDER BY` and `LIMIT`.
+    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.
 
-    Fixes #30886.
+    Usage:
 
-    *Ryuta Kamizono*
+    ```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.
+    ```
 
-*   PostgreSQL `tsrange` now preserves subsecond precision.
+    *Eileen M. Uchitelle*, *Aaron Patterson*
 
-    PostgreSQL 9.1+ introduced range types, and Rails added support for using
-    this datatype in Active Record. However, the serialization of
-    `PostgreSQL::OID::Range` was incomplete, because it did not properly
-    cast the bounds that make up the range. This led to subseconds being
-    dropped in SQL commands:
+*   Add support for PostgreSQL 11+ partitioned indexes when using `upsert_all`.
 
-    Before:
+    *Sebastián Palma*
 
-        connection.type_cast(tsrange.serialize(range_value))
-        # => "[2010-01-01 13:30:00 UTC,2011-02-02 19:30:00 UTC)"
+*   Adds support for `if_not_exists` to `add_column` and `if_exists` to `remove_column`.
 
-    Now:
+    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.
 
-        connection.type_cast(tsrange.serialize(range_value))
-        # => "[2010-01-01 13:30:00.670277,2011-02-02 19:30:00.745125)"
+    Example Usage:
 
-    *Thomas Cannon*
+    ```ruby
+    class AddColumnTitle < ActiveRecord::Migration[6.1]
+      def change
+        add_column :posts, :title, :string, if_not_exists: true
+      end
+    end
+    ```
 
-*   Passing a `Set` to `Relation#where` now behaves the same as passing an
-    array.
+    ```ruby
+    class RemoveColumnTitle < ActiveRecord::Migration[6.1]
+      def change
+        remove_column :posts, :title, if_exists: true
+      end
+    end
+    ```
 
-    *Sean Griffin*
+    *Eileen M. Uchitelle*
 
-*   Use given algorithm while removing index from database.
+*   Regexp-escape table name for MS SQL Server.
 
-    Fixes #24190.
+    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.
 
-    *Mehmet Emin İNAÇ*
+    *Larry Reid*
 
-*   Update payload names for `sql.active_record` instrumentation to be
-    more descriptive.
+*   Store advisory locks on their own named connection.
 
-    Fixes #30586.
+    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.
 
-    *Jeremy Green*
+    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.
 
-*   Add new error class `LockWaitTimeout` which will be raised
-    when lock wait timeout exceeded.
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-    *Gabriel Courtemanche*
+*   Allow schema cache path to be defined in the database configuration file.
 
-*   Remove deprecated `#migration_keys`.
+    For example:
 
-    *Ryuta Kamizono*
+    ```yaml
+    development:
+      adapter: postgresql
+      database: blog_development
+      pool: 5
+      schema_cache_path: tmp/schema/main.yml
+    ```
 
-*   Automatically guess the inverse associations for STI.
+    *Katrina Owen*
 
-    *Yuichiro Kaneko*
+*   Deprecate `#remove_connection` in favor of `#remove_connection_pool` when called on the handler.
 
-*   Ensure `sum` honors `distinct` on `has_many :through` 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 6.2.
 
-    Fixes #16791.
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-    *Aaron Wortham*
+*   Deprecate `#default_hash` and it's alias `#[]` on database configurations.
 
-*   Add `binary` fixture helper method.
+    Applications should use `configs_for`. `#default_hash` and `#[]` will be removed in 6.2.
 
-    *Atsushi Yoshida*
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-*   When using `Relation#or`, extract the common conditions and put them before the OR condition.
+*   Add scale support to `ActiveRecord::Validations::NumericalityValidator`.
 
-    *Maxime Handfield Lapointe*
+    *Gannon McGibbon*
 
-*   `Relation#or` now accepts two relations who have different values for
-    `references` only, as `references` can be implicitly called by `where`.
+*   Find orphans by looking for missing relations through chaining `where.missing`:
 
-    Fixes #29411.
+    Before:
 
-    *Sean Griffin*
+    ```ruby
+    Post.left_joins(:author).where(authors: { id: nil })
+    ```
 
-*   `ApplicationRecord` is no longer generated when generating models. If you
-    need to generate it, it can be created with `rails g application_record`.
+    After:
 
-    *Lisa Ugray*
+    ```ruby
+    Post.where.missing(:author)
+    ```
 
-*   Fix `COUNT(DISTINCT ...)` with `ORDER BY` and `LIMIT` to keep the existing select list.
+    *Tom Rossi*
 
-    *Ryuta Kamizono*
+*   Ensure `:reading` connections always raise if a write is attempted.
 
-*   When a `has_one` association is destroyed by `dependent: destroy`,
-    `destroyed_by_association` will now be set to the reflection, matching the
-    behaviour of `has_many` associations.
+    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`.
 
-    *Lisa Ugray*
+    *Eileen M. Uchitelle*
 
-*   Fix `unscoped(where: [columns])` removing the wrong bind values.
+*   Deprecate `"primary"` as the `connection_specification_name` for `ActiveRecord::Base`.
 
-    When the `where` is called on a relation after a `or`, unscoping the column of that later `where` removed
-    bind values used by the `or` instead. (possibly other cases too)
+    `"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"`.
 
-    ```
-    Post.where(id: 1).or(Post.where(id: 2)).where(foo: 3).unscope(where: :foo).to_sql
-    # Currently:
-    #     SELECT "posts".* FROM "posts" WHERE ("posts"."id" = 2 OR "posts"."id" = 3)
-    # With fix:
-    #     SELECT "posts".* FROM "posts" WHERE ("posts"."id" = 1 OR "posts"."id" = 2)
+    *Eileen M. Uchitelle*, *John Crepezzi*
+
+*   Add `ActiveRecord::Validations::NumericalityValidator` with
+    support for casting floats using a database columns' precision value.
+
+    *Gannon McGibbon*
+
+*   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.
+
+    Fixes #38078.
+
+    *Aaron Lipman*
+
+*   Skip test database when running `db:create` or `db:drop` in development
+    with `DATABASE_URL` set.
+
+    *Brian Buchalter*
+
+*   Don't allow mutations on the database configurations hash.
+
+    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.
+
+    Before:
+
+    ```ruby
+    @db_config = ActiveRecord::Base.configurations.configs_for(env_name: "test", spec_name: "primary")
+    @db_config.configuration_hash.merge!(idle_timeout: "0.02")
     ```
 
-    *Maxime Handfield Lapointe*
+    After:
 
-*   Values constructed using multi-parameter assignment will now use the
-    post-type-cast value for rendering in single-field form inputs.
+    ```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)
+    ```
 
-    *Sean Griffin*
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-*   `Relation#joins` is no longer affected by the target model's
-    `current_scope`, with the exception of `unscoped`.
+*   Remove `:connection_id` from the `sql.active_record` notification.
 
-    Fixes #29338.
+    *Aaron Patterson*, *Rafael Mendonça França*
 
-    *Sean Griffin*
+*   The `:name` key will no longer be returned as part of `DatabaseConfig#configuration_hash`. Please use `DatabaseConfig#owner_name` instead.
 
-*   Change sqlite3 boolean serialization to use 1 and 0.
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-    SQLite natively recognizes 1 and 0 as true and false, but does not natively
-    recognize 't' and 'f' as was previously serialized.
+*   ActiveRecord's `belongs_to_required_by_default` flag can now be set per model.
 
-    This change in serialization requires a migration of stored boolean data
-    for SQLite databases, so it's implemented behind a configuration flag
-    whose default false value is deprecated.
+    You can now opt-out/opt-in specific models from having their associations required
+    by default.
 
-    *Lisa Ugray*
+    This change is meant to ease the process of migrating all your models to have
+    their association required.
 
-*   Skip query caching when working with batches of records (`find_each`, `find_in_batches`,
-    `in_batches`).
+    *Edouard Chin*
 
-    Previously, records would be fetched in batches, but all records would be retained in memory
-    until the end of the request or job.
+*   The `connection_config` method has been deprecated, please use `connection_db_config` instead which will return a `DatabaseConfigurations::DatabaseConfig` instead of a `Hash`.
 
-    *Eugene Kenny*
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-*   Prevent errors raised by `sql.active_record` notification subscribers from being converted into
-    `ActiveRecord::StatementInvalid` exceptions.
+*   Retain explicit selections on the base model after applying `includes` and `joins`.
 
-    *Dennis Taylor*
+    Resolves #34889.
 
-*   Fix eager loading/preloading association with scope including joins.
+    *Patrick Rebsch*
 
-    Fixes #28324.
+*   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.
 
-    *Ryuta Kamizono*
+    *Eileen M. Uchitelle*, *John Crepezzi*
 
-*   Fix transactions to apply state to child transactions.
+*   Allow attributes to be fetched from Arel node groupings.
 
-    Previously, if you had a nested transaction and the outer transaction was rolledback, the record from the
-    inner transaction would still be marked as persisted.
+    *Jeff Emminger*, *Gannon McGibbon*
 
-    This change fixes that by applying the state of the parent transaction to the child transaction when the
-    parent transaction is rolledback. This will correctly mark records from the inner transaction as not persisted.
+*   A database URL can now contain a querystring value that contains an equal sign. This is needed to support passing PostgreSQL `options`.
 
-    *Eileen M. Uchitelle*, *Aaron Patterson*
+    *Joshua Flanagan*
 
-*   Deprecate `set_state` method in `TransactionState`.
+*   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`.
 
-    Deprecated the `set_state` method in favor of setting the state via specific methods. If you need to mark the
-    state of the transaction you can now use `rollback!`, `commit!` or `nullify!` instead of
-    `set_state(:rolledback)`, `set_state(:committed)`, or `set_state(nil)`.
+    *John Crepezzi*
 
-    *Eileen M. Uchitelle*, *Aaron Patterson*
+*   Specifying `implicit_order_column` now subsorts the records by primary key if available to ensure deterministic results.
 
-*   Deprecate delegating to `arel` in `Relation`.
+    *Paweł Urbanek*
 
-    *Ryuta Kamizono*
+*   `where(attr => [])` now loads an empty result without making a query.
 
-*   Query cache was unavailable when entering the `ActiveRecord::Base.cache` block
-    without being connected.
+    *John Hawthorn*
 
-    *Tsukasa Oishi*
+*   Fixed the performance regression for `primary_keys` introduced MySQL 8.0.
 
-*   Previously, when building records using a `has_many :through` association,
-    if the child records were deleted before the parent was saved, they would
-    still be persisted. Now, if child records are deleted before the parent is saved
-    on a `has_many :through` association, the child records will not be persisted.
+    *Hiroyuki Ishii*
 
-    *Tobias Kraze*
+*   Add support for `belongs_to` to `has_many` inversing.
 
-*   Merging two relations representing nested joins no longer transforms the joins of
-    the merged relation into LEFT OUTER JOIN.
+    *Gannon McGibbon*
 
-    Example:
+*   Allow length configuration for `has_secure_token` method. The minimum length
+    is set at 24 characters.
 
+    Before:
+
+    ```ruby
+    has_secure_token :auth_token
     ```
-    Author.joins(:posts).merge(Post.joins(:comments))
-    # Before the change:
-    #=> SELECT ... FROM authors INNER JOIN posts ON ... LEFT OUTER JOIN comments ON...
 
-    # After the change:
-    #=> SELECT ... FROM authors INNER JOIN posts ON ... INNER JOIN comments ON...
+    After:
+
+    ```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
     ```
 
-    *Maxime Handfield Lapointe*
+    *Bernardo de Araujo*
 
-*   `ActiveRecord::Persistence#touch` does not work well when optimistic locking enabled and
-    `locking_column`, without default value, is null in the database.
+*   Deprecate `DatabaseConfigurations#to_h`. These connection hashes are still available via `ActiveRecord::Base.configurations.configs_for`.
 
-    *bogdanvlviv*
+    *Eileen Uchitelle*, *John Crepezzi*
 
-*   Fix destroying existing object does not work well when optimistic locking enabled and
-    `locking_column` is null in the database.
+*   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.
 
-    *bogdanvlviv*
+    *John Crepezzi*, *Eileen Uchitelle*
+
+*   Allow column names to be passed to `remove_index` positionally along with other options.
+
+    Passing other options can be necessary to make `remove_index` correctly reversible.
+
+    Before:
+
+        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
 
-*   Use bulk INSERT to insert fixtures for better performance.
+    After:
+
+        remove_index :reports, :report_id, unique: true # => works
+
+    *Eugene Kenny*
+
+*   Allow bulk `ALTER` statements to drop and recreate indexes with the same name.
+
+    *Eugene Kenny*
+
+*   `insert`, `insert_all`, `upsert`, and `upsert_all` now clear the query cache.
+
+    *Eugene Kenny*
+
+*   Call `while_preventing_writes` directly from `connected_to`.
+
+    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)`.
+
+    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.
+
+    *Eileen M. Uchitelle*
+
+*   Improve detection of ActiveRecord::StatementTimeout with mysql2 adapter in the edge case when the query is terminated during filesort.
 
     *Kir Shatrov*
 
-*   Prevent creation of bind param if casted value is nil.
+*   Stop trying to read yaml file fixtures when loading Active Record fixtures.
+
+    *Gannon McGibbon*
+
+*   Deprecate `.reorder(nil)` with `.first` / `.first!` taking non-deterministic result.
+
+    To continue taking non-deterministic result, use `.take` / `.take!` instead.
 
     *Ryuta Kamizono*
 
-*   Deprecate passing arguments and block at the same time to `count` and `sum` in `ActiveRecord::Calculations`.
+*   Preserve user supplied joins order as much as possible.
+
+    Fixes #36761, #34328, #24281, #12953.
 
     *Ryuta Kamizono*
 
-*   Loading model schema from database is now thread-safe.
+*   Allow `matches_regex` and `does_not_match_regexp` on the MySQL Arel visitor.
 
-    Fixes #28589.
+    *James Pearson*
 
-    *Vikrant Chaudhary*, *David Abdemoulaie*
+*   Allow specifying fixtures to be ignored by setting `ignore` in YAML file's '_fixture' section.
 
-*   Add `ActiveRecord::Base#cache_version` to support recyclable cache keys via the new versioned entries
-    in `ActiveSupport::Cache`. This also means that `ActiveRecord::Base#cache_key` will now return a stable key
-    that does not include a timestamp any more.
+    *Tongfei Gao*
 
-    NOTE: This feature is turned off by default, and `#cache_key` will still return cache keys with timestamps
-    until you set `ActiveRecord::Base.cache_versioning = true`. That's the setting for all new apps on Rails 5.2+
+*   Make the DATABASE_URL env variable only affect the primary connection. Add new env variables for multiple databases.
 
-    *DHH*
+    *John Crepezzi*, *Eileen Uchitelle*
 
-*   Respect `SchemaDumper.ignore_tables` in rake tasks for databases structure dump.
+*   Add a warning for enum elements with 'not_' prefix.
 
-    *Rusty Geldmacher*, *Guillermo Iguaran*
+        class Foo
+          enum status: [:sent, :not_sent]
+        end
 
-*   Add type caster to `RuntimeReflection#alias_name`.
+    *Edu Depetris*
 
-    Fixes #28959.
+*   Make currency symbols optional for money column type in PostgreSQL.
 
-    *Jon Moss*
+    *Joel Schneider*
 
-*   Deprecate `supports_statement_cache?`.
+*   Add support for beginless ranges, introduced in Ruby 2.7.
 
-    *Ryuta Kamizono*
+    *Josh Goodall*
 
-*   Raise error `UnknownMigrationVersionError` on the movement of migrations
-    when the current migration does not exist.
+*   Add `database_exists?` method to connection adapters to check if a database exists.
 
-    *bogdanvlviv*
+    *Guilherme Mansur*
 
-*   Fix `bin/rails db:forward` first migration.
+*   Loading the schema for a model that has no `table_name` raises a `TableNotSpecified` error.
 
-    *bogdanvlviv*
+    *Guilherme Mansur*, *Eugene Kenny*
 
-*   Support Descending Indexes for MySQL.
+*   PostgreSQL: Fix GROUP BY with ORDER BY virtual count attribute.
 
-    MySQL 8.0.1 and higher supports descending indexes: `DESC` in an index definition is no longer ignored.
-    See https://dev.mysql.com/doc/refman/8.0/en/descending-indexes.html.
+    Fixes #36022.
 
     *Ryuta Kamizono*
 
-*   Fix inconsistency with changed attributes when overriding Active Record attribute reader.
+*   Make ActiveRecord `ConnectionPool.connections` method thread-safe.
+
+    Fixes #36465.
 
-    *bogdanvlviv*
+    *Jeff Doering*
+
+*   Add support for multiple databases to `rails db:abort_if_pending_migrations`.
+
+    *Mark Lee*
+
+*   Fix sqlite3 collation parsing when using decimal columns.
+
+    *Martin R. Schuster*
+
+*   Fix invalid schema when primary key column has a comment.
+
+    Fixes #29966.
+
+    *Guilherme Goettems Schneider*
+
+*   Fix table comment also being applied to the primary key column.
+
+    *Guilherme Goettems Schneider*
 
-*   When calling the dynamic fixture accessor method with no arguments, it now returns all fixtures of this type.
-    Previously this method always returned an empty array.
+*   Allow generated `create_table` migrations to include or skip timestamps.
 
-    *Kevin McPhillips*
+    *Michael Duchemin*
 
 
-Please check [5-1-stable](https://github.com/rails/rails/blob/5-1-stable/activerecord/CHANGELOG.md) for previous changes.
+Please check [6-0-stable](https://github.com/rails/rails/blob/6-0-stable/activerecord/CHANGELOG.md) for previous changes.