RubyGems - activerecord - Versions diffs - 5.1.7 → 5.2.8.1 - Mend

activerecord 5.1.7 → 5.2.8.1

Potentially problematic release.

This version of activerecord might be problematic. Click here for more details.

Files changed (261) hide show

data/CHANGELOG.md CHANGED Viewed

@@ -1,1116 +1,1084 @@
-## Rails 5.1.7 (March 27, 2019) ##
+## 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]
+    ```
-*   Fix `touch` option to behave consistently with `Persistence#touch` method.
+    [CVE-2022-32224]
-    *Ryuta Kamizono*
-*   Back port Rails 5.2 `reverse_order` Arel SQL literal fix.
+## Rails 5.2.8 (May 09, 2022) ##
-    *Matt Jones*, *Brooke Kuhlmann*
+*   No changes.
-*   `becomes` should clear the mutation tracker which is created in `after_initialize`.
-    Fixes #32867.
+## Rails 5.2.7.1 (April 26, 2022) ##
-    *Ryuta Kamizono*
+*   No changes.
-## Rails 5.1.6.2 (March 11, 2019) ##
+## Rails 5.2.7 (March 10, 2022) ##
 *   No changes.
-## Rails 5.1.6.1 (November 27, 2018) ##
+## Rails 5.2.6.3 (March 08, 2022) ##
 *   No changes.
-## Rails 5.1.6 (March 29, 2018) ##
+## Rails 5.2.6.2 (February 11, 2022) ##
-*   MySQL: Support mysql2 0.5.x.
+*   No changes.
-    *Aaron Stone*
-*   Apply time column precision on assignment.
+## Rails 5.2.6.1 (February 11, 2022) ##
-    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.
+*   No changes.
-    Fixes #30301.
-    *Andrew White*
+## Rails 5.2.6 (May 05, 2021) ##
-*   Normalize time column values for SQLite database.
+*   No changes.
-    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.
-    *Andrew White*
+## Rails 5.2.5 (March 26, 2021) ##
-*   Ensure that the date component is removed when quoting times.
+*   No changes.
-    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.
-    *Andrew White*
+## Rails 5.2.4.6 (May 05, 2021) ##
-*   Fix that after commit callbacks on update does not triggered when optimistic locking is enabled.
+*   No changes.
-    *Ryuta Kamizono*
-*   `ActiveRecord::Persistence#touch` does not work well when optimistic locking enabled and
-    `locking_column`, without default value, is null in the database.
+## Rails 5.2.4.5 (February 10, 2021) ##
-    *bogdanvlviv*
+*   Fix possible DoS vector in PostgreSQL money type
-*   Fix destroying existing object does not work well when optimistic locking enabled and
-    `locking column` is null in the database.
+    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.
-    *bogdanvlviv*
+    Thanks to @dee-see from Hackerone for this patch!
+    [CVE-2021-22880]
-## Rails 5.1.5 (February 14, 2018) ##
+    *Aaron Patterson*
-*   PostgreSQL: Allow pg-1.0 gem to be used with Active Record.
-    *Lars Kanis*
+## Rails 5.2.4.4 (September 09, 2020) ##
-*   Fix `count(:all)` with eager loading and having an order other than the driving table.
+*   No changes.
-    Fixes #31783.
-    *Ryuta Kamizono*
+## Rails 5.2.4.3 (May 18, 2020) ##
-*   Use `count(:all)` in `HasManyAssociation#count_records` to prevent invalid
-    SQL queries for association counting.
+*   No changes.
-    *Klas Eskilson*
+## Rails 5.2.4.2 (March 19, 2020) ##
-*   Fix to invoke callbacks when using `update_attribute`.
+*   No changes.
-    *Mike Busch*
-*   Fix `count(:all)` to correctly work `distinct` with custom SELECT list.
+## Rails 5.2.4.1 (December 18, 2019) ##
-    *Ryuta Kamizono*
+*   No changes.
-*   Fix conflicts `counter_cache` with `touch: true` by optimistic locking.
-    ```
-    # create_table :posts do |t|
-    #   t.integer :comments_count, default: 0
-    #   t.integer :lock_version
-    #   t.timestamps
-    # end
-    class Post < ApplicationRecord
-    end
+## Rails 5.2.4 (November 27, 2019) ##
-    # create_table :comments do |t|
-    #   t.belongs_to :post
-    # end
-    class Comment < ApplicationRecord
-      belongs_to :post, touch: true, counter_cache: true
-    end
-    ```
+*   Fix circular `autosave: true` causes invalid records to be saved.
-    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
+    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`.
-    comment = Comment.create!(post: post)
-    # => begin transaction
-         INSERT INTO "comments" ("post_id") VALUES (1)
+    Fixes #28080.
-         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) + 1,
-         "lock_version" = COALESCE("lock_version", 0) + 1 WHERE "posts"."id" = 1
+    *Larry Reid*
-         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.
+*   PostgreSQL: Fix GROUP BY with ORDER BY virtual count attribute.
-    Comment.take.destroy!
-    # => begin transaction
-         DELETE FROM "comments" WHERE "comments"."id" = 1
+    Fixes #36022.
-         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) - 1,
-         "lock_version" = COALESCE("lock_version", 0) + 1 WHERE "posts"."id" = 1
+    *Ryuta Kamizono*
-         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.
-    ```
+*   Fix sqlite3 collation parsing when using decimal columns.
-    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
+    *Martin R. Schuster*
-    comment = Comment.create!(post: post)
-    # => begin transaction
-         INSERT INTO "comments" ("post_id") VALUES (1)
+*   Make ActiveRecord `ConnectionPool.connections` method thread-safe.
-         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
+    Fixes #36465.
-    comment.destroy!
-    # => begin transaction
-         DELETE FROM "comments" WHERE "comments"."id" = 1
+    *Jeff Doering*
-         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
-    ```
+*   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.
-    Fixes #31199.
+    Fixes #33249.
-    *bogdanvlviv*
+    *Ryan H. Kerr*
-*   Query cache was unavailable when entering the `ActiveRecord::Base.cache` block
-    without being connected.
-    *Tsukasa Oishi*
+## Rails 5.2.3 (March 27, 2019) ##
-*   Fix `bin/rails db:setup` and `bin/rails db:test:prepare` create  wrong
-    ar_internal_metadata's data for a test database.
+*   Fix different `count` calculation when using `size` with manual `select` with DISTINCT.
-    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
-    ```
+    Fixes #35214.
-    After:
-    ```
-    $ 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
-    ```
+    *Juani Villarejo*
-    Fixes #26731.
+*   Fix prepared statements caching to be enabled even when query caching is enabled.
-    *bogdanvlviv*
+    *Ryuta Kamizono*
-*   Fix longer sequence name detection for serial columns.
+*   Don't allow `where` with invalid value matches to nil values.
-    Fixes #28332.
+    Fixes #33624.
     *Ryuta Kamizono*
-*   MySQL: Don't lose `auto_increment: true` in the `db/schema.rb`.
+*   Restore an ability that class level `update` without giving ids.
-    Fixes #30894.
+    Fixes #34743.
     *Ryuta Kamizono*
-*   Fix `COUNT(DISTINCT ...)` for `GROUP BY` with `ORDER BY` and `LIMIT`.
+*   Fix join table column quoting with SQLite.
-    Fixes #30886.
+    *Gannon McGibbon*
+*   Ensure that `delete_all` on collection proxy returns affected count.
     *Ryuta Kamizono*
+*   Reset scope after delete on collection association to clear stale offsets of removed records.
-## Rails 5.1.4 (September 07, 2017) ##
+    *Gannon McGibbon*
-*   No changes.
+## Rails 5.2.2.1 (March 11, 2019) ##
-## Rails 5.1.4.rc1 (August 24, 2017) ##
-*   Ensure `sum` honors `distinct` on `has_many :through` associations
+*   No changes.
-    Fixes #16791
-    *Aaron Wortham
+## Rails 5.2.2 (December 04, 2018) ##
-*   Fix `COUNT(DISTINCT ...)` with `ORDER BY` and `LIMIT` to keep the existing select list.
+*   Do not ignore the scoping with query methods in the scope block.
     *Ryuta Kamizono*
-*   Fix `unscoped(where: [columns])` removing the wrong bind values
+*   Allow aliased attributes to be used in `#update_columns` and `#update`.
-    When the `where` is called on a relation after a `or`, unscoping the column of that later `where`, it removed
-    bind values used by the `or` instead.
+    *Gannon McGibbon*
-    ```
-    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)
-    ```
-    *Maxime Handfield Lapointe*
+*   Allow spaces in postgres table names.
-*   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.
+    Fixes issue where "user post" is misinterpreted as "\"user\".\"post\"" when quoting table names with the postgres
+    adapter.
-    *Lisa Ugray*
+    *Gannon McGibbon*
+*   Cached columns_hash fields should be excluded from ResultSet#column_types
-## Rails 5.1.3 (August 03, 2017) ##
+    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:
-*   No changes.
+    ```ruby
+    class DeveloperName < ActiveRecord::Type::String
+      def deserialize(value)
+        "Developer: #{value}"
+      end
+    end
+    class AttributedDeveloper < ActiveRecord::Base
+      self.table_name = "developers"
-## Rails 5.1.3.rc3 (July 31, 2017) ##
-*   No changes.
+      attribute :name, DeveloperName.new
+      self.ignored_columns += ["name"]
+    end
-## Rails 5.1.3.rc2 (July 25, 2017) ##
+    developer = AttributedDeveloper.create
+    developer.update_column :name, "name"
-*   No changes.
+    loaded_developer = AttributedDeveloper.where(id: developer.id).select("*").first
+    puts loaded_developer.name # should be "Developer: name" but it's just "name"
+    ```
+    *Dmitry Tsepelev*
-## Rails 5.1.3.rc1 (July 19, 2017) ##
+*   Values of enum are frozen, raising an error when attempting to modify them.
-*   `Relation#joins` is no longer affected by the target model's
-    `current_scope`, with the exception of `unscoped`.
+    *Emmanuel Byrd*
-    Fixes #29338.
+*   `update_columns` now correctly raises `ActiveModel::MissingAttributeError`
+    if the attribute does not exist.
     *Sean Griffin*
-*   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.
-    *Tobias Kraze*
+*   Do not use prepared statement in queries that have a large number of binds.
+    *Ryuta Kamizono*
-## Rails 5.1.2 (June 26, 2017) ##
+*   Fix query cache to load before first request.
-*   Restore previous behavior of collection proxies: their values can have
-    methods stubbed, and they respect extension modules applied by a default
-    scope.
+    *Eileen M. Uchitelle*
-    *Ryuta Kamizono*
+*   Fix collection cache key with limit and custom select to avoid ambiguous timestamp column error.
-*   Loading model schema from database is now thread-safe.
+    Fixes #33056.
-    Fixes #28589.
+    *Federico Martinez*
-    *Vikrant Chaudhary*, *David Abdemoulaie*
+*   Fix duplicated record creation when using nested attributes with `create_with`.
+    *Darwin Wu*
-## Rails 5.1.1 (May 12, 2017) ##
+*   Fix regression setting children record in parent `before_save` callback.
-*   Add type caster to `RuntimeReflection#alias_name`
+    *Guo Xiang Tan*
-    Fixes #28959.
+*   Prevent leaking of user's DB credentials on `rails db:create` failure.
-    *Jon Moss*
+    *bogdanvlviv*
+*   Clear mutation tracker before continuing the around callbacks.
-## Rails 5.1.0 (April 27, 2017) ##
+    *Yuya Tanaka*
-*   Quote database name in db:create grant statement (when database_user does not have access to create the database).
+*   Prevent deadlocks when waiting for connection from pool.
-    *Rune Philosof*
+    *Brent Wheeldon*
-*   When multiple threads are sharing a database connection inside a test using
-    transactional fixtures, a nested transaction will temporarily lock the
-    connection to the current thread, forcing others to wait.
+*   Avoid extra scoping when using `Relation#update` that was causing this method to change the current scope.
-    Fixes #28197.
+    *Ryuta Kamizono*
-    *Matthew Draper*
+*   Fix numericality validator not to be affected by custom getter.
-*   Load only needed records on `ActiveRecord::Relation#inspect`.
+    *Ryuta Kamizono*
-    Instead of loading all records and returning only a subset of those, just
-    load the records as needed.
+*   Fix bulk change table ignores comment option on PostgreSQL.
-    Fixes #25537.
+    *Yoshiyuki Kinjo*
-    *Hendy Tanata*
-*   Remove comments from structure.sql when using postgresql adapter to avoid
-    version-specific parts of the file.
+## Rails 5.2.1.1 (November 27, 2018) ##
-    Fixes #28153.
+*   No changes.
-    *Ari Pollak*
-*   Add `:default` option to `belongs_to`.
+## Rails 5.2.1 (August 07, 2018) ##
-    Use it to specify that an association should be initialized with a particular
-    record before validation. For example:
+*   PostgreSQL: Support new relkind for partitioned tables.
-        # Before
-        belongs_to :account
-        before_validation -> { self.account ||= Current.account }
+    Fixes #33008.
-        # After
-        belongs_to :account, default: -> { Current.account }
+    *Yannick Schutz*
-    *George Claghorn*
+*   Rollback parent transaction when children fails to update.
-*   Deprecate `Migrator.schema_migrations_table_name`.
+    *Guillaume Malette*
-    *Ryuta Kamizono*
+*   Fix default value for MySQL time types with specified precision.
-*   Fix select with block doesn't return newly built records in has_many association.
+    *Nikolay Kondratyev*
-    Fixes #28348.
+*   Fix `touch` option to behave consistently with `Persistence#touch` method.
     *Ryuta Kamizono*
-*   Check whether `Rails.application` defined before calling it
+*   Fix `save` in `after_create_commit` won't invoke extra `after_create_commit`.
-    In #27674 we changed the migration generator to generate migrations at the
-    path defined in `Rails.application.config.paths` however the code checked
-    for the presence of the `Rails` constant but not the `Rails.application`
-    method which caused problems when using Active Record and generators outside
-    of the context of a Rails application.
+    Fixes #32831.
-    Fixes #28325.
+    *Ryuta Kamizono*
-    *Andrew White*
+*   Fix logic on disabling commit callbacks so they are not called unexpectedly when errors occur.
-*   Fix `deserialize` with JSON array.
+    *Brian Durand*
-    Fixes #28285.
+*   Fix parent record should not get saved with duplicate children records.
-    *Ryuta Kamizono*
+    Fixes #32940.
-*   Fix `rake db:schema:load` with subdirectories.
+    *Santosh Wadghule*
-    *Ryuta Kamizono*
+*   Fix that association's after_touch is not called with counter cache.
-*   Fix `rake db:migrate:status` with subdirectories.
+    Fixes #31559.
     *Ryuta Kamizono*
-*   Don't share options between reference id and type columns
+*   `becomes` should clear the mutation tracker which is created in `after_initialize`.
-    When using a polymorphic reference column in a migration, sharing options
-    between the two columns doesn't make sense since they are different types.
-    The `reference_id` column is usually an integer and the `reference_type`
-    column a string so options like `unsigned: true` will result in an invalid
-    table definition.
+    Fixes #32867.
     *Ryuta Kamizono*
-*   Use `max_identifier_length` for `index_name_length` in PostgreSQL adapter.
-    *Ryuta Kamizono*
+*   Allow a belonging to parent object to be created from a new record.
-*   Deprecate `supports_migrations?` on connection adapters.
+    *Jolyon Pawlyn*
-    *Ryuta Kamizono*
+*   Fix that building record with assigning multiple has_one associations
+    wrongly persists through record.
-*   Fix regression of #1969 with SELECT aliases in HAVING clause.
+    Fixes #32511.
-    *Eugene Kenny*
+    *Sam DeCesare*
-*   Deprecate using `#quoted_id` in quoting.
+*   Fix relation merging when one of the relations is going to skip the
+    query cache.
-    *Ryuta Kamizono*
+    *James Williams*
-*   Fix `wait_timeout` to configurable for mysql2 adapter.
-    Fixes #26556.
+## Rails 5.2.0 (April 09, 2018) ##
-    *Ryuta Kamizono*
+*   MySQL: Support mysql2 0.5.x.
-*   Correctly dump native timestamp types for MySQL.
+    *Aaron Stone*
-    The native timestamp type in MySQL is different from datetime type.
-    Internal representation of the timestamp type is UNIX time, This means
-    that timestamp columns are affected by time zone.
+*   Apply time column precision on assignment.
-        > SET time_zone = '+00:00';
-        Query OK, 0 rows affected (0.00 sec)
+    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.
-        > INSERT INTO time_with_zone(ts,dt) VALUES (NOW(),NOW());
-        Query OK, 1 row affected (0.02 sec)
+    Fixes #30301.
-        > SELECT * FROM time_with_zone;
-        +---------------------+---------------------+
-        | ts                  | dt                  |
-        +---------------------+---------------------+
-        | 2016-02-07 22:11:44 | 2016-02-07 22:11:44 |
-        +---------------------+---------------------+
-        1 row in set (0.00 sec)
+    *Andrew White*
-        > SET time_zone = '-08:00';
-        Query OK, 0 rows affected (0.00 sec)
+*   Normalize time column values for SQLite database.
-        > SELECT * FROM time_with_zone;
-        +---------------------+---------------------+
-        | ts                  | dt                  |
-        +---------------------+---------------------+
-        | 2016-02-07 14:11:44 | 2016-02-07 22:11:44 |
-        +---------------------+---------------------+
-        1 row in set (0.00 sec)
+    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.
-    *Ryuta Kamizono*
+    *Andrew White*
-*   All integer-like PKs are autoincrement unless they have an explicit default.
+*   Ensure that the date component is removed when quoting times.
-    *Matthew Draper*
+    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.
-*   Omit redundant `using: :btree` for schema dumping.
+    *Andrew White*
-    *Ryuta Kamizono*
+*   Fix `dependent: :destroy` issue for has_one/belongs_to relationship where
+    the parent class was getting deleted when the child was not.
-*   Deprecate passing `default` to `index_name_exists?`.
+    Fixes #32022.
-    *Ryuta Kamizono*
+    *Fernando Gorodscy*
-*   PostgreSQL: schema dumping support for interval and OID columns.
+*   Whitelist `NULLS FIRST` and `NULLS LAST` in order clauses too.
-    *Ryuta Kamizono*
+    *Xavier Noria*
-*   Deprecate `supports_primary_key?` on connection adapters since it's
-    been long unused and unsupported.
+*   Fix that after commit callbacks on update does not triggered when optimistic locking is enabled.
     *Ryuta Kamizono*
-*   Make `table_name=` reset current statement cache,
-    so queries are not run against the previous table name.
-    *namusyaka*
+*   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.
-*   Allow `ActiveRecord::Base#as_json` to be passed a frozen Hash.
+    Fixes #28364.
-    *Isaac Betesh*
+    *Takumi Kagiyama*
-*   Fix inspection behavior when the :id column is not primary key.
+*   Make `reflection.klass` raise if `polymorphic?` not to be misused.
-    *namusyaka*
+    Fixes #31876.
-*   Deprecate locking records with unpersisted changes.
-    *Marc Schütz*
+    *Ryuta Kamizono*
-*   Remove deprecated behavior that halts callbacks when the return is false.
+*   PostgreSQL: Allow pg-1.0 gem to be used with Active Record.
-    *Rafael Mendonça França*
+    *Lars Kanis*
-*   Deprecate `ColumnDumper#migration_keys`.
+*   Deprecate `expand_hash_conditions_for_aggregates` without replacement.
+    Using a `Relation` for performing queries is the prefered API.
     *Ryuta Kamizono*
-*   Fix `association_primary_key_type` for reflections with symbol primary key.
-    Fixes #27864.
+*   Fix not expanded problem when passing an Array object as argument to the where method using `composed_of` column.
-    *Daniel Colson*
+    ```
+    david_balance = customers(:david).balance
+    Customer.where(balance: [david_balance]).to_sql
-*   Virtual/generated column support for MySQL 5.7.5+ and MariaDB 5.2.0+.
+    # Before: WHERE `customers`.`balance` = NULL
+    # After : WHERE `customers`.`balance` = 50
+    ```
-    MySQL generated columns: https://dev.mysql.com/doc/refman/5.7/en/create-table-generated-columns.html
-    MariaDB virtual columns: https://mariadb.com/kb/en/mariadb/virtual-computed-columns/
+    Fixes #31723.
-    Declare virtual columns with `t.virtual name, type: …, as: "expression"`.
-    Pass `stored: true` to persist the generated value (false by default).
+    *Yutaro Kanagawa*
-    Example:
+*   Fix `count(:all)` with eager loading and having an order other than the driving table.
-        create_table :generated_columns do |t|
-          t.string  :name
-          t.virtual :upper_name,  type: :string,  as: "UPPER(name)"
-          t.virtual :name_length, type: :integer, as: "LENGTH(name)", stored: true
-          t.index :name_length  # May be indexed, too!
-        end
+    Fixes #31783.
     *Ryuta Kamizono*
-*   Deprecate `initialize_schema_migrations_table` and `initialize_internal_metadata_table`.
+*   Clear the transaction state when an Active Record object is duped.
-    *Ryuta Kamizono*
+    Fixes #31670.
-*   Support foreign key creation for SQLite3.
+    *Yuriy Ustushenko*
-    *Ryuta Kamizono*
+*   Support for PostgreSQL foreign tables.
+    *fatkodima*
-*   Place generated migrations into the path set by `config.paths["db/migrate"]`.
+*   Fix relation merger issue with `left_outer_joins`.
-    *Kevin Glowacz*
+    *Mehmet Emin İNAÇ*
-*   Raise `ActiveRecord::InvalidForeignKey` when a foreign key constraint fails on SQLite3.
+*   Don't allow destroyed object mutation after `save` or `save!` is called.
     *Ryuta Kamizono*
-*   Add the touch option to `#increment!` and `#decrement!`.
-    *Hiroaki Izu*
+*   Take into account association conditions when deleting through records.
-*   Deprecate passing a class to the `class_name` because it eagerloads more classes than
-    necessary and potentially creates circular dependencies.
+    Fixes #18424.
-    *Kir Shatrov*
+    *Piotr Jakubowski*
-*   Raise error when has_many through is defined before through association.
+*   Fix nested `has_many :through` associations on unpersisted parent instances.
-    Fixes #26834.
+    For example, if you have
-    *Chris Holmes*
+        class Post < ActiveRecord::Base
+          belongs_to :author
+          has_many :books, through: :author
+          has_many :subscriptions, through: :books
+        end
-*   Deprecate passing `name` to `indexes`.
+        class Author < ActiveRecord::Base
+          has_one :post
+          has_many :books
+          has_many :subscriptions, through: :books
+        end
-    *Ryuta Kamizono*
+        class Book < ActiveRecord::Base
+          belongs_to :author
+          has_many :subscriptions
+        end
-*   Remove deprecated tasks: `db:test:clone`, `db:test:clone_schema`, `db:test:clone_structure`.
+        class Subscription < ActiveRecord::Base
+          belongs_to :book
+        end
-    *Rafel Mendonça França*
+    Before:
-*   Compare deserialized values for `PostgreSQL::OID::Hstore` types when
-    calling `ActiveRecord::Dirty#changed_in_place?`.
+    If `post` is not persisted, then `post.subscriptions` will be empty.
-    Fixes #27502.
+    After:
-    *Jon Moss*
+    If `post` is not persisted, then `post.subscriptions` can be set and used
+    just like it would if `post` were persisted.
-*   Raise `ArgumentError` when passing an `ActiveRecord::Base` instance to `.find`,
-    `.exists?` and `.update`.
+    Fixes #16313.
-    *Rafael Mendonça França*
+    *Zoltan Kiss*
-*   Respect precision option for arrays of timestamps.
+*   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)`.
-    Fixes #27514.
+    Fixes #23979.
-    *Sean Griffin*
+    *Brian Christian*
-*   Optimize slow model instantiation when using STI and `store_full_sti_class = false` option.
+*   Use `count(:all)` in `HasManyAssociation#count_records` to prevent invalid
+    SQL queries for association counting.
-    *Konstantin Lazarev*
+    *Klas Eskilson*
-*   Add `touch` option to counter cache modifying methods.
+*   Fix to invoke callbacks when using `update_attribute`.
-    Works when updating, resetting, incrementing and decrementing counters:
+    *Mike Busch*
-        # Touches `updated_at`/`updated_on`.
-        Topic.increment_counter(:messages_count, 1, touch: true)
-        Topic.decrement_counter(:messages_count, 1, touch: true)
+*   Fix `count(:all)` to correctly work `distinct` with custom SELECT list.
-        # Touches `last_discussed_at`.
-        Topic.reset_counters(18, :messages, touch: :last_discussed_at)
+    *Ryuta Kamizono*
-        # Touches `updated_at` and `last_discussed_at`.
-        Topic.update_counters(18, messages_count: 5, touch: %i( updated_at last_discussed_at ))
+*   Using subselect for `delete_all` with `limit` or `offset`.
-    Fixes #26724.
+    *Ryuta Kamizono*
-    *Jarred Trost*
+*   Undefine attribute methods on descendants when resetting column
+    information.
-*   Remove deprecated `#uniq`, `#uniq!`, and `#uniq_value`.
+    *Chris Salzberg*
-    *Ryuta Kamizono*
+*   Log database query callers.
-*   Remove deprecated `#insert_sql`, `#update_sql`, and `#delete_sql`.
+    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.
-    *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.
-*   Remove deprecated `#use_transactional_fixtures` configuration.
+    *Olivier Lacan*
-    *Rafael Mendonça França*
+*   Fix conflicts `counter_cache` with `touch: true` by optimistic locking.
-*   Remove deprecated `#raise_in_transactional_callbacks` configuration.
+    ```
+    # create_table :posts do |t|
+    #   t.integer :comments_count, default: 0
+    #   t.integer :lock_version
+    #   t.timestamps
+    # end
+    class Post < ApplicationRecord
+    end
-    *Rafael Mendonça França*
+    # create_table :comments do |t|
+    #   t.belongs_to :post
+    # end
+    class Comment < ApplicationRecord
+      belongs_to :post, touch: true, counter_cache: true
+    end
+    ```
-*   Remove deprecated `#load_schema_for`.
+    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
-    *Rafael Mendonça França*
+    comment = Comment.create!(post: post)
+    # => begin transaction
+         INSERT INTO "comments" ("post_id") VALUES (1)
-*   Remove deprecated conditions parameter from `#destroy_all` and `#delete_all`.
+         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) + 1,
+         "lock_version" = COALESCE("lock_version", 0) + 1 WHERE "posts"."id" = 1
-    *Rafael Mendonça França*
+         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.
-*   Remove deprecated support to passing arguments to `#select` when a block is provided.
+    Comment.take.destroy!
+    # => begin transaction
+         DELETE FROM "comments" WHERE "comments"."id" = 1
-    *Rafael Mendonça França*
+         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) - 1,
+         "lock_version" = COALESCE("lock_version", 0) + 1 WHERE "posts"."id" = 1
-*   Remove deprecated support to query using commas on LIMIT.
+         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.
+    ```
-    *Rafael Mendonça França*
+    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
-*   Remove deprecated support to passing a class as a value in a query.
+    comment = Comment.create!(post: post)
+    # => begin transaction
+         INSERT INTO "comments" ("post_id") VALUES (1)
-    *Rafael Mendonça França*
+         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
-*   Raise `ActiveRecord::IrreversibleOrderError` when using `last` with an irreversible
-    order.
+    comment.destroy!
+    # => begin transaction
+         DELETE FROM "comments" WHERE "comments"."id" = 1
-    *Rafael Mendonça França*
+         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
+    ```
-*   Raise when a `has_many :through` association has an ambiguous reflection name.
+    Fixes #31199.
-    *Rafael Mendonça França*
+    *bogdanvlviv*
-*   Raise when `ActiveRecord::Migration` is inherited from directly.
+*   Add support for PostgreSQL operator classes to `add_index`.
-    *Rafael Mendonça França*
+    Example:
-*   Remove deprecated `original_exception` argument in `ActiveRecord::StatementInvalid#initialize`
-    and `ActiveRecord::StatementInvalid#original_exception`.
+        add_index :users, :name, using: :gist, opclass: { name: :gist_trgm_ops }
-    *Rafael Mendonça França*
+    *Greg Navis*
-*   `#tables` and `#table_exists?` return only tables and not views.
+*   Don't allow scopes to be defined which conflict with instance methods on `Relation`.
-    All the deprecations on those methods were removed.
+    Fixes #31120.
-    *Rafael Mendonça França*
+    *kinnrot*
-*   Remove deprecated `name` argument from `#tables`.
+*   Add new error class `QueryCanceled` which will be raised
+    when canceling statement due to user request.
-    *Rafael Mendonça França*
+    *Ryuta Kamizono*
-*   Remove deprecated support to passing a column to `#quote`.
+*   Add `#up_only` to database migrations for code that is only relevant when
+    migrating up, e.g. populating a new column.
-    *Rafael Mendonça França*
+    *Rich Daley*
-*   Set `:time` as a timezone aware type and remove deprecation when
-    `config.active_record.time_zone_aware_types` is not explicitly set.
+*   Require raw SQL fragments to be explicitly marked when used in
+    relation query methods.
-    *Rafael Mendonça França*
+    Before:
+    ```
+    Article.order("LENGTH(title)")
+    ```
-*   Remove deprecated force reload argument in singular and collection association readers.
+    After:
+    ```
+    Article.order(Arel.sql("LENGTH(title)"))
+    ```
-    *Rafael Mendonça França*
+    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.
-*   Remove deprecated `activerecord.errors.messages.restrict_dependent_destroy.one` and
-    `activerecord.errors.messages.restrict_dependent_destroy.many` i18n scopes.
+    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`.
-    *Rafael Mendonça França*
+    Common and judged-safe string values (such as simple column
+    references) are unaffected:
+    ```
+    Article.order("title DESC")
+    ```
-*   Allow passing extra flags to `db:structure:load` and `db:structure:dump`
+    *Ben Toews*
-    Introduces `ActiveRecord::Tasks::DatabaseTasks.structure_(load|dump)_flags` to customize the
-    eventual commands run against the database, e.g. mysqldump/pg_dump.
+*   `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.
-    *Kir Shatrov*
+    *Sean Griffin*
-*   Notifications see frozen SQL string.
+*   Add new error class `StatementTimeout` which will be raised
+    when statement timeout exceeded.
-    Fixes #23774.
+    *Ryuta Kamizono*
-    *Richard Monette*
+*   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.
-*   RuntimeErrors are no longer translated to `ActiveRecord::StatementInvalid`.
+    *bogdanvlviv*
-    *Richard Monette*
+*   Fixed a bug where column orders for an index weren't written to
+    `db/schema.rb` when using the sqlite adapter.
-*   Change the schema cache format to use YAML instead of Marshal.
+    Fixes #30902.
-    *Kir Shatrov*
+    *Paul Kuruvilla*
-*   Support index length and order options using both string and symbol
-    column names.
+*   Remove deprecated method `#sanitize_conditions`.
-    Fixes #27243.
+    *Rafael Mendonça França*
-    *Ryuta Kamizono*
+*   Remove deprecated method `#scope_chain`.
-*   Raise `ActiveRecord::RangeError` when values that executed are out of range.
+    *Rafael Mendonça França*
-    *Ryuta Kamizono*
+*   Remove deprecated configuration `.error_on_ignored_order_or_limit`.
-*   Raise `ActiveRecord::NotNullViolation` when a record cannot be inserted
-    or updated because it would violate a not null constraint.
+    *Rafael Mendonça França*
-    *Ryuta Kamizono*
+*   Remove deprecated arguments from `#verify!`.
-*   Emulate db trigger behaviour for after_commit :destroy, :update.
+    *Rafael Mendonça França*
-    Race conditions can occur when an ActiveRecord is destroyed
-    twice or destroyed and updated. The callbacks should only be
-    triggered once, similar to a SQL database trigger.
+*   Remove deprecated argument `name` from `#indexes`.
-    *Stefan Budeanu*
+    *Rafael Mendonça França*
-*   Moved `DecimalWithoutScale`, `Text`, and `UnsignedInteger` from Active Model to Active Record.
+*   Remove deprecated method `ActiveRecord::Migrator.schema_migrations_table_name`.
-    *Iain Beeston*
+    *Rafael Mendonça França*
-*   Fix `write_attribute` method to check whether an attribute is aliased or not, and
-    use the aliased attribute name if needed.
+*   Remove deprecated method `supports_primary_key?`.
-    *Prathamesh Sonpatki*
+    *Rafael Mendonça França*
-*   Fix `read_attribute` method to check whether an attribute is aliased or not, and
-    use the aliased attribute name if needed.
+*   Remove deprecated method `supports_migrations?`.
-    Fixes #26417.
+    *Rafael Mendonça França*
-    *Prathamesh Sonpatki*
+*   Remove deprecated methods `initialize_schema_migrations_table` and `initialize_internal_metadata_table`.
-*   PostgreSQL & MySQL: Use big integer as primary key type for new tables.
+    *Rafael Mendonça França*
-    *Jon McCartie*, *Pavel Pravosud*
+*   Raises when calling `lock!` in a dirty record.
-*   Change the type argument of `ActiveRecord::Base#attribute` to be optional.
-    The default is now `ActiveRecord::Type::Value.new`, which provides no type
-    casting behavior.
+    *Rafael Mendonça França*
-    *Sean Griffin*
+*   Remove deprecated support to passing a class to `:class_name` on associations.
-*   Don't treat unsigned integers with zerofill as signed.
+    *Rafael Mendonça França*
-    Fixes #27125.
+*   Remove deprecated argument `default` from `index_name_exists?`.
-    *Ryuta Kamizono*
+    *Rafael Mendonça França*
-*   Fix the uniqueness validation scope with a polymorphic association.
+*   Remove deprecated support to `quoted_id` when typecasting an Active Record object.
-    *Sergey Alekseev*
+    *Rafael Mendonça França*
-*   Raise `ActiveRecord::RecordNotFound` from collection `*_ids` setters
-    for unknown IDs with a better error message.
+*   Fix `bin/rails db:setup` and `bin/rails db:test:prepare` create wrong
+    ar_internal_metadata's data for a test database.
-    Changes the collection `*_ids` setters to cast provided IDs the data
-    type of the primary key set in the association, not the model
-    primary key.
+    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
+    ```
-    *Dominic Cleal*
+    After:
+    ```
+    $ 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
+    ```
-*   For PostgreSQL >= 9.4 use `pgcrypto`'s `gen_random_uuid()` instead of
-    `uuid-ossp`'s UUID generation function.
+    Fixes #26731.
-    *Yuji Yaginuma*, *Yaw Boakye*
+    *bogdanvlviv*
-*   Introduce `Model#reload_<association>` to bring back the behavior
-    of `Article.category(true)` where `category` is a singular
-    association.
+*   Fix longer sequence name detection for serial columns.
-    The force reloading of the association reader was deprecated
-    in #20888. Unfortunately the suggested alternative of
-    `article.reload.category` does not expose the same behavior.
+    Fixes #28332.
-    This patch adds a reader method with the prefix `reload_` for
-    singular associations. This method has the same semantics as
-    passing true to the association reader used to have.
+    *Ryuta Kamizono*
-    *Yves Senn*
+*   MySQL: Don't lose `auto_increment: true` in the `db/schema.rb`.
-*   Make sure eager loading `ActiveRecord::Associations` also loads
-    constants defined in `ActiveRecord::Associations::Preloader`.
+    Fixes #30894.
-    *Yves Senn*
+    *Ryuta Kamizono*
-*   Allow `ActionController::Parameters`-like objects to be passed as
-    values for Postgres HStore columns.
+*   Fix `COUNT(DISTINCT ...)` for `GROUP BY` with `ORDER BY` and `LIMIT`.
-    Fixes #26904.
+    Fixes #30886.
-    *Jon Moss*
+    *Ryuta Kamizono*
-*   Added `stat` method to `ActiveRecord::ConnectionAdapters::ConnectionPool`.
+*   PostgreSQL `tsrange` now preserves subsecond precision.
-    Example:
+    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:
-        ActiveRecord::Base.connection_pool.stat # =>
-        { size: 15, connections: 1, busy: 1, dead: 0, idle: 0, waiting: 0, checkout_timeout: 5 }
+    Before:
-    *Pavel Evstigneev*
+        connection.type_cast(tsrange.serialize(range_value))
+        # => "[2010-01-01 13:30:00 UTC,2011-02-02 19:30:00 UTC)"
-*   Avoid `unscope(:order)` when `limit_value` is presented for `count`
-    and `exists?`.
+    Now:
-    If `limit_value` is presented, records fetching order is very important
-    for performance. We should not unscope the order in the case.
+        connection.type_cast(tsrange.serialize(range_value))
+        # => "[2010-01-01 13:30:00.670277,2011-02-02 19:30:00.745125)"
-    *Ryuta Kamizono*
+    *Thomas Cannon*
-*   Fix an Active Record `DateTime` field `NoMethodError` caused by incomplete
-    datetime.
+*   Passing a `Set` to `Relation#where` now behaves the same as passing an
+    array.
-    Fixes #24195.
+    *Sean Griffin*
-    *Sen Zhang*
+*   Use given algorithm while removing index from database.
-*   Allow `slice` to take an array of methods(without the need for splatting).
+    Fixes #24190.
-    *Cohen Carlisle*
+    *Mehmet Emin İNAÇ*
-*   Improved partial writes with HABTM and has many through associations
-    to fire database query only if relation has been changed.
+*   Update payload names for `sql.active_record` instrumentation to be
+    more descriptive.
-    Fixes #19663.
+    Fixes #30586.
-    *Mehmet Emin İNAÇ*
+    *Jeremy Green*
-*   Deprecate passing arguments and block at the same time to
-    `ActiveRecord::QueryMethods#select`.
+*   Add new error class `LockWaitTimeout` which will be raised
+    when lock wait timeout exceeded.
-    *Prathamesh Sonpatki*
+    *Gabriel Courtemanche*
-*   Fixed: Optimistic locking does not work well with `null` in the database.
+*   Remove deprecated `#migration_keys`.
-    Fixes #26024.
+    *Ryuta Kamizono*
-    *bogdanvlviv*
+*   Automatically guess the inverse associations for STI.
-*   Fixed support for case insensitive comparisons of `text` columns in
-    PostgreSQL.
+    *Yuichiro Kaneko*
-    *Edho Arief*
+*   Ensure `sum` honors `distinct` on `has_many :through` associations.
-*   Serialize JSON attribute value `nil` as SQL `NULL`, not JSON `null`.
+    Fixes #16791.
-    *Trung Duc Tran*
+    *Aaron Wortham*
-*   Return `true` from `update_attribute` when the value of the attribute
-    to be updated is unchanged.
+*   Add `binary` fixture helper method.
-    Fixes #26593.
+    *Atsushi Yoshida*
-    *Prathamesh Sonpatki*
+*   When using `Relation#or`, extract the common conditions and put them before the OR condition.
-*   Always store errors details information with symbols.
+    *Maxime Handfield Lapointe*
-    When the association is autosaved we were storing the details with
-    string keys. This was creating inconsistency with other details that are
-    added using the `Errors#add` method. It was also inconsistent with the
-    `Errors#messages` storage.
+*   `Relation#or` now accepts two relations who have different values for
+    `references` only, as `references` can be implicitly called by `where`.
-    To fix this inconsistency we are always storing with symbols. This will
-    cause a small breaking change because in those cases the details could
-    be accessed as strings keys but now it can not.
+    Fixes #29411.
-    Fix #26499.
+    *Sean Griffin*
-    *Rafael Mendonça França*, *Marcus Vieira*
+*   `ApplicationRecord` is no longer generated when generating models. If you
+    need to generate it, it can be created with `rails g application_record`.
-*   Calling `touch` on a model using optimistic locking will now leave the model
-    in a non-dirty state with no attribute changes.
+    *Lisa Ugray*
-    Fixes #26496.
+*   Fix `COUNT(DISTINCT ...)` with `ORDER BY` and `LIMIT` to keep the existing select list.
-    *Jakob Skjerning*
+    *Ryuta Kamizono*
-*   Using a mysql2 connection after it fails to reconnect will now have an error message
-    saying the connection is closed rather than an undefined method error message.
+*   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.
-    *Dylan Thacker-Smith*
+    *Lisa Ugray*
-*   PostgreSQL array columns will now respect the encoding of strings contained
-    in the array.
+*   Fix `unscoped(where: [columns])` removing the wrong bind values.
-    Fixes #26326.
+    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)
-    *Sean Griffin*
+    ```
+    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)
+    ```
-*   Inverse association instances will now be set before `after_find` or
-    `after_initialize` callbacks are run.
+    *Maxime Handfield Lapointe*
-    Fixes #26320.
+*   Values constructed using multi-parameter assignment will now use the
+    post-type-cast value for rendering in single-field form inputs.
     *Sean Griffin*
-*   Remove unnecessarily association load when a `belongs_to` association has already been
-    loaded then the foreign key is changed directly and the record saved.
+*   `Relation#joins` is no longer affected by the target model's
+    `current_scope`, with the exception of `unscoped`.
-    *James Coleman*
+    Fixes #29338.
-*   Remove standardized column types/arguments spaces in schema dump.
+    *Sean Griffin*
-    *Tim Petricola*
+*   Change sqlite3 boolean serialization to use 1 and 0.
-*   Avoid loading records from database when they are already loaded using
-    the `pluck` method on a collection.
+    SQLite natively recognizes 1 and 0 as true and false, but does not natively
+    recognize 't' and 'f' as was previously serialized.
-    Fixes #25921.
+    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.
-    *Ryuta Kamizono*
+    *Lisa Ugray*
-*   Remove text default treated as an empty string in non-strict mode for
-    consistency with other types.
-    Strict mode controls how MySQL handles invalid or missing values in
-    data-change statements such as INSERT or UPDATE. If strict mode is not
-    in effect, MySQL inserts adjusted values for invalid or missing values
-    and produces warnings.
-        def test_mysql_not_null_defaults_non_strict
-          using_strict(false) do
-            with_mysql_not_null_table do |klass|
-              record = klass.new
-              assert_nil record.non_null_integer
-              assert_nil record.non_null_string
-              assert_nil record.non_null_text
-              assert_nil record.non_null_blob
-              record.save!
-              record.reload
-              assert_equal 0,  record.non_null_integer
-              assert_equal "", record.non_null_string
-              assert_equal "", record.non_null_text
-              assert_equal "", record.non_null_blob
-            end
-          end
-        end
+*   Skip query caching when working with batches of records (`find_each`, `find_in_batches`,
+    `in_batches`).
-    https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sql-mode-strict
+    Previously, records would be fetched in batches, but all records would be retained in memory
+    until the end of the request or job.
-    *Ryuta Kamizono*
+    *Eugene Kenny*
-*   SQLite3 migrations to add a column to an existing table can now be
-    successfully rolled back when the column was given and invalid column
-    type.
+*   Prevent errors raised by `sql.active_record` notification subscribers from being converted into
+    `ActiveRecord::StatementInvalid` exceptions.
-    Fixes #26087.
+    *Dennis Taylor*
-    *Travis O'Neill*
+*   Fix eager loading/preloading association with scope including joins.
-*   Deprecate `sanitize_conditions`. Use `sanitize_sql` instead.
+    Fixes #28324.
     *Ryuta Kamizono*
-*   Doing count on relations that contain LEFT OUTER JOIN Arel node no longer
-    force a DISTINCT. This solves issues when using count after a left_joins.
-    *Maxime Handfield Lapointe*
+*   Fix transactions to apply state to child transactions.
-*   RecordNotFound raised by association.find exposes `id`, `primary_key` and
-    `model` methods to be consistent with RecordNotFound raised by Record.find.
+    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.
-    *Michel Pigassou*
+    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.
-*   Hashes can once again be passed to setters of `composed_of`, if all of the
-    mapping methods are methods implemented on `Hash`.
+    *Eileen M. Uchitelle*, *Aaron Patterson*
-    Fixes #25978.
+*   Deprecate `set_state` method in `TransactionState`.
-    *Sean Griffin*
+    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)`.
-*   Fix the SELECT statement in `#table_comment` for MySQL.
+    *Eileen M. Uchitelle*, *Aaron Patterson*
-    *Takeshi Akima*
+*   Deprecate delegating to `arel` in `Relation`.
-*   Virtual attributes will no longer raise when read on models loaded from the
-    database.
+    *Ryuta Kamizono*
-    *Sean Griffin*
+*   Query cache was unavailable when entering the `ActiveRecord::Base.cache` block
+    without being connected.
-*   Support calling the method `merge` in `scope`'s lambda.
+    *Tsukasa Oishi*
-    *Yasuhiro Sugino*
+*   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.
-*   Fixes multi-parameter attributes conversion with invalid params.
+    *Tobias Kraze*
-    *Hiroyuki Ishii*
+*   Merging two relations representing nested joins no longer transforms the joins of
+    the merged relation into LEFT OUTER JOIN.
-*   Add newline between each migration in `structure.sql`.
+    Example:
-    Keeps schema migration inserts as a single commit, but allows for easier
-    git diffing.
+    ```
+    Author.joins(:posts).merge(Post.joins(:comments))
+    # Before the change:
+    #=> SELECT ... FROM authors INNER JOIN posts ON ... LEFT OUTER JOIN comments ON...
-    Fixes #25504.
+    # After the change:
+    #=> SELECT ... FROM authors INNER JOIN posts ON ... INNER JOIN comments ON...
+    ```
-    *Grey Baker*, *Norberto Lopes*
+    *Maxime Handfield Lapointe*
-*   The flag `error_on_ignored_order_or_limit` has been deprecated in favor of
-    the current `error_on_ignored_order`.
+*   `ActiveRecord::Persistence#touch` does not work well when optimistic locking enabled and
+    `locking_column`, without default value, is null in the database.
-    *Xavier Noria*
+    *bogdanvlviv*
-*   Batch processing methods support `limit`:
+*   Fix destroying existing object does not work well when optimistic locking enabled and
+    `locking_column` is null in the database.
-        Post.limit(10_000).find_each do |post|
-          # ...
-        end
+    *bogdanvlviv*
-    It also works in `find_in_batches` and `in_batches`.
+*   Use bulk INSERT to insert fixtures for better performance.
-    *Xavier Noria*
+    *Kir Shatrov*
-*   Using `group` with an attribute that has a custom type will properly cast
-    the hash keys after calling a calculation method like `count`.
+*   Prevent creation of bind param if casted value is nil.
-    Fixes #25595.
+    *Ryuta Kamizono*
-    *Sean Griffin*
+*   Deprecate passing arguments and block at the same time to `count` and `sum` in `ActiveRecord::Calculations`.
-*   Fix the generated `#to_param` method to use `omission: ''` so that
-    the resulting output is actually up to 20 characters, not
-    effectively 17 to leave room for the default "...".
-    Also call `#parameterize` before `#truncate` and make the
-    `separator: /-/` to maximize the information included in the
-    output.
+    *Ryuta Kamizono*
-    Fixes #23635.
+*   Loading model schema from database is now thread-safe.
-    *Rob Biedenharn*
+    Fixes #28589.
-*   Ensure concurrent invocations of the connection reaper cannot allocate the
-    same connection to two threads.
+    *Vikrant Chaudhary*, *David Abdemoulaie*
-    Fixes #25585.
+*   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.
-    *Matthew Draper*
+    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+
-*   Inspecting an object with an associated array of over 10 elements no longer
-    truncates the array, preventing `inspect` from looping infinitely in some
-    cases.
+    *DHH*
-    *Kevin McPhillips*
+*   Respect `SchemaDumper.ignore_tables` in rake tasks for databases structure dump.
-*   Removed the unused methods `ActiveRecord::Base.connection_id` and
-    `ActiveRecord::Base.connection_id=`.
+    *Rusty Geldmacher*, *Guillermo Iguaran*
-    *Sean Griffin*
+*   Add type caster to `RuntimeReflection#alias_name`.
-*   Ensure hashes can be assigned to attributes created using `composed_of`.
+    Fixes #28959.
-    Fixes #25210.
+    *Jon Moss*
-    *Sean Griffin*
+*   Deprecate `supports_statement_cache?`.
-*   Fix logging edge case where if an attribute was of the binary type and
-    was provided as a Hash.
+    *Ryuta Kamizono*
-    *Jon Moss*
+*   Raise error `UnknownMigrationVersionError` on the movement of migrations
+    when the current migration does not exist.
-*   Handle JSON deserialization correctly if the column default from database
-    adapter returns `''` instead of `nil`.
+    *bogdanvlviv*
-    *Johannes Opper*
+*   Fix `bin/rails db:forward` first migration.
-*   Introduce new Active Record transaction error classes for catching
-    transaction serialization failures or deadlocks.
+    *bogdanvlviv*
-    *Erol Fornoles*
+*   Support Descending Indexes for MySQL.
-*   PostgreSQL: Fix `db:structure:load` silent failure on SQL error.
+    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.
-    The command line flag `-v ON_ERROR_STOP=1` should be used
-    when invoking `psql` to make sure errors are not suppressed.
+    *Ryuta Kamizono*
-    Example:
+*   Fix inconsistency with changed attributes when overriding Active Record attribute reader.
-        psql -v ON_ERROR_STOP=1 -q -f awesome-file.sql my-app-db
+    *bogdanvlviv*
-    Fixes #23818.
+*   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.
-    *Ralin Chimev*
+    *Kevin McPhillips*
-Please check [5-0-stable](https://github.com/rails/rails/blob/5-0-stable/activerecord/CHANGELOG.md) for previous changes.
+Please check [5-1-stable](https://github.com/rails/rails/blob/5-1-stable/activerecord/CHANGELOG.md) for previous changes.