activerecord 3.2.22.5 → 4.0.0.beta1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b2a1b133cbd413ee58ccc671828333632ed6db3b
-  data.tar.gz: 8f7eed84647eebadf1270dc241dca3063b4586f5
+  metadata.gz: 8b06fdbc87492769dd5d79108a95f66047b330b0
+  data.tar.gz: 2695993c7be8d8a4d56f88eb0ba19fc844e86b54
 SHA512:
-  metadata.gz: 0bef1cca318f136e3c84fda17c030b840b6d889a836dee9753b000bde1fa951b90873145d6a79f7f42d76db8ae6fa66e79244baea47f5e440f8dafa1ecd6325e
-  data.tar.gz: 98f44f3efcaa299b5044a14851dc577b63c6281d4f18c152ce2fd4de1562170e8fa6aac3109eb101fdc1b5df05f5cb06efc1b8ea6ab7e69e080ebbac137a74fd
+  metadata.gz: f0c5bbb50b6b28e0208a50bea7f4268f3d9bc1de8353c2ddb5219675324fb2dbd9fe6ff2e0f662d161cd06f6532a87a51a7a1a70bdbad52bc03af438fa79cfa6
+  data.tar.gz: 32eecd85c4382a9b6e64b9c6b26354bc9fbffd974d65681e74f709d789dcf0474bb4bda94f52a1c4d538e2af17c70db2667126e36ceeb6f4c87e56e57a1195a6

data/CHANGELOG.md

@@ -1,260 +1,227 @@
-* Support Ruby 2.3 by not unexpectedly calling `.to_proc` on Hash objects
+## Rails 4.0.0.beta1 (February 25, 2013) ##
 
-    Fixes #25010
+*   Fix overriding of attributes by default_scope on `ActiveRecord::Base#dup`.
 
-    *tlrdstd*
-
-## Rails 3.2.22 (Jun 16, 2015) ##
-
-* No changes.
-
-
-## Rails 3.2.19 (Jul 2, 2014) ##
-
-*   Fix SQL Injection Vulnerability in 'bitstring' quoting.
-
-    Fixes CVE-2014-3482.
-
-    *Rafael Mendonça França*
-
-
-## Rails 3.2.18 (May 6, 2014) ##
-
-* No changes.
-
-
-## Rails 3.2.17 (Feb 18, 2014) ##
-
-* No changes.
-
-
-## Rails 3.2.16 (Dec 3, 2013) ##
-
-* No changes.
-
-
-## Rails 3.2.15 (Oct 16, 2013) ##
-
-*   When calling the method .find_or_initialize_by_* from a collection_proxy
-    it should set the inverse_of relation even when the entry was found on the db.
-
-    *arthurnn*
-
-*   Callbacks on has_many should access the in memory parent if a inverse_of is set.
-
-    *arthurnn*
-
-*   Fix `FinderMethods#last` unscoped primary key.
-
-    Fixes #11917.
-
-    *Eugene Kalenkovich*
-
-*   Load fixtures from linked folders.
-
-    *Kassio Borges*
-
-*   When using optimistic locking, `update` was not passing the column to `quote_value`
-    to allow the connection adapter to properly determine how to quote the value. This was
-    affecting certain databases that use specific colmn types.
+    *Hiroshige UMINO*
 
-    Fixes: #6763
+*   Fixing issue #8345. Now throwing an error when one attempts to touch a
+    new object that has not yet been persisted. For instance:
 
-    *Alfred Wong*
+    Example:
 
+        ball = Ball.new
+        ball.touch :updated_at   # => raises error
 
-## Rails 3.2.14 (Jul 22, 2013) ##
+    It is not until the ball object has been persisted that it can be touched.
+    This follows the behavior of update_column.
 
-*   Fix merge error when Equality LHS is non-attribute.
-    Backport of #7380.
+    *John Wang*
 
-    *Karmes Alexander*
+*   Preloading ordered `has_many :through` associations no longer applies
+    invalid ordering to the `:through` association.
+    Fixes #8663.
 
-*   Do not re-create destroyed association when saving the parent object.
+    *Yves Senn*
 
-    Fixes #11450.
+*   The auto explain feature has been removed. This feature was
+    activated by configuring `config.active_record.auto_explain_threshold_in_seconds`.
+    The configuration option was deprecated and has no more effect.
 
-    *Paul Nikitochkin*
+    You can still use `ActiveRecord::Relation#explain` to see the EXPLAIN output for
+    any given relation.
 
-*   Do not shallow the original exception in `exec_cache` on PostgreSQL adapter.
+    *Yves Senn*
 
-    Fixes #11260.
+*   The `:on` option for `after_commit` and `after_rollback` now
+    accepts an Array of actions.
+    Fixes #988.
 
-    *Rafael Mendonça França*
+    Example:
 
-*   Fix `ActiveRecord::Store` incorrectly tracking changes of its attributes.
-    Fixes #10373.
+        after_commit :update_cache on: [:create, :update]
 
-    *Janko Marohnić*
+    *Yves Senn*
 
-*   Fix a bug that prevented the use of the default STI inheritance column
-    (ActiveRecord::Base.inheritance_column = 'some_column'.)
+*   Rename related indexes on `rename_table` and `rename_column`. This
+    does not affect indexes with custom names.
 
-    *chapmajs + Takehiro Adachi*
+    *Yves Senn*
 
-*   Fix mysql2 adapter raises the correct exception when executing a query on a
-    closed connection.
+*   Prevent the creation of indices with too long names, which cause
+    internal operations to fail (sqlite3 adapter only). The method
+    `allowed_index_name_length` defines the length limit enforced by
+    rails. It's value defaults to `index_name_length` but can vary per adapter.
+    Fixes #8264.
 
     *Yves Senn*
 
-*   Fixes bug where `Company.new.contract_ids` would incorrectly load
-    all non-associated contracts.
+*   Fixing issue #776.
 
-    Example:
+    Memory bloat in transactions is handled by having the transaction hold only
+    the AR objects which it absolutely needs to know about. These are the AR
+    objects with callbacks (they need to be updated as soon as something in the
+    transaction occurs).
 
-        company = Company.new # Company has many :contracts
+    All other AR objects can be updated lazily by keeping a reference to a
+    TransactionState object. If an AR object gets inside a transaction, then
+    the transaction will add its TransactionState to the AR object. When the
+    user makes a call to some attribute on an AR object (which has no
+    callbacks) associated with a transaction, the AR object will call the
+    sync_with_transaction_state method and make sure it is up to date with the
+    transaction. After it has synced with the transaction state, the AR object
+    will return the attribute that was requested.
 
-        # before
-        company.contract_ids # => SELECT ... WHERE `contracts`.`company_id` IS NULL
+    Most of the logic in the changes are used to handle multiple transactions,
+    in which case the AR object has to recursively follow parent pointers of
+    TransactionState objects.
 
-        # after
-        company.contract_ids # => []
+    *John Wang*
 
-    *Jared Armstrong*
-
-*   Fix the `:primary_key` option for `has_many` associations.
-    Fixes #10693.
+*   Descriptive error message when the necessary AR adapter gem was not found.
+    Fixes #7313.
 
     *Yves Senn*
 
-*   fixes bug introduced by #3329.  Now, when autosaving associations,
-    deletions happen before inserts and saves.  This prevents a 'duplicate
-    unique value' database error that would occur if a record being created had
-    the same value on a unique indexed field as that of a record being destroyed.
-
-    Backport of #10417
-
-    *Johnny Holton*
+*   Active Record now raises an error when blank arguments are passed to query
+    methods for which blank arguments do not make sense.
 
-*   Fix that under some conditions, Active Record could produce invalid SQL of the sort:
-    "SELECT DISTINCT DISTINCT".
-
-    Backport of #6792.
-
-    *Ben Woosley*
+    Example:
 
-*   Require `ActiveRecord::Base` in railtie hooks for rake_tasks, console and runner to
-    avoid circular constant loading issues.
+        Post.includes()     # => raises error
 
-    Backport #7695.
+    *John Wang*
 
-    Fixes #7683 and #882
+*   Simplified type casting code for timezone aware attributes to use the
+    `in_time_zone` method if it is available. This introduces a subtle change
+    of behavior when using `Date` instances as they are directly converted to
+    `ActiveSupport::TimeWithZone` instances without first being converted to
+    `Time` instances. For example:
 
-    *Ben Holley*
+        # Rails 3.2 behavior
+        >> Date.today.to_time.in_time_zone
+        => Wed, 13 Feb 2013 07:00:00 UTC +00:00
 
-*   Maintain context for joins within ActiveRecord::Relation merges.
-    Backport #10164.
+        # Rails 4.0 behavior
+        >> Date.today.in_time_zone
+        => Wed, 13 Feb 2013 00:00:00 UTC +00:00
 
-    *Neeraj Singh + Andrew Horner*
+    On the plus side it now behaves the same whether you pass a `String` date
+    or an actual `Date` instance. For example:
 
-*   Make sure the `EXPLAIN` command is never triggered by a `select_db` call.
+        # Rails 3.2 behavior
+        >> Date.civil(2013, 2, 13).to_time.in_time_zone
+        => Wed, 13 Feb 2013 07:00:00 UTC +00:00
+        >> Time.zone.parse("2013-02-13")
+        => Wed, 13 Feb 2013 00:00:00 UTC +00:00
 
-    *Daniel Schierbeck*
+        # Rails 4.0 behavior
+        >> Date.civil(2013, 2, 13).in_time_zone
+        => Wed, 13 Feb 2013 00:00:00 UTC +00:00
+        >> "2013-02-13".in_time_zone
+        => Wed, 13 Feb 2013 00:00:00 UTC +00:00
 
-*   Revert changes on `pluck` that was ignoring the select clause when the relation already
-    has one. This caused a regression since it changed the behavior in a stable release.
+    If you need the old behavior you can convert the dates to times manually.
+    For example:
 
-    Fixes #9777.
+        >> Post.new(created_at: Date.today).created_at
+        => Wed, 13 Feb 2013 00:00:00 UTC +00:00
 
-    *Rafael Mendonça França*
+        >> Post.new(created_at: Date.today.to_time).created_at
+        => Wed, 13 Feb 2013 07:00:00 UTC +00:00
 
-*   Confirm a record has not already been destroyed before decrementing counter cache.
+    *Andrew White*
 
-    *Ben Tucker*
+*   Preloading `has_many :through` associations with conditions won't
+    cache the `:through` association. This will prevent invalid
+    subsets to be cached.
+    Fixes #8423.
 
-*   Default values for PostgreSQL bigint types now get parsed and dumped to the
-    schema correctly.
-    Backport #10098.
+    Example:
 
-    *Erik Peterson*
+        class User
+          has_many :posts
+          has_many :recent_comments, -> { where('created_at > ?', 1.week.ago) }, :through => :posts
+        end
 
-*   Removed warning when `auto_explain_threshold_in_seconds` is set and the
-    connection adapter doesn't support explain.
-    This is causing a regression since the Active Record Railtie is trying to
-    connect to the development database in the application boot.
+        a_user = User.includes(:recent_comments).first
 
-    *Rafael Mendonça França*
+        # This is preloaded.
+        a_user.recent_comments
 
-*   Do not reset `inheritance_column` when it's set explicitly.
-    Backport of #5327.
+        # This is not preloaded, fetched now.
+        a_user.posts
 
-    *kennyj + Fred Wu*
+    *Yves Senn*
 
-*   Fix a problem wrong exception is occured
-    when raising no translatable exception in PostgreSQL.
+*   Don't run `after_commit` callbacks when creating through an association
+    if saving the record fails.
 
-    *kennyj*
+    *James Miller*
 
-*   Resets the postgres search path in the structure.sql after the structure
-    is dumped in order to find schema_migrations table when multiples schemas
-    are used.
-    Fixes #9796.
+*   Allow store accessors to be overrided like other attribute methods, e.g.:
 
-    *Juan M. Cuello + Dembskiy Alexander*
+        class User < ActiveRecord::Base
+          store :settings, accessors: [ :color, :homepage ], coder: JSON
 
-*   Reload the association target if it's stale. `@stale_state` should be nil
-    when a model isn't saved.
-    Fixes #7526.
+          def color
+            super || 'red'
+          end
+        end
 
-    *Larry Lv*
+    *Sergey Nartimov*
 
-*   Don't read CSV files during execution of `db:fixtures:load`. CSV support for
-    fixtures was removed some time ago but the task was still loading them, even
-    though later the code was looking for the related yaml file instead.
+*   Quote numeric values being compared to non-numeric columns. Otherwise,
+    in some database, the string column values will be coerced to a numeric
+    allowing 0, 0.0 or false to match any string starting with a non-digit.
 
-    *kennyj*
+    Example:
 
+        App.where(apikey: 0) # => SELECT * FROM users WHERE apikey = '0'
 
-## Rails 3.2.13 (Mar 18, 2013) ##
+    *Dylan Smith*
 
-*   Chaining multiple preloaded scopes will correctly preload all the scopes
-    at the same time.
+*   Schema dumper supports dumping the enabled database extensions to `schema.rb`
+    (currently only supported by postgresql).
 
-    *Chris Geihsler*
+    *Justin George*
 
-*   Reverted 921a296a3390192a71abeec6d9a035cc6d1865c8, 'Quote numeric values
-    compared to string columns.' This caused several regressions.
+*   The database adpters now converts the options passed thought `DATABASE_URL`
+    environment variable to the proper Ruby types before using. For example, SQLite requires
+    that the timeout value is an integer, and PostgreSQL requires that the
+    prepared_statements option is a boolean. These now work as expected:
 
-    *Steve Klabnik*
+    Example:
 
-*   Fix overriding of attributes by `default_scope` on `ActiveRecord::Base#dup`.
+        DATABASE_URL=sqlite3://localhost/test_db?timeout=500
+        DATABASE_URL=postgresql://localhost/test_db?prepared_statements=false
 
-    *Hiroshige UMINO*
+    *Aaron Stone + Rafael Mendonça França*
 
-*   Fix issue with overriding Active Record reader methods with a composed object
-    and using that attribute as the scope of a `uniqueness_of` validation.
-    Backport #7072.
+*   `Relation#merge` now only overwrites where values on the LHS of the
+    merge. Consider:
 
-    *Peter Brown*
+        left  = Person.where(age: [13, 14, 15])
+        right = Person.where(age: [13, 14]).where(age: [14, 15])
 
-*   Sqlite now preserves custom primary keys when copying or altering tables.
-    Fixes #9367.
-    Backport #2312.
+    `left` results in the following SQL:
 
-    *Sean Scally + Yves Senn*
+        WHERE age IN (13, 14, 15)
 
-*   Preloading `has_many :through` associations with conditions won't
-    cache the `:through` association. This will prevent invalid
-    subsets to be cached.
-    Fixes #8423.
-    Backport #9252.
+    `right` results in the following SQL:
 
-    Example:
+        WHERE age IN (13, 14) AND age IN (14, 15)
 
-        class User
-          has_many :posts
-          has_many :recent_comments, -> { where('created_at > ?', 1.week.ago) }, :through => :posts
-        end
+    Previously, `left.merge(right)` would result in all but the last
+    condition being removed:
 
-        a_user = User.includes(:recent_comments).first
+        WHERE age IN (14, 15)
 
-        # this is preloaded
-        a_user.recent_comments
+    Now it results in the LHS condition(s) for `age` being removed, but
+    the RHS remains as it is:
 
-        # fetching the recent_comments through the posts association won't preload it.
-        a_user.posts
+        WHERE age IN (13, 14) AND age IN (14, 15)
 
-    *Yves Senn*
+    *Jon Leighton*
 
 *   Fix handling of dirty time zone aware attributes
 
@@ -282,54 +249,55 @@
           order.changed? # => false, used to return true
         end
 
-    Backport of #9073
-    Fixes #8898
-
     *Lilibeth De La Cruz*
 
-*   Fix counter cache columns not updated when replacing `has_many :through`
-    associations.
-    Backport #8400.
-    Fix #7630.
+*   When `#count` is used in conjunction with `#uniq` we perform `count(:distinct => true)`.
+    Fixes #6865.
 
-    *Matthew Robertson*
+    Example:
 
-*   Don't update `column_defaults` when calling destructive methods on column with default value.
-    Backport c517602.
-    Fix #6115.
+        relation.uniq.count # => SELECT COUNT(DISTINCT *)
 
-    *Piotr Sarnacki + Aleksey Magusev + Alan Daud*
+    *Yves Senn + Kaspar Schiess*
 
-*   When `#count` is used in conjunction with `#uniq` we perform `count(:distinct => true)`.
-    Fix #6865.
+*   PostgreSQL ranges type support. Includes: int4range, int8range,
+    numrange, tsrange, tstzrange, daterange
+
+    Ranges can be created with inclusive and exclusive bounds.
 
     Example:
 
-      relation.uniq.count # => SELECT COUNT(DISTINCT *)
+        create_table :Room do |t|
+          t.daterange :availability
+        end
 
-    *Yves Senn + Kaspar Schiess*
+        Room.create(availability: (Date.today..Float::INFINITY))
+        Room.first.availability # => Wed, 19 Sep 2012..Infinity
 
-*   Fix `ActiveRecord::Relation#pluck` when columns or tables are reserved words.
-    Backport #7536.
-    Fix #8968.
+    One thing to note: Range class does not support exclusive lower
+    bound.
 
-    *Ian Lesperance + Yves Senn + Kaspar Schiess*
+    *Alexander Grebennik*
 
-*   Don't run explain on slow queries for database adapters that don't support it.
-    Backport #6197.
+*   Added a state instance variable to each transaction. Will allow other objects
+    to know whether a transaction has been committed or rolled back.
 
-    *Blake Smith*
+    *John Wang*
 
-*   Revert round usec when comparing timestamp attributes in the dirty tracking.
-    Fixes #8460.
+*   Collection associations `#empty?` always respects builded records.
+    Fixes #8879.
 
-    *Andrew White*
+    Example:
 
-*   Revert creation of through association models when using `collection=[]`
-    on a `has_many :through` association from an unsaved model.
-    Fix #7661, #8269.
+        widget = Widget.new
+        widget.things.build
+        widget.things.empty? # => false
 
-    *Ernie Miller*
+    *Yves Senn*
+
+*   Support for PostgreSQL's `ltree` data type.
+
+    *Rob Worley*
 
 *   Fix undefined method `to_i` when calling `new` on a scope that uses an
     Array; Fix FloatDomainError when setting integer column to NaN.
@@ -337,6 +305,36 @@
 
     *Jason Stirk + Tristan Harward*
 
+*   Rename `update_attributes` to `update`, keep `update_attributes` as an alias for `update` method.
+    This is a soft-deprecation for `update_attributes`, although it will still work without any
+    deprecation message in 4.0 is recommended to start using `update` since `update_attributes` will be
+    deprecated and removed in future versions of Rails.
+
+    *Amparo Luna + Guillermo Iguaran*
+
+*   `after_commit` and `after_rollback` now validate the `:on` option and raise an `ArgumentError`
+    if it is not one of `:create`, `:destroy` or `:update`
+
+    *Pascal Friederich*
+
+*   Improve ways to write `change` migrations, making the old `up` & `down` methods no longer necessary.
+
+    * The methods `drop_table` and `remove_column` are now reversible, as long as the necessary information is given.
+      The method `remove_column` used to accept multiple column names; instead use `remove_columns` (which is not reversible).
+      The method `change_table` is also reversible, as long as its block doesn't call `remove`, `change` or `change_default`
+
+    * New method `reversible` makes it possible to specify code to be run when migrating up or down.
+      See the [Guide on Migration](https://github.com/rails/rails/blob/master/guides/source/migrations.md#using-the-reversible-method)
+
+    * New method `revert` will revert a whole migration or the given block.
+      If migrating down, the given migration / block is run normally.
+      See the [Guide on Migration](https://github.com/rails/rails/blob/master/guides/source/migrations.md#reverting-previous-migrations)
+
+    Attempting to revert the methods `execute`, `remove_columns` and `change_column` will now
+    raise an `IrreversibleMigration` instead of actually executing them without any output.
+
+    *Marc-André Lafortune*
+
 *   Serialized attributes can be serialized in integer columns.
     Fix #8575.
 
@@ -344,27 +342,58 @@
 
 *   Keep index names when using `alter_table` with sqlite3.
     Fix #3489.
-    Backport #8522.
 
     *Yves Senn*
 
+*   Add ability for postgresql adapter to disable user triggers in `disable_referential_integrity`.
+    Fix #5523.
+
+    *Gary S. Weaver*
+
+*   Added support for `validates_uniqueness_of` in PostgreSQL array columns.
+    Fixes #8075.
+
+    *Pedro Padron*
+
+*   Allow int4range and int8range columns to be created in PostgreSQL and properly convert to/from database.
+
+    *Alexey Vasiliev aka leopard*
+
+*   Do not log the binding values for binary columns.
+
+    *Matthew M. Boedicker*
+
+*   Fix counter cache columns not updated when replacing `has_many :through`
+    associations.
+
+    *Matthew Robertson*
+
 *   Recognize migrations placed in directories containing numbers and 'rb'.
-    Fix #8492.
-    Backport of #8500.
+    Fix #8492
 
     *Yves Senn*
 
 *   Add `ActiveRecord::Base.cache_timestamp_format` class attribute to control
-    the format of the timestamp value in the cache key.
-    This allows users to improve the precision of the cache key.
+    the format of the timestamp value in the cache key. Defaults to `:nsec`.
     Fixes #8195.
 
     *Rafael Mendonça França*
 
-*   Add `:nsec` date format. This can be used to improve the precision of cache key.
-    Please note that this format only works with Ruby 1.9, Ruby 1.8 will ignore it completely.
+*   Session variables can be set for the `mysql`, `mysql2`, and `postgresql` adapters
+    in the `variables: <hash>` parameter in `config/database.yml`. The key-value pairs of this
+    hash will be sent in a `SET key = value` query on new database connections. See also:
+    http://dev.mysql.com/doc/refman/5.0/en/set-statement.html
+    http://www.postgresql.org/docs/8.3/static/sql-set.html
+
+    *Aaron Stone*
 
-    *Jamie Gaskins*
+*   Allow `Relation#where` with no arguments to be chained with new `not` query method.
+
+    Example:
+
+        Developer.where.not(name: 'Aaron')
+
+    *Akira Matsuda*
 
 *   Unscope `update_column(s)` query to ignore default scope.
 
@@ -374,7 +403,7 @@
     to the update query.
 
         class User < ActiveRecord::Base
-          default_scope where(active: true)
+          default_scope -> { where(active: true) }
         end
 
         user = User.first
@@ -388,12 +417,16 @@
 
         user.update_column(:active, true) # => true
 
-    Backport of #8436 fix.
+    Fixes #8436.
 
     *Carlos Antonio da Silva*
 
-*   Fix performance problem with primary_key method in PostgreSQL adapter when having many schemas.
-    Uses pg_constraint table instead of pg_depend table which has many records in general.
+*   SQLite adapter no longer corrupts binary data if the data contains `%00`.
+
+    *Chris Feist*
+
+*   Fix performance problem with `primary_key` method in PostgreSQL adapter when having many schemas.
+    Uses `pg_constraint` table instead of `pg_depend` table which has many records in general.
     Fix #8414
 
     *kennyj*
@@ -401,67 +434,73 @@
 *   Do not instantiate intermediate Active Record objects when eager loading.
     These records caused `after_find` to run more than expected.
     Fix #3313
-    Backport of #8403
 
     *Yves Senn*
 
-*   Fix `pluck` to work with joins. Backport of #4942.
+*   Add STI support to init and building associations.
+    Allows you to do `BaseClass.new(type: "SubClass")` as well as
+    `parent.children.build(type: "SubClass")` or `parent.build_child`
+    to initialize an STI subclass. Ensures that the class name is a
+    valid class and that it is in the ancestors of the super class
+    that the association is expecting.
 
-    *Carlos Antonio da Silva*
+    *Jason Rush*
 
-*   Fix a problem with `translate_exception` method in a non English environment.
-    Backport of #6397.
+*   Observers was extracted from Active Record as `rails-observers` gem.
 
-    *kennyj*
+    *Rafael Mendonça França*
+
+*   Ensure that associations take a symbol argument. *Steve Klabnik*
 
-*   Fix dirty attribute checks for TimeZoneConversion with nil and blank
+*   Fix dirty attribute checks for `TimeZoneConversion` with nil and blank
     datetime attributes. Setting a nil datetime to a blank string should not
-    result in a change being flagged.
-    Fixes #8310.
-    Backport of #8311.
+    result in a change being flagged. Fix #8310
 
     *Alisdair McDiarmid*
 
-*   Prevent mass assignment to the type column of polymorphic associations when using `build`.
-    Fixes #8265.
-    Backport of #8291.
+*   Prevent mass assignment to the type column of polymorphic associations when using `build`
+    Fix #8265
 
     *Yves Senn*
 
-*   When running migrations on Postgresql, the `:limit` option for `binary` and `text` columns is
-    silently dropped.
-    Previously, these migrations caused sql exceptions, because Postgresql doesn't support limits
-    on these types.
+*   Deprecate calling `Relation#sum` with a block. To perform a calculation over
+    the array result of the relation, use `to_a.sum(&block)`.
+
+    *Carlos Antonio da Silva*
+
+*   Fix postgresql adapter to handle BC timestamps correctly
+
+        HistoryEvent.create!(name: "something", occured_at: Date.new(0) - 5.years)
+
+    *Bogdan Gusiev*
+
+*   When running migrations on Postgresql, the `:limit` option for `binary` and `text` columns is silently dropped.
+    Previously, these migrations caused sql exceptions, because Postgresql doesn't support limits on these types.
 
     *Victor Costan*
 
-*   `#pluck` can be used on a relation with `select` clause.
-    Fixes #7551.
-    Backport of #8176.
+*   Don't change STI type when calling `ActiveRecord::Base#becomes`.
+    Add `ActiveRecord::Base#becomes!` with the previous behavior.
 
-    Example:
+    See #3023 for more information.
 
-        Topic.select([:approved, :id]).order(:id).pluck(:id)
+    *Thomas Hollstegge*
 
-    *Yves Senn*
+*   `rename_index` can be used inside a `change_table` block.
 
-*   Use `nil?` instead of `blank?` to check whether dynamic finder with a bang
-    should raise RecordNotFound.
-    Fixes #7238.
+        change_table :accounts do |t|
+          t.rename_index :user_id, :account_id
+        end
 
-    *Nikita Afanasenko*
+    *Jarek Radosz*
 
-*   Fix deleting from a HABTM join table upon destroying an object of a model
-    with optimistic locking enabled.
-    Fixes #5332.
+*   `#pluck` can be used on a relation with `select` clause. Fix #7551
 
-    *Nick Rogers*
+    Example:
 
-*   Use query cache/uncache when using ENV["DATABASE_URL"].
-    Fixes #6951.
-    Backport of #8074.
+        Topic.select([:approved, :id]).order(:id).pluck(:id)
 
-    *kennyj*
+    *Yves Senn*
 
 *   Do not create useless database transaction when building `has_one` association.
 
@@ -470,114 +509,150 @@
         User.has_one :profile
         User.new.build_profile
 
-    Backport of #8154.
-
     *Bogdan Gusiev*
 
-*   `AR::Base#attributes_before_type_cast` now returns unserialized values for serialized attributes.
+*   `:counter_cache` option for `has_many` associations to support custom named counter caches.
+    Fix #7993
 
-    *Nikita Afanasenko*
+    *Yves Senn*
 
-*   Fix issue that raises `NameError` when overriding the `accepts_nested_attributes` in child classes.
+*   Deprecate the possibility to pass a string as third argument of `add_index`.
+    Pass `unique: true` instead.
 
-    Before:
+        add_index(:users, :organization_id, unique: true)
 
-        class Shared::Person < ActiveRecord::Base
-          has_one :address
+    *Rafael Mendonça França*
 
-          accepts_nested_attributes :address, :reject_if => :all_blank
-        end
+*   Raise an `ArgumentError` when passing an invalid option to `add_index`.
 
-        class Person < Shared::Person
-          accepts_nested_attributes :address
-        end
+    *Rafael Mendonça França*
 
-        Person
-        #=> NameError: method `address_attributes=' not defined in Person
+*   Fix `find_in_batches` crashing when IDs are strings and start option is not specified.
 
-    After:
+    *Alexis Bernard*
 
-        Person
-        #=> Person(id: integer, ...)
+*   `AR::Base#attributes_before_type_cast` now returns unserialized values for serialized attributes.
 
-    Fixes #8131.
+    *Nikita Afanasenko*
 
-    *Gabriel Sobrinho, Ricardo Henrique*
+*   Use query cache/uncache when using `DATABASE_URL`.
+    Fix #6951.
 
+    *kennyj*
 
-## Rails 3.2.12 (Feb 11, 2013) ##
+*   Fix bug where `update_columns` and `update_column` would not let you update the primary key column.
 
-*   Quote numeric values being compared to non-numeric columns. Otherwise,
-    in some database, the string column values will be coerced to a numeric
-    allowing 0, 0.0 or false to match any string starting with a non-digit.
+    *Henrik Nyh*
 
-    Example:
+*   The `create_table` method raises an `ArgumentError` when the primary key column is redefined.
+    Fix #6378
 
-        App.where(apikey: 0) # => SELECT * FROM users WHERE apikey = '0'
+    *Yves Senn*
 
-    *Dylan Smith*
+*   `ActiveRecord::AttributeMethods#[]` raises `ActiveModel::MissingAttributeError`
+    error if the given attribute is missing. Fixes #5433.
 
+        class Person < ActiveRecord::Base
+          belongs_to :company
+        end
 
-## Rails 3.2.11 (Jan 8, 2013) ##
+        # Before:
+        person = Person.select('id').first
+        person[:name]       # => nil
+        person.name         # => ActiveModel::MissingAttributeError: missing_attribute: name
+        person[:company_id] # => nil
+        person.company      # => nil
 
-*   Fix querying with an empty hash *Damien Mathieu* [CVE-2013-0155]
+        # After:
+        person = Person.select('id').first
+        person[:name]       # => ActiveModel::MissingAttributeError: missing_attribute: name
+        person.name         # => ActiveModel::MissingAttributeError: missing_attribute: name
+        person[:company_id] # => ActiveModel::MissingAttributeError: missing_attribute: company_id
+        person.company      # => ActiveModel::MissingAttributeError: missing_attribute: company_id
 
+    *Francesco Rodriguez*
 
-## Rails 3.2.10 (Jan 2, 2013) ##
+*   Small binary fields use the `VARBINARY` MySQL type, instead of `TINYBLOB`.
 
-*   CVE-2012-5664 options hashes should only be extracted if there are extra
-    parameters
+    *Victor Costan*
 
+*   Decode URI encoded attributes on database connection URLs.
 
-## Rails 3.2.9 (Nov 12, 2012) ##
+    *Shawn Veader*
 
-*   Fix `find_in_batches` crashing when IDs are strings and start option is not specified.
+*   Add `find_or_create_by`, `find_or_create_by!` and
+    `find_or_initialize_by` methods to `Relation`.
 
-    *Alexis Bernard*
+    These are similar to the `first_or_create` family of methods, but
+    the behaviour when a record is created is slightly different:
 
-*   Fix issue with collection associations calling first(n)/last(n) and attempting
-    to set the inverse association when `:inverse_of` was used. Fixes #8087.
+        User.where(first_name: 'Penélope').first_or_create
 
-    *Carlos Antonio da Silva*
+    will execute:
 
-*   Fix bug when Column is trying to type cast boolean values to integer.
-    Fixes #8067.
+        User.where(first_name: 'Penélope').create
 
-    *Rafael Mendonça França*
+    Causing all the `create` callbacks to execute within the context of
+    the scope. This could affect queries that occur within callbacks.
 
-*   Fix bug where `rake db:test:prepare` tries to load the structure.sql into development database.
-    Fixes #8032.
+        User.find_or_create_by(first_name: 'Penélope')
 
-    *Grace Liu + Rafael Mendonça França*
+    will execute:
 
-*   Fixed support for `DATABASE_URL` environment variable for rake db tasks. *Grace Liu*
+        User.create(first_name: 'Penélope')
 
-*   Fix bug where `update_columns` and `update_column` would not let you update the primary key column.
+    Which obviously does not affect the scoping of queries within
+    callbacks.
 
-    *Henrik Nyh*
+    The `find_or_create_by` version also reads better, frankly.
 
-*   Decode URI encoded attributes on database connection URLs.
+    If you need to add extra attributes during create, you can do one of:
 
-    *Shawn Veader*
+        User.create_with(active: true).find_or_create_by(first_name: 'Jon')
+        User.find_or_create_by(first_name: 'Jon') { |u| u.active = true }
 
-*   Fix AR#dup to nullify the validation errors in the dup'ed object. Previously the original
-    and the dup'ed object shared the same errors.
+    The `first_or_create` family of methods have been nodoc'ed in favour
+    of this API. They may be deprecated in the future but their
+    implementation is very small and it's probably not worth putting users
+    through lots of annoying deprecation warnings.
 
-    *Christian Seiler*
+    *Jon Leighton*
+
+*   Fix bug with presence validation of associations. Would incorrectly add duplicated errors
+    when the association was blank. Bug introduced in 1fab518c6a75dac5773654646eb724a59741bc13.
+
+    *Scott Willson*
 
-*   Synchronize around deleting from the reserved connections hash.
-    Fixes #7955
+*   Fix bug where sum(expression) returns string '0' for no matching records.
+    Fixes #7439
 
-*   PostgreSQL adapter correctly fetches default values when using
-    multiple schemas and domains in a db. Fixes #7914
+    *Tim Macfarlane*
+
+*   PostgreSQL adapter correctly fetches default values when using multiple schemas and domains in a db. Fixes #7914
 
     *Arturo Pie*
 
-*   Fix deprecation notice when loading a collection association that
-    selects columns from other tables, if a new record was previously
-    built using that association.
+*   Learn ActiveRecord::QueryMethods#order work with hash arguments
 
-    *Ernie Miller*
+    When symbol or hash passed we convert it to Arel::Nodes::Ordering.
+    If we pass invalid direction(like name: :DeSc) ActiveRecord::QueryMethods#order will raise an exception
+
+        User.order(:name, email: :desc)
+        # SELECT "users".* FROM "users" ORDER BY "users"."name" ASC, "users"."email" DESC
+
+    *Tima Maslyuchenko*
+
+*   Rename `ActiveRecord::Fixtures` class to `ActiveRecord::FixtureSet`.
+    Instances of this class normally hold a collection of fixtures (records)
+    loaded either from a single YAML file, or from a file and a folder
+    with the same name.  This change make the class name singular and makes
+    the class easier to distinguish from the modules like
+    `ActiveRecord::TestFixtures`, which operates on multiple fixture sets,
+    or `DelegatingFixtures`, `::Fixtures`, etc.,
+    and from the class `ActiveRecord::Fixture`, which corresponds to a single
+    fixture.
+
+    *Alexey Muranov*
 
 *   The postgres adapter now supports tables with capital letters.
     Fix #5920
@@ -606,15 +681,90 @@
 
     *lulalala*
 
-*   ConnectionPool recognizes checkout_timeout spec key as taking
-    precedence over legacy wait_timeout spec key, can be used to avoid
-    conflict with mysql2 use of wait_timeout.  Closes #7684.
+*   Support for partial inserts.
+
+    When inserting new records, only the fields which have been changed
+    from the defaults will actually be included in the INSERT statement.
+    The other fields will be populated by the database.
+
+    This is more efficient, and also means that it will be safe to
+    remove database columns without getting subsequent errors in running
+    app processes (so long as the code in those processes doesn't
+    contain any references to the removed column).
+
+    The `partial_updates` configuration option is now renamed to
+    `partial_writes` to reflect the fact that it now impacts both inserts
+    and updates.
+
+    *Jon Leighton*
+
+*   Allow before and after validations to take an array of lifecycle events
+
+    *John Foley*
+
+*   Support for specifying transaction isolation level
+
+    If your database supports setting the isolation level for a transaction, you can set
+    it like so:
+
+        Post.transaction(isolation: :serializable) do
+          # ...
+        end
+
+    Valid isolation levels are:
+
+    * `:read_uncommitted`
+    * `:read_committed`
+    * `:repeatable_read`
+    * `:serializable`
+
+    You should consult the documentation for your database to understand the
+    semantics of these different levels:
+
+    * http://www.postgresql.org/docs/9.1/static/transaction-iso.html
+    * https://dev.mysql.com/doc/refman/5.0/en/set-transaction.html
+
+    An `ActiveRecord::TransactionIsolationError` will be raised if:
+
+    * The adapter does not support setting the isolation level
+    * You are joining an existing open transaction
+    * You are creating a nested (savepoint) transaction
+
+    The mysql, mysql2 and postgresql adapters support setting the transaction
+    isolation level. However, support is disabled for mysql versions below 5,
+    because they are affected by a bug (http://bugs.mysql.com/bug.php?id=39170)
+    which means the isolation level gets persisted outside the transaction.
+
+    *Jon Leighton*
+
+*   `ActiveModel::ForbiddenAttributesProtection` is included by default
+    in Active Record models. Check the docs of `ActiveModel::ForbiddenAttributesProtection`
+    for more details.
+
+    *Guillermo Iguaran*
+
+*   Remove integration between Active Record and
+    `ActiveModel::MassAssignmentSecurity`, `protected_attributes` gem
+    should be added to use `attr_accessible`/`attr_protected`. Mass
+    assignment options has been removed from all the AR methods that
+    used it (ex. `AR::Base.new`, `AR::Base.create`, `AR::Base#update_attributes`, etc).
 
-    *jrochkind*
+    *Guillermo Iguaran*
 
-*   Rename field_changed? to _field_changed? so that users can create a field named field
+*   Fix the return of querying with an empty hash.
+    Fix #6971.
+
+        User.where(token: {})
+
+    Before:
 
-    *Akira Matsuda*, backported by *Steve Klabnik*
+        #=> SELECT * FROM users;
+
+    After:
+
+        #=> SELECT * FROM users WHERE 1=0;
+
+    *Damien Mathieu*
 
 *   Fix creation of through association models when using `collection=[]`
     on a `has_many :through` association from an unsaved model.
@@ -623,115 +773,250 @@
     *Ernie Miller*
 
 *   Explain only normal CRUD sql (select / update / insert / delete).
-    Fix problem that explains unexplainable sql. Closes #7544 #6458.
+    Fix problem that explains unexplainable sql.
+    Closes #7544 #6458.
 
     *kennyj*
 
-*   Backport test coverage to ensure that PostgreSQL auto-reconnect functionality
-    remains healthy.
+*   You can now override the generated accessor methods for stored attributes
+    and reuse the original behavior with `read_store_attribute` and `write_store_attribute`,
+    which are counterparts to `read_attribute` and `write_attribute`.
+
+    *Matt Jones*
+
+*   Accept `belongs_to` (including polymorphic) association keys in queries.
 
-    *Steve Jorgensen*
+    The following queries are now equivalent:
 
-*   Use config['encoding'] instead of config['charset'] when executing
-    databases.rake in the mysql/mysql2. A correct option for a database.yml
-    is 'encoding'.
+        Post.where(author: author)
+        Post.where(author_id: author)
+
+        PriceEstimate.where(estimate_of: treasure)
+        PriceEstimate.where(estimate_of_type: 'Treasure', estimate_of_id: treasure)
+
+    *Peter Brown*
+
+*   Use native `mysqldump` command instead of `structure_dump` method
+    when dumping the database structure to a sql file. Fixes #5547.
 
     *kennyj*
 
-*   Fix ConnectionAdapters::Column.type_cast_code integer conversion,
-    to always convert values to integer calling #to_i. Fixes #7509.
+*   PostgreSQL inet and cidr types are converted to `IPAddr` objects.
 
-    *Thiago Pradi*
+    *Dan McClain*
 
-*   Fix time column type casting for invalid time string values to correctly return nil.
+*   PostgreSQL array type support. Any datatype can be used to create an
+    array column, with full migration and schema dumper support.
 
-    *Adam Meehan*
+    To declare an array column, use the following syntax:
+
+        create_table :table_with_arrays do |t|
+          t.integer :int_array, array: true
+          # integer[]
+          t.integer :int_array, array: true, length: 2
+          # smallint[]
+          t.string :string_array, array: true, length: 30
+          # char varying(30)[]
+        end
+
+    This respects any other migration detail (limits, defaults, etc).
+    Active Record will serialize and deserialize the array columns on
+    their way to and from the database.
+
+    One thing to note: PostgreSQL does not enforce any limits on the
+    number of elements, and any array can be multi-dimensional. Any
+    array that is multi-dimensional must be rectangular (each sub array
+    must have the same number of elements as its siblings).
+
+    If the `pg_array_parser` gem is available, it will be used when
+    parsing PostgreSQL's array representation.
+
+    *Dan McClain*
+
+*   Attribute predicate methods, such as `article.title?`, will now raise
+    `ActiveModel::MissingAttributeError` if the attribute being queried for
+    truthiness was not read from the database, instead of just returning `false`.
 
-*   Fix `becomes` when using a configured `inheritance_column`.
+    *Ernie Miller*
+
+*   `ActiveRecord::SchemaDumper` uses Ruby 1.9 style hash, which means that the
+    schema.rb file will be generated using this new syntax from now on.
+
+    *Konstantin Shabanov*
+
+*   Map interval with precision to string datatype in PostgreSQL. Fixes #7518.
 
     *Yves Senn*
 
+*   Fix eagerly loading associations without primary keys. Fixes #4976.
+
+    *Kelley Reynolds*
+
+*   Rails now raise an exception when you're trying to run a migration that has an invalid
+    file name. Only lower case letters, numbers, and '_' are allowed in migration's file name.
+    Please see #7419 for more details.
+
+    *Jan Bernacki*
+
+*   Fix bug when calling `store_accessor` multiple times.
+    Fixes #7532.
+
+    *Matt Jones*
+
+*   Fix store attributes that show the changes incorrectly.
+    Fixes #7532.
+
+    *Matt Jones*
+
+*   Fix `ActiveRecord::Relation#pluck` when columns or tables are reserved words.
+
+    *Ian Lesperance*
+
+*   Allow JSON columns to be created in PostgreSQL and properly encoded/decoded.
+    to/from database.
+
+    *Dickson S. Guedes*
+
+*   Fix time column type casting for invalid time string values to correctly return `nil`.
+
+    *Adam Meehan*
+
+*   Allow to pass Symbol or Proc into `:limit` option of #accepts_nested_attributes_for.
+
+    *Mikhail Dieterle*
+
+*   ActiveRecord::SessionStore has been extracted from Active Record as `activerecord-session_store`
+    gem. Please read the `README.md` file on the gem for the usage.
+
+    *Prem Sichanugrist*
+
 *   Fix `reset_counters` when there are multiple `belongs_to` association with the
     same foreign key and one of them have a counter cache.
     Fixes #5200.
 
     *Dave Desrochers*
 
+*   `serialized_attributes` and `_attr_readonly` become class method only. Instance reader methods are deprecated.
+
+    *kennyj*
+
 *   Round usec when comparing timestamp attributes in the dirty tracking.
     Fixes #6975.
 
     *kennyj*
 
-*   Use inversed parent for first and last child of has_many association.
+*   Use inversed parent for first and last child of `has_many` association.
 
     *Ravil Bayramgalin*
 
-*   Fix Column.microseconds and Column.fast_string_to_date to avoid converting
+*   Fix `Column.microseconds` and `Column.fast_string_to_time` to avoid converting
     timestamp seconds to a float, since it occasionally results in inaccuracies
     with microsecond-precision times. Fixes #7352.
 
     *Ari Pollak*
 
-*   Fix `increment!`, `decrement!`, `toggle!` that was skipping callbacks.
-    Fixes #7306.
+*   Fix AR#dup to nullify the validation errors in the dup'ed object. Previously the original
+    and the dup'ed object shared the same errors.
 
-    *Rafael Mendonça França*
+    *Christian Seiler*
+
+*   Raise `ArgumentError` if list of attributes to change is empty in `update_all`.
+
+    *Roman Shatsov*
 
 *   Fix AR#create to return an unsaved record when AR::RecordInvalid is
     raised. Fixes #3217.
 
     *Dave Yeu*
 
-*   Remove unnecessary transaction when assigning has_one associations with a nil or equal value.
-    Fix #7191.
+*   Fixed table name prefix that is generated in engines for namespaced models.
 
-    *kennyj*
+    *Wojciech Wnętrzak*
 
-*   Allow store to work with an empty column.
-    Fix #4840.
+*   Make sure `:environment` task is executed before `db:schema:load` or `db:structure:load`.
+    Fixes #4772.
 
-    *Jeremy Walker*
+    *Seamus Abshere*
 
-*   Remove prepared statement from system query in postgresql adapter.
-    Fix #5872.
+*   Allow Relation#merge to take a proc.
 
-    *Ivan Evtuhovich*
+    This was requested by DHH to allow creating of one's own custom
+    association macros.
 
-*   Make sure `:environment` task is executed before `db:schema:load` or `db:structure:load`
-    Fixes #4772.
+    For example:
 
-    *Seamus Abshere*
+        module Commentable
+          def has_many_comments(extra)
+            has_many :comments, -> { where(:foo).merge(extra) }
+          end
+        end
+
+        class Post < ActiveRecord::Base
+          extend Commentable
+          has_many_comments -> { where(:bar) }
+        end
 
+    *Jon Leighton*
 
-## Rails 3.2.8 (Aug 9, 2012) ##
+*   Add CollectionProxy#scope.
 
-*   Do not consider the numeric attribute as changed if the old value is zero and the new value
-    is not a string.
-    Fixes #7237.
+    This can be used to get a Relation from an association.
 
-    *Rafael Mendonça França*
+    Previously we had a #scoped method, but we're deprecating that for
+    AR::Base, so it doesn't make sense to have it here.
 
-*   Removes the deprecation of `update_attribute`. *fxn*
+    This was requested by DHH, to facilitate code like this:
 
-*   Reverted the deprecation of `composed_of`. *Rafael Mendonça França*
+        Project.scope.order('created_at DESC').page(current_page).tagged_with(@tag).limit(5).scoping do
+          @topics      = @project.topics.scope
+          @todolists   = @project.todolists.scope
+          @attachments = @project.attachments.scope
+          @documents   = @project.documents.scope
+        end
 
-*   Reverted the deprecation of `*_sql` association options. They will
-    be deprecated in 4.0 instead. *Jon Leighton*
+    *Jon Leighton*
 
-*   Do not eager load AR session store. ActiveRecord::SessionStore depends on the abstract store
-    in Action Pack. Eager loading this class would break client code that eager loads Active Record
-    standalone.
-    Fixes #7160
+*   Add `Relation#load`.
 
-    *Xavier Noria*
+    This method explicitly loads the records and then returns `self`.
 
-*   Do not set RAILS_ENV to "development" when using `db:test:prepare` and related rake tasks.
-    This was causing the truncation of the development database data when using RSpec.
-    Fixes #7175.
+    Rather than deciding between "do I want an array or a relation?",
+    most people are actually asking themselves "do I want to eager load
+    or lazy load?" Therefore, this method provides a way to explicitly
+    eager-load without having to switch from a `Relation` to an array.
 
-    *Rafael Mendonça França*
+    Example:
+
+        @posts = Post.where(published: true).load
 
-## Rails 3.2.7 (Jul 26, 2012) ##
+    *Jon Leighton*
+
+*   `Relation#order`: make new order prepend old one.
+
+        User.order("name asc").order("created_at desc")
+        # SELECT * FROM users ORDER BY created_at desc, name asc
+
+    This also affects order defined in `default_scope` or any kind of associations.
+
+    *Bogdan Gusiev*
+
+*   `Model.all` now returns an `ActiveRecord::Relation`, rather than an
+    array of records. Use `Relation#to_a` if you really want an array.
+
+    In some specific cases, this may cause breakage when upgrading.
+    However in most cases the `ActiveRecord::Relation` will just act as a
+    lazy-loaded array and there will be no problems.
+
+    Note that calling `Model.all` with options (e.g.
+    `Model.all(conditions: '...')` was already deprecated, but it will
+    still return an array in order to make the transition easier.
+
+    `Model.scoped` is deprecated in favour of `Model.all`.
+
+    `Relation#all` still returns an array, but is deprecated (since it
+    would serve no purpose if we made it return a `Relation`).
+
+    *Jon Leighton*
 
 *   `:finder_sql` and `:counter_sql` options on collection associations
     are deprecated. Please transition to using scopes.
@@ -740,281 +1025,477 @@
 
 *   `:insert_sql` and `:delete_sql` options on `has_and_belongs_to_many`
     associations are deprecated. Please transition to using `has_many
-    :through`
+    :through`.
 
     *Jon Leighton*
 
-*   `composed_of` has been deprecated. You'll have to write your own accessor
-    and mutator methods if you'd like to use value objects to represent some
-    portion of your models.
+*   Added `#update_columns` method which updates the attributes from
+    the passed-in hash without calling save, hence skipping validations and
+    callbacks. `ActiveRecordError` will be raised when called on new objects
+    or when at least one of the attributes is marked as read only.
 
-    *Steve Klabnik*
+        post.attributes # => {"id"=>2, "title"=>"My title", "body"=>"My content", "author"=>"Peter"}
+        post.update_columns(title: 'New title', author: 'Sebastian') # => true
+        post.attributes # => {"id"=>2, "title"=>"New title", "body"=>"My content", "author"=>"Sebastian"}
 
-*   `update_attribute` has been deprecated. Use `update_column` if
-    you want to bypass mass-assignment protection, validations, callbacks,
-    and touching of updated_at. Otherwise please use `update_attributes`.
+    *Sebastian Martinez + Rafael Mendonça França*
 
-    *Steve Klabnik*
+*   The migration generator now creates a join table with (commented) indexes every time
+    the migration name contains the word `join_table`:
 
-## Rails 3.2.6 (Jun 12, 2012) ##
+        rails g migration create_join_table_for_artists_and_musics artist_id:index music_id
 
-*   protect against the nesting of hashes changing the
-    table context in the next call to build_from_hash. This fix
-    covers this case as well.
+    *Aleksey Magusev*
 
-    CVE-2012-2695
+*   Add `add_reference` and `remove_reference` schema statements. Aliases, `add_belongs_to`
+    and `remove_belongs_to` are acceptable. References are reversible.
 
-*   Revert earlier 'perf fix' (see 3.2.4 changelog / GH #6289). This
-    change introduced a regression (GH #6609). assoc.clear and
-    assoc.delete_all have loaded the association before doing the delete
-    since at least Rails 2.3. Doing the delete without loading the
-    records means that the `before_remove` and `after_remove` callbacks do
-    not get invoked. Therefore, this change was less a fix a more an
-    optimisation, which should only have gone into master.
+    Examples:
 
-    *Jon Leighton*
+        # Create a user_id column
+        add_reference(:products, :user)
+        # Create a supplier_id, supplier_type columns and appropriate index
+        add_reference(:products, :supplier, polymorphic: true, index: true)
+        # Remove polymorphic reference
+        remove_reference(:products, :supplier, polymorphic: true)
 
-## Rails 3.2.5 (Jun 1, 2012) ##
+    *Aleksey Magusev*
 
-*   Restore behavior of Active Record 3.2.3 scopes.
-    A series of commits relating to preloading and scopes caused a regression.
+*   Add `:default` and `:null` options to `column_exists?`.
 
-    *Andrew White*
+        column_exists?(:testings, :taggable_id, :integer, null: false)
+        column_exists?(:testings, :taggable_type, :string, default: 'Photo')
 
+    *Aleksey Magusev*
 
-## Rails 3.2.4 (May 31, 2012) ##
+*   `ActiveRecord::Relation#inspect` now makes it clear that you are
+    dealing with a `Relation` object rather than an array:.
 
-*   Perf fix: Don't load the records when doing assoc.delete_all.
-    GH #6289. *Jon Leighton*
+        User.where(age: 30).inspect
+        # => <ActiveRecord::Relation [#<User ...>, #<User ...>, ...]>
 
-*   Association preloading shouldn't be affected by the current scoping.
-    This could cause infinite recursion and potentially other problems.
-    See GH #5667. *Jon Leighton*
+        User.where(age: 30).to_a.inspect
+        # => [#<User ...>, #<User ...>]
 
-*   Datetime attributes are forced to be changed. GH #3965
+    The number of records displayed will be limited to 10.
 
-*   Fix attribute casting. GH #5549
+    *Brian Cardarella, Jon Leighton & Damien Mathieu*
 
-*   Fix #5667. Preloading should ignore scoping.
+*   Add `collation` and `ctype` support to PostgreSQL. These are available for PostgreSQL 8.4 or later.
+    Example:
 
-*   Predicate builder should not recurse for determining where columns.
-    Thanks to Ben Murphy for reporting this! CVE-2012-2661
+        development:
+          adapter: postgresql
+          host: localhost
+          database: rails_development
+          username: foo
+          password: bar
+          encoding: UTF8
+          collation: ja_JP.UTF8
+          ctype: ja_JP.UTF8
 
+    *kennyj*
 
-## Rails 3.2.3 (March 30, 2012) ##
+*   Changed `validates_presence_of` on an association so that children objects
+    do not validate as being present if they are marked for destruction. This
+    prevents you from saving the parent successfully and thus putting the parent
+    in an invalid state.
 
-*   Added find_or_create_by_{attribute}! dynamic method. *Andrew White*
+    *Nick Monje & Brent Wheeldon*
 
-*   Whitelist all attribute assignment by default. Change the default for newly generated applications to whitelist all attribute assignment.  Also update the generated model classes so users are reminded of the importance of attr_accessible. *NZKoz*
+*   `FinderMethods#exists?` now returns `false` with the `false` argument.
 
-*   Update ActiveRecord::AttributeMethods#attribute_present? to return false for empty strings. *Jacobkg*
+    *Egor Lynko*
 
-*   Fix associations when using per class databases. *larskanis*
+*   Added support for specifying the precision of a timestamp in the postgresql
+    adapter. So, instead of having to incorrectly specify the precision using the
+    `:limit` option, you may use `:precision`, as intended. For example, in a migration:
 
-*   Revert setting NOT NULL constraints in add_timestamps *fxn*
+        def change
+          create_table :foobars do |t|
+            t.timestamps precision: 0
+          end
+        end
 
-*   Fix mysql to use proper text types. Fixes #3931. *kennyj*
+    *Tony Schneider*
 
-*   Fix #5069 - Protect foreign key from mass assignment through association builder. *byroot*
+*   Allow `ActiveRecord::Relation#pluck` to accept multiple columns. Returns an
+    array of arrays containing the typecasted values:
 
+        Person.pluck(:id, :name)
+        # SELECT people.id, people.name FROM people
+        # [[1, 'David'], [2, 'Jeremy'], [3, 'Jose']]
 
-## Rails 3.2.2 (March 1, 2012) ##
+    *Jeroen van Ingen & Carlos Antonio da Silva*
 
-*   No changes.
+*   Improve the derivation of HABTM join table name to take account of nesting.
+    It now takes the table names of the two models, sorts them lexically and
+    then joins them, stripping any common prefix from the second table name.
 
+    Some examples:
 
-## Rails 3.2.1 (January 26, 2012) ##
+        Top level models (Category <=> Product)
+        Old: categories_products
+        New: categories_products
 
-*   The threshold for auto EXPLAIN is ignored if there's no logger. *fxn*
+        Top level models with a global table_name_prefix (Category <=> Product)
+        Old: site_categories_products
+        New: site_categories_products
 
-*   Call `to_s` on the value passed to `table_name=`, in particular symbols
-    are supported (regression). *Sergey Nartimov*
+        Nested models in a module without a table_name_prefix method (Admin::Category <=> Admin::Product)
+        Old: categories_products
+        New: categories_products
 
-*   Fix possible race condition when two threads try to define attribute
-    methods for the same class. *Jon Leighton*
+        Nested models in a module with a table_name_prefix method (Admin::Category <=> Admin::Product)
+        Old: categories_products
+        New: admin_categories_products
 
+        Nested models in a parent model (Catalog::Category <=> Catalog::Product)
+        Old: categories_products
+        New: catalog_categories_products
 
-## Rails 3.2.0 (January 20, 2012) ##
+        Nested models in different parent models (Catalog::Category <=> Content::Page)
+        Old: categories_pages
+        New: catalog_categories_content_pages
 
-*   Added a `with_lock` method to ActiveRecord objects, which starts
-    a transaction, locks the object (pessimistically) and yields to the block.
-    The method takes one (optional) parameter and passes it to `lock!`.
+    *Andrew White*
 
-    Before:
+*   Move HABTM validity checks to `ActiveRecord::Reflection`. One side effect of
+    this is to move when the exceptions are raised from the point of declaration
+    to when the association is built. This is consistant with other association
+    validity checks.
 
-        class Order < ActiveRecord::Base
-          def cancel!
-            transaction do
-              lock!
-              # ... cancelling logic
-            end
-          end
-        end
+    *Andrew White*
 
-    After:
+*   Added `stored_attributes` hash which contains the attributes stored using
+    `ActiveRecord::Store`. This allows you to retrieve the list of attributes
+    you've defined.
 
-        class Order < ActiveRecord::Base
-          def cancel!
-            with_lock do
-              # ... cancelling logic
-            end
-          end
-        end
+       class User < ActiveRecord::Base
+         store :settings, accessors: [:color, :homepage]
+       end
 
-    *Olek Janiszewski*
+       User.stored_attributes[:settings] # [:color, :homepage]
 
-*   'on' and 'ON' boolean columns values are type casted to true
-    *Santiago Pastorino*
+    *Joost Baaij & Carlos Antonio da Silva*
 
-*   Added ability to run migrations only for given scope, which allows
-    to run migrations only from one engine (for example to revert changes
-    from engine that you want to remove).
+*   PostgreSQL default log level is now 'warning', to bypass the noisy notice
+    messages. You can change the log level using the `min_messages` option
+    available in your config/database.yml.
 
-    Example:
-      rake db:migrate SCOPE=blog
+    *kennyj*
 
-    *Piotr Sarnacki*
+*   Add uuid datatype support to PostgreSQL adapter.
 
-*   Migrations copied from engines are now scoped with engine's name,
-    for example 01_create_posts.blog.rb. *Piotr Sarnacki*
+    *Konstantin Shabanov*
 
-*   Implements `AR::Base.silence_auto_explain`. This method allows the user to
-    selectively disable automatic EXPLAINs within a block. *fxn*
+*   Added `ActiveRecord::Migration.check_pending!` that raises an error if
+    migrations are pending.
 
-*   Implements automatic EXPLAIN logging for slow queries.
+    *Richard Schneeman*
 
-    A new configuration parameter `config.active_record.auto_explain_threshold_in_seconds`
-    determines what's to be considered a slow query. Setting that to `nil` disables
-    this feature. Defaults are 0.5 in development mode, and `nil` in test and production
-    modes.
+*   Added `#destroy!` which acts like `#destroy` but will raise an
+    `ActiveRecord::RecordNotDestroyed` exception instead of returning `false`.
 
-    As of this writing there's support for SQLite, MySQL (mysql2 adapter), and
-    PostgreSQL.
+    *Marc-André Lafortune*
 
-    *fxn*
+*   Added support to `CollectionAssociation#delete` for passing `fixnum`
+    or `string` values as record ids. This finds the records responding
+    to the `id` and executes delete on them.
 
-*   Implemented ActiveRecord::Relation#pluck method
+        class Person < ActiveRecord::Base
+          has_many :pets
+        end
 
-    Method returns Array of column value from table under ActiveRecord model
+        person.pets.delete("1") # => [#<Pet id: 1>]
+        person.pets.delete(2, 3) # => [#<Pet id: 2>, #<Pet id: 3>]
 
-        Client.pluck(:id)
+    *Francesco Rodriguez*
 
-    *Bogdan Gusiev*
+*   Deprecated most of the 'dynamic finder' methods. All dynamic methods
+    except for `find_by_...` and `find_by_...!` are deprecated. Here's
+    how you can rewrite the code:
 
-*   Automatic closure of connections in threads is deprecated.  For example
-    the following code is deprecated:
+      * `find_all_by_...` can be rewritten using `where(...)`
+      * `find_last_by_...` can be rewritten using `where(...).last`
+      * `scoped_by_...` can be rewritten using `where(...)`
+      * `find_or_initialize_by_...` can be rewritten using
+        `where(...).first_or_initialize`
+      * `find_or_create_by_...` can be rewritten using
+        `find_or_create_by(...)` or where(...).first_or_create`
+      * `find_or_create_by_...!` can be rewritten using
+        `find_or_create_by!(...) or `where(...).first_or_create!`
 
-    Thread.new { Post.find(1) }.join
+    The implementation of the deprecated dynamic finders has been moved
+    to the `activerecord-deprecated_finders` gem. See below for details.
 
-    It should be changed to close the database connection at the end of
-    the thread:
+    *Jon Leighton*
 
-    Thread.new {
-      Post.find(1)
-      Post.connection.close
-    }.join
+*   Deprecated the old-style hash based finder API. This means that
+    methods which previously accepted "finder options" no longer do. For
+    example this:
 
-    Only people who spawn threads in their application code need to worry
-    about this change.
+        Post.find(:all, conditions: { comments_count: 10 }, limit: 5)
 
-*   Deprecated:
+    Should be rewritten in the new style which has existed since Rails 3:
 
-      * `set_table_name`
-      * `set_inheritance_column`
-      * `set_sequence_name`
-      * `set_primary_key`
-      * `set_locking_column`
+        Post.where(comments_count: 10).limit(5)
 
-    Use an assignment method instead. For example, instead of `set_table_name`, use `self.table_name=`:
+    Note that as an interim step, it is possible to rewrite the above as:
 
-         class Project < ActiveRecord::Base
-           self.table_name = "project"
-         end
+        Post.all.merge(where: { comments_count: 10 }, limit: 5)
 
-    Or define your own `self.table_name` method:
+    This could save you a lot of work if there is a lot of old-style
+    finder usage in your application.
 
-         class Post < ActiveRecord::Base
-           def self.table_name
-             "special_" + super
-           end
-         end
-         Post.table_name # => "special_posts"
+    `Relation#merge` now accepts a hash of
+    options, but they must be identical to the names of the equivalent
+    finder method. These are mostly identical to the old-style finder
+    option names, except in the following cases:
+
+      * `:conditions` becomes `:where`.
+      * `:include` becomes `:includes`.
+
+    The code to implement the deprecated features has been moved out to the
+    `activerecord-deprecated_finders` gem. This gem is a dependency of Active
+    Record in Rails 4.0, so the interface works out of the box. It will no
+    longer be a dependency from Rails 4.1 (you'll need to add it to the
+    `Gemfile` in 4.1), and will be maintained until Rails 5.0.
 
     *Jon Leighton*
 
-*   Generated association methods are created within a separate module to allow overriding and
-    composition using `super`. For a class named `MyModel`, the module is named
-    `MyModel::GeneratedFeatureMethods`. It is included into the model class immediately after
-    the `generated_attributes_methods` module defined in ActiveModel, so association methods
-    override attribute methods of the same name. *Josh Susser*
+*   It's not possible anymore to destroy a model marked as read only.
 
-*   Implemented ActiveRecord::Relation#explain. *fxn*
+    *Johannes Barre*
 
-*   Add ActiveRecord::Relation#uniq for generating unique queries.
+*   Added ability to ActiveRecord::Relation#from to accept other ActiveRecord::Relation objects.
 
-    Before:
+      Record.from(subquery)
+      Record.from(subquery, :a)
 
-        Client.select('DISTINCT name')
+    *Radoslav Stankov*
 
-    After:
+*   Added custom coders support for ActiveRecord::Store. Now you can set
+    your custom coder like this:
+
+        store :settings, accessors: [ :color, :homepage ], coder: JSON
+
+    *Andrey Voronkov*
 
-        Client.select(:name).uniq
+*   `mysql` and `mysql2` connections will set `SQL_MODE=STRICT_ALL_TABLES` by
+    default to avoid silent data loss. This can be disabled by specifying
+    `strict: false` in your `database.yml`.
 
-    This also allows you to revert the unqueness in a relation:
+    *Michael Pearson*
 
-        Client.select(:name).uniq.uniq(false)
+*   Added default order to `first` to assure consistent results among
+    different database engines. Introduced `take` as a replacement to
+    the old behavior of `first`.
+
+    *Marcelo Silveira*
+
+*   Added an `:index` option to automatically create indexes for references
+    and belongs_to statements in migrations.
+
+    The `references` and `belongs_to` methods now support an `index`
+    option that receives either a boolean value or an options hash
+    that is identical to options available to the add_index method:
+
+      create_table :messages do |t|
+        t.references :person, index: true
+      end
+
+      Is the same as:
+
+      create_table :messages do |t|
+        t.references :person
+      end
+      add_index :messages, :person_id
+
+    Generators have also been updated to use the new syntax.
+
+    *Joshua Wood*
+
+*   Added `#find_by` and `#find_by!` to mirror the functionality
+    provided by dynamic finders in a way that allows dynamic input more
+    easily:
+
+        Post.find_by name: 'Spartacus', rating: 4
+        Post.find_by "published_at < ?", 2.weeks.ago
+        Post.find_by! name: 'Spartacus'
 
     *Jon Leighton*
 
-*   Support index sort order in sqlite, mysql and postgres adapters. *Vlad Jebelev*
+*   Added ActiveRecord::Base#slice to return a hash of the given methods with
+    their names as keys and returned values as values.
+
+    *Guillermo Iguaran*
+
+*   Deprecate eager-evaluated scopes.
 
-*   Allow the :class_name option for associations to take a symbol (:Client) in addition to
-    a string ('Client').
+    Don't use this:
 
-    This is to avoid confusing newbies, and to be consistent with the fact that other options
-    like :foreign_key already allow a symbol or a string.
+        scope :red, where(color: 'red')
+        default_scope where(color: 'red')
+
+    Use this:
+
+        scope :red, -> { where(color: 'red') }
+        default_scope { where(color: 'red') }
+
+    The former has numerous issues. It is a common newbie gotcha to do
+    the following:
+
+        scope :recent, where(published_at: Time.now - 2.weeks)
+
+    Or a more subtle variant:
+
+        scope :recent, -> { where(published_at: Time.now - 2.weeks) }
+        scope :recent_red, recent.where(color: 'red')
+
+    Eager scopes are also very complex to implement within Active
+    Record, and there are still bugs. For example, the following does
+    not do what you expect:
+
+        scope :remove_conditions, except(:where)
+        where(...).remove_conditions # => still has conditions
 
     *Jon Leighton*
 
-*   In development mode the db:drop task also drops the test database. For symmetry with
-    the db:create task. *Dmitriy Kiriyenko*
+*   Remove IdentityMap
 
-*   Added ActiveRecord::Base.store for declaring simple single-column key/value stores *DHH*
+    IdentityMap has never graduated to be an "enabled-by-default" feature, due
+    to some inconsistencies with associations, as described in this commit:
 
-        class User < ActiveRecord::Base
-          store :settings, accessors: [ :color, :homepage ]
-        end
+       https://github.com/rails/rails/commit/302c912bf6bcd0fa200d964ec2dc4a44abe328a6
+
+    Hence the removal from the codebase, until such issues are fixed.
+
+    *Carlos Antonio da Silva*
+
+*   Added the schema cache dump feature.
+
+    `Schema cache dump` feature was implemetend. This feature can dump/load internal state of `SchemaCache` instance
+    because we want to boot rails more quickly when we have many models.
+
+    Usage notes:
+
+      1) execute rake task.
+      RAILS_ENV=production bundle exec rake db:schema:cache:dump
+      => generate db/schema_cache.dump
+
+      2) add config.active_record.use_schema_cache_dump = true in config/production.rb. BTW, true is default.
+
+      3) boot rails.
+      RAILS_ENV=production bundle exec rails server
+      => use db/schema_cache.dump
+
+      4) If you remove clear dumped cache, execute rake task.
+      RAILS_ENV=production bundle exec rake db:schema:cache:clear
+      => remove db/schema_cache.dump
+
+    *kennyj*
+
+*   Added support for partial indices to PostgreSQL adapter.
+
+    The `add_index` method now supports a `where` option that receives a
+    string with the partial index criteria.
+
+        add_index(:accounts, :code, where: 'active')
 
-        u = User.new(color: 'black', homepage: '37signals.com')
-        u.color                          # Accessor stored attribute
-        u.settings[:country] = 'Denmark' # Any attribute, even if not specified with an accessor
+        Generates
 
+        CREATE INDEX index_accounts_on_code ON accounts(code) WHERE active
 
-*   MySQL: case-insensitive uniqueness validation avoids calling LOWER when
-    the column already uses a case-insensitive collation. Fixes #561.
+    *Marcelo Silveira*
 
-    *Joseph Palermo*
+*   Implemented ActiveRecord::Relation#none method.
 
-*   Transactional fixtures enlist all active database connections. You can test
-    models on different connections without disabling transactional fixtures.
+    The `none` method returns a chainable relation with zero records
+    (an instance of the NullRelation class).
+
+    Any subsequent condition chained to the returned relation will continue
+    generating an empty relation and will not fire any query to the database.
+
+    *Juanjo Bazán*
+
+*   Added the `ActiveRecord::NullRelation` class implementing the null
+    object pattern for the Relation class.
+
+    *Juanjo Bazán*
+
+*   Added new `dependent: :restrict_with_error` option. This will add
+    an error to the model, rather than raising an exception.
+
+    The `:restrict` option is renamed to `:restrict_with_exception` to
+    make this distinction explicit.
+
+    *Manoj Kumar & Jon Leighton*
+
+*   Added `create_join_table` migration helper to create HABTM join tables.
+
+        create_join_table :products, :categories
+        # =>
+        # create_table :categories_products, id: false do |td|
+        #   td.integer :product_id,  null: false
+        #   td.integer :category_id, null: false
+        # end
+
+    *Rafael Mendonça França*
+
+*   The primary key is always initialized in the @attributes hash to `nil` (unless
+    another value has been specified).
+
+    *Aaron Paterson*
+
+*   In previous releases, the following would generate a single query with
+    an `OUTER JOIN comments`, rather than two separate queries:
+
+        Post.includes(:comments)
+            .where("comments.name = 'foo'")
+
+    This behaviour relies on matching SQL string, which is an inherently
+    flawed idea unless we write an SQL parser, which we do not wish to
+    do.
+
+    Therefore, it is now deprecated.
+
+    To avoid deprecation warnings and for future compatibility, you must
+    explicitly state which tables you reference, when using SQL snippets:
+
+        Post.includes(:comments)
+            .where("comments.name = 'foo'")
+            .references(:comments)
+
+    Note that you do not need to explicitly specify references in the
+    following cases, as they can be automatically inferred:
+
+        Post.includes(:comments).where(comments: { name: 'foo' })
+        Post.includes(:comments).where('comments.name' => 'foo')
+        Post.includes(:comments).order('comments.name')
+
+    You do not need to worry about this unless you are doing eager
+    loading. Basically, don't worry unless you see a deprecation warning
+    or (in future releases) an SQL error due to a missing JOIN.
+
+    *Jon Leighton*
 
-    *Jeremy Kemper*
+*   Support for the `schema_info` table has been dropped. Please
+    switch to `schema_migrations`.
 
-*   Add first_or_create, first_or_create!, first_or_initialize methods to Active Record. This is a
-    better approach over the old find_or_create_by dynamic methods because it's clearer which
-    arguments are used to find the record and which are used to create it:
+    *Aaron Patterson*
 
-        User.where(:first_name => "Scarlett").first_or_create!(:last_name => "Johansson")
+*   Connections *must* be closed at the end of a thread. If not, your
+    connection pool can fill and an exception will be raised.
 
-    *Andrés Mejía*
+    *Aaron Patterson*
 
-*   Fix nested attributes bug where _destroy parameter is taken into account
-    during :reject_if => :all_blank (fixes #2937)
+*   PostgreSQL hstore records can be created.
 
-    *Aaron Christy*
+    *Aaron Patterson*
 
-*   Add ActiveSupport::Cache::NullStore for use in development and testing.
+*   PostgreSQL hstore types are automatically deserialized from the database.
 
-    *Brian Durand*
+    *Aaron Patterson*
 
-Please check [3-1-stable](https://github.com/rails/rails/blob/3-1-stable/activerecord/CHANGELOG.md) for previous changes.
+Please check [3-2-stable](https://github.com/rails/rails/blob/3-2-stable/activerecord/CHANGELOG.md) for previous changes.