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

activerecord 5.1.6.2 → 5.2.8.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (261) hide show

data/CHANGELOG.md CHANGED Viewed

@@ -1,1099 +1,1084 @@
-## Rails 5.1.6.2 (March 11, 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]
+    ```
-*   No changes.
+    [CVE-2022-32224]
-## Rails 5.1.6.1 (November 27, 2018) ##
+## Rails 5.2.8 (May 09, 2022) ##
 *   No changes.
-## Rails 5.1.6 (March 29, 2018) ##
+## Rails 5.2.7.1 (April 26, 2022) ##
-*   MySQL: Support mysql2 0.5.x.
+*   No changes.
-    *Aaron Stone*
-*   Apply time column precision on assignment.
+## Rails 5.2.7 (March 10, 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.3 (March 08, 2022) ##
-*   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.6.2 (February 11, 2022) ##
-*   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.6.1 (February 11, 2022) ##
-*   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.6 (May 05, 2021) ##
-    *bogdanvlviv*
+*   No changes.
-*   Fix destroying existing object does not work well when optimistic locking enabled and
-    `locking column` is null in the database.
-    *bogdanvlviv*
+## Rails 5.2.5 (March 26, 2021) ##
+*   No changes.
-## Rails 5.1.5 (February 14, 2018) ##
-*   PostgreSQL: Allow pg-1.0 gem to be used with Active Record.
+## Rails 5.2.4.6 (May 05, 2021) ##
-    *Lars Kanis*
+*   No changes.
-*   Fix `count(:all)` with eager loading and having an order other than the driving table.
-    Fixes #31783.
+## Rails 5.2.4.5 (February 10, 2021) ##
-    *Ryuta Kamizono*
+*   Fix possible DoS vector in PostgreSQL money type
-*   Use `count(:all)` in `HasManyAssociation#count_records` to prevent invalid
-    SQL queries for association counting.
+    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.
-    *Klas Eskilson*
+    Thanks to @dee-see from Hackerone for this patch!
-*   Fix to invoke callbacks when using `update_attribute`.
+    [CVE-2021-22880]
-    *Mike Busch*
+    *Aaron Patterson*
-*   Fix `count(:all)` to correctly work `distinct` with custom SELECT list.
-    *Ryuta Kamizono*
+## Rails 5.2.4.4 (September 09, 2020) ##
-*   Fix conflicts `counter_cache` with `touch: true` by optimistic locking.
+*   No changes.
-    ```
-    # create_table :posts do |t|
-    #   t.integer :comments_count, default: 0
-    #   t.integer :lock_version
-    #   t.timestamps
-    # end
-    class Post < ApplicationRecord
-    end
-    # create_table :comments do |t|
-    #   t.belongs_to :post
-    # end
-    class Comment < ApplicationRecord
-      belongs_to :post, touch: true, counter_cache: true
-    end
-    ```
+## Rails 5.2.4.3 (May 18, 2020) ##
-    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
+*   No changes.
-    comment = Comment.create!(post: post)
-    # => begin transaction
-         INSERT INTO "comments" ("post_id") VALUES (1)
+## Rails 5.2.4.2 (March 19, 2020) ##
-         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) + 1,
-         "lock_version" = COALESCE("lock_version", 0) + 1 WHERE "posts"."id" = 1
+*   No changes.
-         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
+## Rails 5.2.4.1 (December 18, 2019) ##
-         UPDATE "posts" SET "comments_count" = COALESCE("comments_count", 0) - 1,
-         "lock_version" = COALESCE("lock_version", 0) + 1 WHERE "posts"."id" = 1
+*   No changes.
-         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.
-    ```
-    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
+## Rails 5.2.4 (November 27, 2019) ##
-    comment = Comment.create!(post: post)
-    # => begin transaction
-         INSERT INTO "comments" ("post_id") VALUES (1)
+*   Fix circular `autosave: true` causes invalid records to be saved.
-         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
+    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.destroy!
-    # => begin transaction
-         DELETE FROM "comments" WHERE "comments"."id" = 1
+    Fixes #28080.
-         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
-    ```
+    *Larry Reid*
-    Fixes #31199.
+*   PostgreSQL: Fix GROUP BY with ORDER BY virtual count attribute.
-    *bogdanvlviv*
+    Fixes #36022.
-*   Query cache was unavailable when entering the `ActiveRecord::Base.cache` block
-    without being connected.
+    *Ryuta Kamizono*
-    *Tsukasa Oishi*
+*   Fix sqlite3 collation parsing when using decimal columns.
-*   Fix `bin/rails db:setup` and `bin/rails db:test:prepare` create  wrong
-    ar_internal_metadata's data for a test database.
+    *Martin R. Schuster*
-    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
-    ```
+*   Make ActiveRecord `ConnectionPool.connections` method thread-safe.
-    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
-    ```
+    Fixes #36465.
-    Fixes #26731.
+    *Jeff Doering*
-    *bogdanvlviv*
+*   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.
-*   Fix longer sequence name detection for serial columns.
+    Fixes #33249.
-    Fixes #28332.
+    *Ryan H. Kerr*
-    *Ryuta Kamizono*
-*   MySQL: Don't lose `auto_increment: true` in the `db/schema.rb`.
+## Rails 5.2.3 (March 27, 2019) ##
-    Fixes #30894.
+*   Fix different `count` calculation when using `size` with manual `select` with DISTINCT.
-    *Ryuta Kamizono*
+    Fixes #35214.
-*   Fix `COUNT(DISTINCT ...)` for `GROUP BY` with `ORDER BY` and `LIMIT`.
+    *Juani Villarejo*
-    Fixes #30886.
+*   Fix prepared statements caching to be enabled even when query caching is enabled.
     *Ryuta Kamizono*
+*   Don't allow `where` with invalid value matches to nil values.
-## Rails 5.1.4 (September 07, 2017) ##
-*   No changes.
+    Fixes #33624.
-## Rails 5.1.4.rc1 (August 24, 2017) ##
-*   Ensure `sum` honors `distinct` on `has_many :through` associations
-    Fixes #16791
+    *Ryuta Kamizono*
-    *Aaron Wortham
+*   Restore an ability that class level `update` without giving ids.
-*   Fix `COUNT(DISTINCT ...)` with `ORDER BY` and `LIMIT` to keep the existing select list.
+    Fixes #34743.
     *Ryuta Kamizono*
-*   Fix `unscoped(where: [columns])` removing the wrong bind values
+*   Fix join table column quoting with SQLite.
-    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)
-    ```
+*   Ensure that `delete_all` on collection proxy returns affected count.
-    *Maxime Handfield Lapointe*
+    *Ryuta Kamizono*
-*   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.
+*   Reset scope after delete on collection association to clear stale offsets of removed records.
-    *Lisa Ugray*
+    *Gannon McGibbon*
-## Rails 5.1.3 (August 03, 2017) ##
+## Rails 5.2.2.1 (March 11, 2019) ##
 *   No changes.
-## Rails 5.1.3.rc3 (July 31, 2017) ##
-*   No changes.
+## Rails 5.2.2 (December 04, 2018) ##
+*   Do not ignore the scoping with query methods in the scope block.
-## Rails 5.1.3.rc2 (July 25, 2017) ##
+    *Ryuta Kamizono*
-*   No changes.
+*   Allow aliased attributes to be used in `#update_columns` and `#update`.
+    *Gannon McGibbon*
-## Rails 5.1.3.rc1 (July 19, 2017) ##
+*   Allow spaces in postgres table names.
-*   `Relation#joins` is no longer affected by the target model's
-    `current_scope`, with the exception of `unscoped`.
+    Fixes issue where "user post" is misinterpreted as "\"user\".\"post\"" when quoting table names with the postgres
+    adapter.
-    Fixes #29338.
+    *Gannon McGibbon*
-    *Sean Griffin*
+*   Cached columns_hash fields should be excluded from ResultSet#column_types
-*   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.
+    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:
-    *Tobias Kraze*
+    ```ruby
+    class DeveloperName < ActiveRecord::Type::String
+      def deserialize(value)
+        "Developer: #{value}"
+      end
+    end
+    class AttributedDeveloper < ActiveRecord::Base
+      self.table_name = "developers"
-## Rails 5.1.2 (June 26, 2017) ##
+      attribute :name, DeveloperName.new
-*   Restore previous behavior of collection proxies: their values can have
-    methods stubbed, and they respect extension modules applied by a default
-    scope.
+      self.ignored_columns += ["name"]
+    end
-    *Ryuta Kamizono*
+    developer = AttributedDeveloper.create
+    developer.update_column :name, "name"
-*   Loading model schema from database is now thread-safe.
+    loaded_developer = AttributedDeveloper.where(id: developer.id).select("*").first
+    puts loaded_developer.name # should be "Developer: name" but it's just "name"
+    ```
-    Fixes #28589.
+    *Dmitry Tsepelev*
-    *Vikrant Chaudhary*, *David Abdemoulaie*
+*   Values of enum are frozen, raising an error when attempting to modify them.
+    *Emmanuel Byrd*
-## Rails 5.1.1 (May 12, 2017) ##
+*   `update_columns` now correctly raises `ActiveModel::MissingAttributeError`
+    if the attribute does not exist.
-*   Add type caster to `RuntimeReflection#alias_name`
+    *Sean Griffin*
-    Fixes #28959.
+*   Do not use prepared statement in queries that have a large number of binds.
-    *Jon Moss*
+    *Ryuta Kamizono*
+*   Fix query cache to load before first request.
-## Rails 5.1.0 (April 27, 2017) ##
+    *Eileen M. Uchitelle*
-*   Quote database name in db:create grant statement (when database_user does not have access to create the database).
+*   Fix collection cache key with limit and custom select to avoid ambiguous timestamp column error.
-    *Rune Philosof*
+    Fixes #33056.
-*   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.
+    *Federico Martinez*
-    Fixes #28197.
+*   Fix duplicated record creation when using nested attributes with `create_with`.
-    *Matthew Draper*
+    *Darwin Wu*
-*   Load only needed records on `ActiveRecord::Relation#inspect`.
+*   Fix regression setting children record in parent `before_save` callback.
-    Instead of loading all records and returning only a subset of those, just
-    load the records as needed.
+    *Guo Xiang Tan*
-    Fixes #25537.
+*   Prevent leaking of user's DB credentials on `rails db:create` failure.
-    *Hendy Tanata*
+    *bogdanvlviv*
-*   Remove comments from structure.sql when using postgresql adapter to avoid
-    version-specific parts of the file.
+*   Clear mutation tracker before continuing the around callbacks.
-    Fixes #28153.
+    *Yuya Tanaka*
-    *Ari Pollak*
+*   Prevent deadlocks when waiting for connection from pool.
-*   Add `:default` option to `belongs_to`.
+    *Brent Wheeldon*
-    Use it to specify that an association should be initialized with a particular
-    record before validation. For example:
+*   Avoid extra scoping when using `Relation#update` that was causing this method to change the current scope.
-        # Before
-        belongs_to :account
-        before_validation -> { self.account ||= Current.account }
+    *Ryuta Kamizono*
-        # After
-        belongs_to :account, default: -> { Current.account }
+*   Fix numericality validator not to be affected by custom getter.
-    *George Claghorn*
+    *Ryuta Kamizono*
-*   Deprecate `Migrator.schema_migrations_table_name`.
+*   Fix bulk change table ignores comment option on PostgreSQL.
-    *Ryuta Kamizono*
+    *Yoshiyuki Kinjo*
-*   Fix select with block doesn't return newly built records in has_many association.
-    Fixes #28348.
+## Rails 5.2.1.1 (November 27, 2018) ##
-    *Ryuta Kamizono*
+*   No changes.
-*   Check whether `Rails.application` defined before calling it
-    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.
+## Rails 5.2.1 (August 07, 2018) ##
-    Fixes #28325.
+*   PostgreSQL: Support new relkind for partitioned tables.
-    *Andrew White*
+    Fixes #33008.
-*   Fix `deserialize` with JSON array.
+    *Yannick Schutz*
-    Fixes #28285.
+*   Rollback parent transaction when children fails to update.
-    *Ryuta Kamizono*
+    *Guillaume Malette*
-*   Fix `rake db:schema:load` with subdirectories.
+*   Fix default value for MySQL time types with specified precision.
-    *Ryuta Kamizono*
+    *Nikolay Kondratyev*
-*   Fix `rake db:migrate:status` with subdirectories.
+*   Fix `touch` option to behave consistently with `Persistence#touch` method.
     *Ryuta Kamizono*
-*   Don't share options between reference id and type columns
+*   Fix `save` in `after_create_commit` won't invoke extra `after_create_commit`.
-    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 #32831.
     *Ryuta Kamizono*
-*   Use `max_identifier_length` for `index_name_length` in PostgreSQL adapter.
+*   Fix logic on disabling commit callbacks so they are not called unexpectedly when errors occur.
-    *Ryuta Kamizono*
+    *Brian Durand*
-*   Deprecate `supports_migrations?` on connection adapters.
+*   Fix parent record should not get saved with duplicate children records.
-    *Ryuta Kamizono*
+    Fixes #32940.
-*   Fix regression of #1969 with SELECT aliases in HAVING clause.
+    *Santosh Wadghule*
-    *Eugene Kenny*
+*   Fix that association's after_touch is not called with counter cache.
-*   Deprecate using `#quoted_id` in quoting.
+    Fixes #31559.
     *Ryuta Kamizono*
-*   Fix `wait_timeout` to configurable for mysql2 adapter.
+*   `becomes` should clear the mutation tracker which is created in `after_initialize`.
-    Fixes #26556.
+    Fixes #32867.
     *Ryuta Kamizono*
-*   Correctly dump native timestamp types for MySQL.
-    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.
+*   Allow a belonging to parent object to be created from a new record.
-        > SET time_zone = '+00:00';
-        Query OK, 0 rows affected (0.00 sec)
+    *Jolyon Pawlyn*
-        > INSERT INTO time_with_zone(ts,dt) VALUES (NOW(),NOW());
-        Query OK, 1 row affected (0.02 sec)
+*   Fix that building record with assigning multiple has_one associations
+    wrongly persists through record.
-        > 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)
+    Fixes #32511.
-        > SET time_zone = '-08:00';
-        Query OK, 0 rows affected (0.00 sec)
+    *Sam DeCesare*
-        > 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)
+*   Fix relation merging when one of the relations is going to skip the
+    query cache.
-    *Ryuta Kamizono*
-*   All integer-like PKs are autoincrement unless they have an explicit default.
+    *James Williams*
-    *Matthew Draper*
-*   Omit redundant `using: :btree` for schema dumping.
+## Rails 5.2.0 (April 09, 2018) ##
-    *Ryuta Kamizono*
+*   MySQL: Support mysql2 0.5.x.
-*   Deprecate passing `default` to `index_name_exists?`.
+    *Aaron Stone*
-    *Ryuta Kamizono*
+*   Apply time column precision on assignment.
-*   PostgreSQL: schema dumping support for interval and OID columns.
+    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.
-    *Ryuta Kamizono*
+    Fixes #30301.
-*   Deprecate `supports_primary_key?` on connection adapters since it's
-    been long unused and unsupported.
+    *Andrew White*
-    *Ryuta Kamizono*
+*   Normalize time column values for SQLite database.
-*   Make `table_name=` reset current statement cache,
-    so queries are not run against the previous table name.
+    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.
-    *namusyaka*
+    *Andrew White*
-*   Allow `ActiveRecord::Base#as_json` to be passed a frozen Hash.
+*   Ensure that the date component is removed when quoting times.
-    *Isaac Betesh*
+    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.
-*   Fix inspection behavior when the :id column is not primary key.
+    *Andrew White*
-    *namusyaka*
+*   Fix `dependent: :destroy` issue for has_one/belongs_to relationship where
+    the parent class was getting deleted when the child was not.
-*   Deprecate locking records with unpersisted changes.
+    Fixes #32022.
-    *Marc Schütz*
+    *Fernando Gorodscy*
-*   Remove deprecated behavior that halts callbacks when the return is false.
+*   Whitelist `NULLS FIRST` and `NULLS LAST` in order clauses too.
-    *Rafael Mendonça França*
+    *Xavier Noria*
-*   Deprecate `ColumnDumper#migration_keys`.
+*   Fix that after commit callbacks on update does not triggered when optimistic locking is enabled.
     *Ryuta Kamizono*
-*   Fix `association_primary_key_type` for reflections with symbol primary key.
+*   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.
-    Fixes #27864.
+    Fixes #28364.
-    *Daniel Colson*
+    *Takumi Kagiyama*
-*   Virtual/generated column support for MySQL 5.7.5+ and MariaDB 5.2.0+.
+*   Make `reflection.klass` raise if `polymorphic?` not to be misused.
-    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 #31876.
-    Declare virtual columns with `t.virtual name, type: …, as: "expression"`.
-    Pass `stored: true` to persist the generated value (false by default).
+    *Ryuta Kamizono*
-    Example:
+*   PostgreSQL: Allow pg-1.0 gem to be used with Active Record.
-        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
+    *Lars Kanis*
+*   Deprecate `expand_hash_conditions_for_aggregates` without replacement.
+    Using a `Relation` for performing queries is the prefered API.
     *Ryuta Kamizono*
-*   Deprecate `initialize_schema_migrations_table` and `initialize_internal_metadata_table`.
+*   Fix not expanded problem when passing an Array object as argument to the where method using `composed_of` column.
-    *Ryuta Kamizono*
+    ```
+    david_balance = customers(:david).balance
+    Customer.where(balance: [david_balance]).to_sql
-*   Support foreign key creation for SQLite3.
+    # Before: WHERE `customers`.`balance` = NULL
+    # After : WHERE `customers`.`balance` = 50
+    ```
-    *Ryuta Kamizono*
+    Fixes #31723.
-*   Place generated migrations into the path set by `config.paths["db/migrate"]`.
+    *Yutaro Kanagawa*
-    *Kevin Glowacz*
+*   Fix `count(:all)` with eager loading and having an order other than the driving table.
-*   Raise `ActiveRecord::InvalidForeignKey` when a foreign key constraint fails on SQLite3.
+    Fixes #31783.
     *Ryuta Kamizono*
-*   Add the touch option to `#increment!` and `#decrement!`.
+*   Clear the transaction state when an Active Record object is duped.
-    *Hiroaki Izu*
+    Fixes #31670.
-*   Deprecate passing a class to the `class_name` because it eagerloads more classes than
-    necessary and potentially creates circular dependencies.
+    *Yuriy Ustushenko*
-    *Kir Shatrov*
+*   Support for PostgreSQL foreign tables.
-*   Raise error when has_many through is defined before through association.
+    *fatkodima*
-    Fixes #26834.
+*   Fix relation merger issue with `left_outer_joins`.
-    *Chris Holmes*
+    *Mehmet Emin İNAÇ*
-*   Deprecate passing `name` to `indexes`.
+*   Don't allow destroyed object mutation after `save` or `save!` is called.
     *Ryuta Kamizono*
-*   Remove deprecated tasks: `db:test:clone`, `db:test:clone_schema`, `db:test:clone_structure`.
+*   Take into account association conditions when deleting through records.
-    *Rafel Mendonça França*
+    Fixes #18424.
-*   Compare deserialized values for `PostgreSQL::OID::Hstore` types when
-    calling `ActiveRecord::Dirty#changed_in_place?`.
+    *Piotr Jakubowski*
-    Fixes #27502.
+*   Fix nested `has_many :through` associations on unpersisted parent instances.
-    *Jon Moss*
+    For example, if you have
-*   Raise `ArgumentError` when passing an `ActiveRecord::Base` instance to `.find`,
-    `.exists?` and `.update`.
+        class Post < ActiveRecord::Base
+          belongs_to :author
+          has_many :books, through: :author
+          has_many :subscriptions, through: :books
+        end
-    *Rafael Mendonça França*
+        class Author < ActiveRecord::Base
+          has_one :post
+          has_many :books
+          has_many :subscriptions, through: :books
+        end
-*   Respect precision option for arrays of timestamps.
+        class Book < ActiveRecord::Base
+          belongs_to :author
+          has_many :subscriptions
+        end
-    Fixes #27514.
+        class Subscription < ActiveRecord::Base
+          belongs_to :book
+        end
-    *Sean Griffin*
+    Before:
-*   Optimize slow model instantiation when using STI and `store_full_sti_class = false` option.
+    If `post` is not persisted, then `post.subscriptions` will be empty.
-    *Konstantin Lazarev*
+    After:
-*   Add `touch` option to counter cache modifying methods.
+    If `post` is not persisted, then `post.subscriptions` can be set and used
+    just like it would if `post` were persisted.
-    Works when updating, resetting, incrementing and decrementing counters:
+    Fixes #16313.
-        # Touches `updated_at`/`updated_on`.
-        Topic.increment_counter(:messages_count, 1, touch: true)
-        Topic.decrement_counter(:messages_count, 1, touch: true)
+    *Zoltan Kiss*
-        # Touches `last_discussed_at`.
-        Topic.reset_counters(18, :messages, touch: :last_discussed_at)
+*   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)`.
-        # Touches `updated_at` and `last_discussed_at`.
-        Topic.update_counters(18, messages_count: 5, touch: %i( updated_at last_discussed_at ))
+    Fixes #23979.
-    Fixes #26724.
+    *Brian Christian*
-    *Jarred Trost*
+*   Use `count(:all)` in `HasManyAssociation#count_records` to prevent invalid
+    SQL queries for association counting.
-*   Remove deprecated `#uniq`, `#uniq!`, and `#uniq_value`.
+    *Klas Eskilson*
-    *Ryuta Kamizono*
+*   Fix to invoke callbacks when using `update_attribute`.
-*   Remove deprecated `#insert_sql`, `#update_sql`, and `#delete_sql`.
+    *Mike Busch*
-    *Ryuta Kamizono*
+*   Fix `count(:all)` to correctly work `distinct` with custom SELECT list.
-*   Remove deprecated `#use_transactional_fixtures` configuration.
+    *Ryuta Kamizono*
-    *Rafael Mendonça França*
+*   Using subselect for `delete_all` with `limit` or `offset`.
-*   Remove deprecated `#raise_in_transactional_callbacks` configuration.
+    *Ryuta Kamizono*
-    *Rafael Mendonça França*
+*   Undefine attribute methods on descendants when resetting column
+    information.
-*   Remove deprecated `#load_schema_for`.
+    *Chris Salzberg*
-    *Rafael Mendonça França*
+*   Log database query callers.
-*   Remove deprecated conditions parameter from `#destroy_all` and `#delete_all`.
+    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.
-    *Rafael Mendonça França*
+    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 support to passing arguments to `#select` when a block is provided.
+    *Olivier Lacan*
-    *Rafael Mendonça França*
+*   Fix conflicts `counter_cache` with `touch: true` by optimistic locking.
-*   Remove deprecated support to query using commas on LIMIT.
+    ```
+    # 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 support to passing a class as a value in a query.
+    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)
-*   Raise `ActiveRecord::IrreversibleOrderError` when using `last` with an irreversible
-    order.
+         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.
-*   Raise when a `has_many :through` association has an ambiguous reflection name.
+    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
-*   Raise when `ActiveRecord::Migration` is inherited from directly.
+         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 `original_exception` argument in `ActiveRecord::StatementInvalid#initialize`
-    and `ActiveRecord::StatementInvalid#original_exception`.
+    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
-*   `#tables` and `#table_exists?` return only tables and not views.
+    comment.destroy!
+    # => begin transaction
+         DELETE FROM "comments" WHERE "comments"."id" = 1
-    All the deprecations on those methods were removed.
+         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
+    ```
-    *Rafael Mendonça França*
+    Fixes #31199.
-*   Remove deprecated `name` argument from `#tables`.
+    *bogdanvlviv*
-    *Rafael Mendonça França*
+*   Add support for PostgreSQL operator classes to `add_index`.
-*   Remove deprecated support to passing a column to `#quote`.
+    Example:
-    *Rafael Mendonça França*
+        add_index :users, :name, using: :gist, opclass: { name: :gist_trgm_ops }
-*   Set `:time` as a timezone aware type and remove deprecation when
-    `config.active_record.time_zone_aware_types` is not explicitly set.
+    *Greg Navis*
-    *Rafael Mendonça França*
+*   Don't allow scopes to be defined which conflict with instance methods on `Relation`.
-*   Remove deprecated force reload argument in singular and collection association readers.
+    Fixes #31120.
-    *Rafael Mendonça França*
+    *kinnrot*
-*   Remove deprecated `activerecord.errors.messages.restrict_dependent_destroy.one` and
-    `activerecord.errors.messages.restrict_dependent_destroy.many` i18n scopes.
+*   Add new error class `QueryCanceled` which will be raised
+    when canceling statement due to user request.
-    *Rafael Mendonça França*
+    *Ryuta Kamizono*
-*   Allow passing extra flags to `db:structure:load` and `db:structure:dump`
+*   Add `#up_only` to database migrations for code that is only relevant when
+    migrating up, e.g. populating a new column.
-    Introduces `ActiveRecord::Tasks::DatabaseTasks.structure_(load|dump)_flags` to customize the
-    eventual commands run against the database, e.g. mysqldump/pg_dump.
+    *Rich Daley*
-    *Kir Shatrov*
+*   Require raw SQL fragments to be explicitly marked when used in
+    relation query methods.
-*   Notifications see frozen SQL string.
+    Before:
+    ```
+    Article.order("LENGTH(title)")
+    ```
-    Fixes #23774.
+    After:
+    ```
+    Article.order(Arel.sql("LENGTH(title)"))
+    ```
-    *Richard Monette*
+    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.
-*   RuntimeErrors are no longer translated to `ActiveRecord::StatementInvalid`.
+    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`.
-    *Richard Monette*
+    Common and judged-safe string values (such as simple column
+    references) are unaffected:
+    ```
+    Article.order("title DESC")
+    ```
-*   Change the schema cache format to use YAML instead of Marshal.
+    *Ben Toews*
-    *Kir Shatrov*
+*   `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.
-*   Support index length and order options using both string and symbol
-    column names.
+    *Sean Griffin*
-    Fixes #27243.
+*   Add new error class `StatementTimeout` which will be raised
+    when statement timeout exceeded.
     *Ryuta Kamizono*
-*   Raise `ActiveRecord::RangeError` when values that executed are out of range.
+*   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.
-    *Ryuta Kamizono*
+    *bogdanvlviv*
-*   Raise `ActiveRecord::NotNullViolation` when a record cannot be inserted
-    or updated because it would violate a not null constraint.
+*   Fixed a bug where column orders for an index weren't written to
+    `db/schema.rb` when using the sqlite adapter.
-    *Ryuta Kamizono*
+    Fixes #30902.
-*   Emulate db trigger behaviour for after_commit :destroy, :update.
+    *Paul Kuruvilla*
-    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 method `#sanitize_conditions`.
-    *Stefan Budeanu*
+    *Rafael Mendonça França*
-*   Moved `DecimalWithoutScale`, `Text`, and `UnsignedInteger` from Active Model to Active Record.
+*   Remove deprecated method `#scope_chain`.
-    *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 configuration `.error_on_ignored_order_or_limit`.
-    *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 arguments from `#verify!`.
-    Fixes #26417.
+    *Rafael Mendonça França*
-    *Prathamesh Sonpatki*
+*   Remove deprecated argument `name` from `#indexes`.
-*   PostgreSQL & MySQL: Use big integer as primary key type for new tables.
+    *Rafael Mendonça França*
-    *Jon McCartie*, *Pavel Pravosud*
+*   Remove deprecated method `ActiveRecord::Migrator.schema_migrations_table_name`.
-*   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 method `supports_primary_key?`.
-*   Don't treat unsigned integers with zerofill as signed.
+    *Rafael Mendonça França*
-    Fixes #27125.
+*   Remove deprecated method `supports_migrations?`.
-    *Ryuta Kamizono*
+    *Rafael Mendonça França*
-*   Fix the uniqueness validation scope with a polymorphic association.
+*   Remove deprecated methods `initialize_schema_migrations_table` and `initialize_internal_metadata_table`.
-    *Sergey Alekseev*
+    *Rafael Mendonça França*
-*   Raise `ActiveRecord::RecordNotFound` from collection `*_ids` setters
-    for unknown IDs with a better error message.
+*   Raises when calling `lock!` in a dirty record.
-    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.
+    *Rafael Mendonça França*
-    *Dominic Cleal*
+*   Remove deprecated support to passing a class to `:class_name` on associations.
-*   For PostgreSQL >= 9.4 use `pgcrypto`'s `gen_random_uuid()` instead of
-    `uuid-ossp`'s UUID generation function.
+    *Rafael Mendonça França*
-    *Yuji Yaginuma*, *Yaw Boakye*
+*   Remove deprecated argument `default` from `index_name_exists?`.
-*   Introduce `Model#reload_<association>` to bring back the behavior
-    of `Article.category(true)` where `category` is a singular
-    association.
+    *Rafael Mendonça França*
-    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.
+*   Remove deprecated support to `quoted_id` when typecasting an Active Record object.
-    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.
+    *Rafael Mendonça França*
-    *Yves Senn*
+*   Fix `bin/rails db:setup` and `bin/rails db:test:prepare` create wrong
+    ar_internal_metadata's data for a test database.
-*   Make sure eager loading `ActiveRecord::Associations` also loads
-    constants defined in `ActiveRecord::Associations::Preloader`.
+    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
+    ```
-    *Yves Senn*
+    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
+    ```
-*   Allow `ActionController::Parameters`-like objects to be passed as
-    values for Postgres HStore columns.
+    Fixes #26731.
-    Fixes #26904.
+    *bogdanvlviv*
-    *Jon Moss*
+*   Fix longer sequence name detection for serial columns.
-*   Added `stat` method to `ActiveRecord::ConnectionAdapters::ConnectionPool`.
+    Fixes #28332.
-    Example:
+    *Ryuta Kamizono*
+*   MySQL: Don't lose `auto_increment: true` in the `db/schema.rb`.
-        ActiveRecord::Base.connection_pool.stat # =>
-        { size: 15, connections: 1, busy: 1, dead: 0, idle: 0, waiting: 0, checkout_timeout: 5 }
+    Fixes #30894.
-    *Pavel Evstigneev*
+    *Ryuta Kamizono*
-*   Avoid `unscope(:order)` when `limit_value` is presented for `count`
-    and `exists?`.
+*   Fix `COUNT(DISTINCT ...)` for `GROUP BY` with `ORDER BY` and `LIMIT`.
-    If `limit_value` is presented, records fetching order is very important
-    for performance. We should not unscope the order in the case.
+    Fixes #30886.
     *Ryuta Kamizono*
-*   Fix an Active Record `DateTime` field `NoMethodError` caused by incomplete
-    datetime.
+*   PostgreSQL `tsrange` now preserves subsecond precision.
-    Fixes #24195.
+    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:
-    *Sen Zhang*
+    Before:
+        connection.type_cast(tsrange.serialize(range_value))
+        # => "[2010-01-01 13:30:00 UTC,2011-02-02 19:30:00 UTC)"
-*   Allow `slice` to take an array of methods(without the need for splatting).
+    Now:
-    *Cohen Carlisle*
+        connection.type_cast(tsrange.serialize(range_value))
+        # => "[2010-01-01 13:30:00.670277,2011-02-02 19:30:00.745125)"
-*   Improved partial writes with HABTM and has many through associations
-    to fire database query only if relation has been changed.
+    *Thomas Cannon*
-    Fixes #19663.
+*   Passing a `Set` to `Relation#where` now behaves the same as passing an
+    array.
+    *Sean Griffin*
+*   Use given algorithm while removing index from database.
+    Fixes #24190.
     *Mehmet Emin İNAÇ*
-*   Deprecate passing arguments and block at the same time to
-    `ActiveRecord::QueryMethods#select`.
+*   Update payload names for `sql.active_record` instrumentation to be
+    more descriptive.
-    *Prathamesh Sonpatki*
+    Fixes #30586.
-*   Fixed: Optimistic locking does not work well with `null` in the database.
+    *Jeremy Green*
-    Fixes #26024.
+*   Add new error class `LockWaitTimeout` which will be raised
+    when lock wait timeout exceeded.
-    *bogdanvlviv*
+    *Gabriel Courtemanche*
-*   Fixed support for case insensitive comparisons of `text` columns in
-    PostgreSQL.
+*   Remove deprecated `#migration_keys`.
-    *Edho Arief*
+    *Ryuta Kamizono*
-*   Serialize JSON attribute value `nil` as SQL `NULL`, not JSON `null`.
+*   Automatically guess the inverse associations for STI.
-    *Trung Duc Tran*
+    *Yuichiro Kaneko*
-*   Return `true` from `update_attribute` when the value of the attribute
-    to be updated is unchanged.
+*   Ensure `sum` honors `distinct` on `has_many :through` associations.
-    Fixes #26593.
+    Fixes #16791.
-    *Prathamesh Sonpatki*
+    *Aaron Wortham*
-*   Always store errors details information with symbols.
+*   Add `binary` fixture helper method.
-    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.
+    *Atsushi Yoshida*
-    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.
+*   When using `Relation#or`, extract the common conditions and put them before the OR condition.
-    Fix #26499.
+    *Maxime Handfield Lapointe*
-    *Rafael Mendonça França*, *Marcus Vieira*
+*   `Relation#or` now accepts two relations who have different values for
+    `references` only, as `references` can be implicitly called by `where`.
-*   Calling `touch` on a model using optimistic locking will now leave the model
-    in a non-dirty state with no attribute changes.
+    Fixes #29411.
-    Fixes #26496.
+    *Sean Griffin*
-    *Jakob Skjerning*
+*   `ApplicationRecord` is no longer generated when generating models. If you
+    need to generate it, it can be created with `rails g application_record`.
-*   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.
+    *Lisa Ugray*
-    *Dylan Thacker-Smith*
+*   Fix `COUNT(DISTINCT ...)` with `ORDER BY` and `LIMIT` to keep the existing select list.
-*   PostgreSQL array columns will now respect the encoding of strings contained
-    in the array.
+    *Ryuta Kamizono*
-    Fixes #26326.
+*   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.
-    *Sean Griffin*
+    *Lisa Ugray*
+*   Fix `unscoped(where: [columns])` removing the wrong bind values.
+    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)
+    ```
+    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.
+*   Fix transactions to apply state to child transactions.
-    *Maxime Handfield Lapointe*
-*   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.