activerecord 3.1.12 → 3.2.22.1

data/CHANGELOG.md

@@ -1,548 +1,1014 @@
-## unreleased ##
+## Rails 3.2.22 (Jun 16, 2015) ##
 
-*   Reverted 921a296a3390192a71abeec6d9a035cc6d1865c8, 'Quote numeric values
-    compared to string columns.' This caused several regressions.
+* No changes.
 
-    *Steve Klabnik*
 
-## Rails 3.1.11 (Feb 11, 2011) ##
+## Rails 3.2.19 (Jul 2, 2014) ##
 
-*   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.
+*   Fix SQL Injection Vulnerability in 'bitstring' quoting.
 
-    Example:
+    Fixes CVE-2014-3482.
 
-        App.where(apikey: 0) # => SELECT * FROM users WHERE apikey = '0'
+    *Rafael Mendonça França*
 
-    *Dylan Smith*
 
-## Rails 3.1.10 (Jan 8, 2013) ##
+## Rails 3.2.18 (May 6, 2014) ##
 
-*   Fix querying with an empty hash *Damien Mathieu* [CVE-2013-0155]
+* No changes.
 
-## Rails 3.1.9 (Jan 2, 2013) ##
 
-*  CVE-2012-5664 ensure that options are never taken from the first parameter
+## Rails 3.2.17 (Feb 18, 2014) ##
 
-## Rails 3.1.8 (Aug 9, 2012) ##
+* No changes.
 
-*   No changes.
 
-## Rails 3.1.7 (Jul 26, 2012) ##
+## Rails 3.2.16 (Dec 3, 2013) ##
 
-*   No changes.
+* No changes.
 
-## Rails 3.1.6 (Jun 12, 2012) ##
 
-*   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.
+## Rails 3.2.15 (Oct 16, 2013) ##
 
-    CVE-2012-2695
+*   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.
 
-## Rails 3.1.5 (May 31, 2012) ##
+    *arthurnn*
 
-*   Fix type_to_sql with text and limit on mysql/mysql2. Fix GH #3931.
+*   Callbacks on has_many should access the in memory parent if a inverse_of is set.
 
-*   only log an error if there is a logger. fixes #5226
+    *arthurnn*
 
-*   fix activerecord query_method regression with offset into Fixnum
+*   Fix `FinderMethods#last` unscoped primary key.
 
-*   predicate builder should not recurse for determining where columns.
-    Thanks to Ben Murphy for reporting this! CVE-2012-2661
+    Fixes #11917.
 
-## Rails 3.1.4 (unreleased) ##
+    *Eugene Kalenkovich*
 
-*   Fix a custom primary key regression *GH 3987*
+*   Load fixtures from linked folders.
 
-    *Jon Leighton*
+    *Kassio Borges*
 
-*   Perf fix (second try): don't load records for `has many :dependent =>
-    :delete_all` *GH 3672*
+*   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.
 
-    *Jon Leighton*
+    Fixes: #6763
 
-*   Fix accessing `proxy_association` method from an association extension
-    where the calls are chained. *GH #3890*
+    *Alfred Wong*
 
-    (E.g. `post.comments.where(bla).my_proxy_method`)
 
-    *Jon Leighton*
+## Rails 3.2.14 (Jul 22, 2013) ##
 
-*   Perf fix: MySQL primary key lookup was still slow for very large
-    tables. *GH 3678*
+*   Fix merge error when Equality LHS is non-attribute.
+    Backport of #7380.
 
-    *Kenny J*
+    *Karmes Alexander*
 
-*   Perf fix: If a table has no primary key, don't repeatedly ask the database for it.
+*   Do not re-create destroyed association when saving the parent object.
 
-    *Julius de Bruijn*
+    Fixes #11450.
 
-## Rails 3.1.3 (unreleased) ##
+    *Paul Nikitochkin*
 
-*   Perf fix: If we're deleting all records in an association, don't add a IN(..) clause
-    to the query. *GH 3672*
+*   Do not shallow the original exception in `exec_cache` on PostgreSQL adapter.
 
-    *Jon Leighton*
+    Fixes #11260.
 
-*   Fix bug with referencing other mysql databases in set_table_name. *GH 3690*
+    *Rafael Mendonça França*
 
-*   Fix performance bug with mysql databases on a server with lots of other databses. *GH 3678*
+*   Fix `ActiveRecord::Store` incorrectly tracking changes of its attributes.
+    Fixes #10373.
 
-    *Christos Zisopoulos and Kenny J*
+    *Janko Marohnić*
 
-## Rails 3.1.2 (unreleased) ##
+*   Fix a bug that prevented the use of the default STI inheritance column
+    (ActiveRecord::Base.inheritance_column = 'some_column'.)
 
-*   Fix problem with prepared statements and PostgreSQL when multiple schemas are used.
-    *GH #3232*
+    *chapmajs + Takehiro Adachi*
 
-    *Juan M. Cuello*
+*   Fix mysql2 adapter raises the correct exception when executing a query on a
+    closed connection.
 
-*   Fix bug with PostgreSQLAdapter#indexes. When the search path has multiple schemas, spaces
-    were not being stripped from the schema names after the first.
+    *Yves Senn*
 
-    *Sean Kirby*
+*   Fixes bug where `Company.new.contract_ids` would incorrectly load
+    all non-associated contracts.
 
-*   Preserve SELECT columns on the COUNT for finder_sql when possible. *GH 3503*
+    Example:
 
-    *Justin Mazzi*
+        company = Company.new # Company has many :contracts
 
-*   Reset prepared statement cache when schema changes impact statement results. *GH 3335*
+        # before
+        company.contract_ids # => SELECT ... WHERE `contracts`.`company_id` IS NULL
 
-    *Aaron Patterson*
+        # after
+        company.contract_ids # => []
 
-*   Postgres: Do not attempt to deallocate a statement if the connection is no longer active.
+    *Jared Armstrong*
 
-    *Ian Leitch*
+*   Fix the `:primary_key` option for `has_many` associations.
+    Fixes #10693.
 
-*   Prevent QueryCache leaking database connections. *GH 3243*
+    *Yves Senn*
 
-    *Mark J. Titorenko*
+*   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.
 
-*   Fix bug where building the conditions of a nested through association could potentially
-    modify the conditions of the through and/or source association. If you have experienced
-    bugs with conditions appearing in the wrong queries when using nested through associations,
-    this probably solves your problems. *GH #3271*
+    Backport of #10417
 
-    *Jon Leighton*
+    *Johnny Holton*
 
-*   If a record is removed from a has_many :through, all of the join records relating to that
-    record should also be removed from the through association's target.
+*   Fix that under some conditions, Active Record could produce invalid SQL of the sort:
+    "SELECT DISTINCT DISTINCT".
 
-    *Jon Leighton*
+    Backport of #6792.
 
-*   Fix adding multiple instances of the same record to a has_many :through. *GH #3425*
+    *Ben Woosley*
 
-    *Jon Leighton*
+*   Require `ActiveRecord::Base` in railtie hooks for rake_tasks, console and runner to
+    avoid circular constant loading issues.
 
-*   Fix creating records in a through association with a polymorphic source type. *GH #3247*
+    Backport #7695.
 
-    *Jon Leighton*
+    Fixes #7683 and #882
 
-*   MySQL: use the information_schema than the describe command when we look for a primary key. *GH #3440*
-    *Kenny J*
+    *Ben Holley*
 
-## Rails 3.1.1 (October 7, 2011) ##
+*   Maintain context for joins within ActiveRecord::Relation merges.
+    Backport #10164.
 
-*   Raise an exception if the primary key of a model in an association is needed
-    but unknown. Fixes #3207.
+    *Neeraj Singh + Andrew Horner*
 
-    *Jon Leighton*
+*   Make sure the `EXPLAIN` command is never triggered by a `select_db` call.
 
-*   Add deprecation for the preload_associations method. Fixes #3022.
+    *Daniel Schierbeck*
 
-    *Jon Leighton*
+*   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.
 
-*   Don't require a DB connection when loading a model that uses set_primary_key. GH #2807.
+    Fixes #9777.
 
-    *Jon Leighton*
+    *Rafael Mendonça França*
 
-*   Fix using select() with a habtm association, e.g. Person.friends.select(:name). GH #3030 and
-    \#2923.
+*   Confirm a record has not already been destroyed before decrementing counter cache.
 
-    *Hendy Tanata*
+    *Ben Tucker*
 
-*   Fix belongs_to polymorphic with custom primary key on target. GH #3104.
+*   Default values for PostgreSQL bigint types now get parsed and dumped to the
+    schema correctly.
+    Backport #10098.
 
-    *Jon Leighton*
+    *Erik Peterson*
 
-*   CollectionProxy#replace should change the DB records rather than just mutating the array.
-    Fixes #3020.
+*   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.
 
-    *Jon Leighton*
+    *Rafael Mendonça França*
 
-*   LRU cache in mysql and sqlite are now per-process caches.
+*   Do not reset `inheritance_column` when it's set explicitly.
+    Backport of #5327.
 
-    * lib/active_record/connection_adapters/mysql_adapter.rb: LRU cache
-  	  keys are per process id.
-    * lib/active_record/connection_adapters/sqlite_adapter.rb: ditto
+    *kennyj + Fred Wu*
 
-    *Aaron Patterson*
+*   Fix a problem wrong exception is occured
+    when raising no translatable exception in PostgreSQL.
 
-*   Database adapters use a statement pool for limiting the number of open
-    prepared statments on the database.  The limit defaults to 1000, but can
-    be adjusted in your database config by changing 'statement_limit'.
+    *kennyj*
 
-*   Fix clash between using 'preload', 'joins' or 'eager_load' in a default scope and including the
-    default scoped model in a nested through association. (GH #2834.) *Jon Leighton*
+*   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.
 
-*   Ensure we are not comparing a string with a symbol in HasManyAssociation#inverse_updates_counter_cache?.
-    Fixes GH #2755, where a counter cache could be decremented twice as far as it was supposed to be.
+    *Juan M. Cuello + Dembskiy Alexander*
 
-    *Jon Leighton*
+*   Reload the association target if it's stale. `@stale_state` should be nil
+    when a model isn't saved.
+    Fixes #7526.
 
-*   Don't send any queries to the database when the foreign key of a belongs_to is nil. Fixes
-    GH #2828. *Georg Friedrich*
+    *Larry Lv*
 
-*   Fixed find_in_batches method to not include order from default_scope. See GH #2832 *Arun Agrawal*
+*   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.
 
-*   Don't compute table name for abstract classes. Fixes problem with setting the primary key
-    in an abstract class. See GH #2791. *Akira Matsuda*
+    *kennyj*
 
-*   Psych errors with poor yaml formatting are proxied. Fixes GH #2645 and
-    GH #2731
 
-*   Use the LIMIT word with the methods #last and #first. Fixes GH #2783 *Damien Mathieu*
+## Rails 3.2.13 (Mar 18, 2013) ##
 
-## Rails 3.1.0 (August 30, 2011) ##
+*   Chaining multiple preloaded scopes will correctly preload all the scopes
+    at the same time.
 
-*   Add a proxy_association method to association proxies, which can be called by association
-    extensions to access information about the association. This replaces proxy_owner etc with
-    proxy_association.owner.
+    *Chris Geihsler*
 
-    *Jon Leighton*
+*   Reverted 921a296a3390192a71abeec6d9a035cc6d1865c8, 'Quote numeric values
+    compared to string columns.' This caused several regressions.
+
+    *Steve Klabnik*
 
-*   Active Record's dynamic finder will now show a deprecation warning if you passing in less number of arguments than what you call in method signature. This behavior will raise ArgumentError in the next version of Rails *Prem Sichanugrist*
+*   Fix overriding of attributes by `default_scope` on `ActiveRecord::Base#dup`.
 
-*   Deprecated the AssociationCollection constant. CollectionProxy is now the appropriate constant
-    to use, though be warned that this is not really a public API.
+    *Hiroshige UMINO*
 
-    This should solve upgrade problems with the will_paginate plugin (and perhaps others). Thanks
-    Paul Battley for reporting.
+*   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.
 
-    *Jon Leighton*
+    *Peter Brown*
 
-*   ActiveRecord::MacroReflection::AssociationReflection#build_record has a new method signature.
+*   Sqlite now preserves custom primary keys when copying or altering tables.
+    Fixes #9367.
+    Backport #2312.
 
-    Before: def build_association(*options)
-    After:  def build_association(*options, &block)
+    *Sean Scally + Yves Senn*
 
-    Users who are redefining this method to extend functionality should ensure that the block is
-    passed through to ActiveRecord::Base#new.
+*   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.
 
-    This change is necessary to fix https://github.com/rails/rails/issues/1842.
+    Example:
 
-    A deprecation warning and workaround has been added to 3.1, but authors will need to update
-    their code for it to work correctly in 3.2.
+        class User
+          has_many :posts
+          has_many :recent_comments, -> { where('created_at > ?', 1.week.ago) }, :through => :posts
+        end
 
-    *Jon Leighton*
+        a_user = User.includes(:recent_comments).first
 
-*   AR#pluralize_table_names can be used to singularize/pluralize table name of an individual model:
+        # this is preloaded
+        a_user.recent_comments
 
-        class User < ActiveRecord::Base
-          self.pluralize_table_names = false
+        # fetching the recent_comments through the posts association won't preload it.
+        a_user.posts
+
+    *Yves Senn*
+
+*   Fix handling of dirty time zone aware attributes
+
+    Previously, when `time_zone_aware_attributes` were enabled, after
+    changing a datetime or timestamp attribute and then changing it back
+    to the original value, `changed_attributes` still tracked the
+    attribute as changed. This caused `[attribute]_changed?` and
+    `changed?` methods to return true incorrectly.
+
+    Example:
+
+        in_time_zone 'Paris' do
+          order = Order.new
+          original_time = Time.local(2012, 10, 10)
+          order.shipped_at = original_time
+          order.save
+          order.changed? # => false
+
+          # changing value
+          order.shipped_at = Time.local(2013, 1, 1)
+          order.changed? # => true
+
+          # reverting to original value
+          order.shipped_at = original_time
+          order.changed? # => false, used to return true
         end
 
-    Previously this could only be set globally for all models through ActiveRecord::Base.pluralize_table_names. *Guillermo Iguaran*
+    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.
+
+    *Matthew Robertson*
+
+*   Don't update `column_defaults` when calling destructive methods on column with default value.
+    Backport c517602.
+    Fix #6115.
+
+    *Piotr Sarnacki + Aleksey Magusev + Alan Daud*
+
+*   When `#count` is used in conjunction with `#uniq` we perform `count(:distinct => true)`.
+    Fix #6865.
+
+    Example:
+
+      relation.uniq.count # => SELECT COUNT(DISTINCT *)
+
+    *Yves Senn + Kaspar Schiess*
+
+*   Fix `ActiveRecord::Relation#pluck` when columns or tables are reserved words.
+    Backport #7536.
+    Fix #8968.
+
+    *Ian Lesperance + Yves Senn + Kaspar Schiess*
+
+*   Don't run explain on slow queries for database adapters that don't support it.
+    Backport #6197.
+
+    *Blake Smith*
+
+*   Revert round usec when comparing timestamp attributes in the dirty tracking.
+    Fixes #8460.
+
+    *Andrew White*
+
+*   Revert creation of through association models when using `collection=[]`
+    on a `has_many :through` association from an unsaved model.
+    Fix #7661, #8269.
+
+    *Ernie Miller*
+
+*   Fix undefined method `to_i` when calling `new` on a scope that uses an
+    Array; Fix FloatDomainError when setting integer column to NaN.
+    Fixes #8718, #8734, #8757.
+
+    *Jason Stirk + Tristan Harward*
+
+*   Serialized attributes can be serialized in integer columns.
+    Fix #8575.
+
+    *Rafael Mendonça França*
 
-*   Add block setting of attributes to singular associations:
+*   Keep index names when using `alter_table` with sqlite3.
+    Fix #3489.
+    Backport #8522.
+
+    *Yves Senn*
+
+*   Recognize migrations placed in directories containing numbers and 'rb'.
+    Fix #8492.
+    Backport of #8500.
+
+    *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.
+    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.
+
+    *Jamie Gaskins*
+
+*   Unscope `update_column(s)` query to ignore default scope.
+
+    When applying `default_scope` to a class with a where clause, using
+    `update_column(s)` could generate a query that would not properly update
+    the record due to the where clause from the `default_scope` being applied
+    to the update query.
 
         class User < ActiveRecord::Base
-          has_one :account
+          default_scope where(active: true)
         end
 
-        user.build_account{ |a| a.credit_limit => 100.0 }
+        user = User.first
+        user.active = false
+        user.save!
 
-    The block is called after the instance has been initialized. *Andrew White*
+        user.update_column(:active, true) # => false
 
-*   Add ActiveRecord::Base.attribute_names to return a list of attribute names. This will return an empty array if the model is abstract or table does not exists. *Prem Sichanugrist*
+    In this situation we want to skip the default_scope clause and just
+    update the record based on the primary key. With this change:
 
-*   CSV Fixtures are deprecated and support will be removed in Rails 3.2.0
+        user.update_column(:active, true) # => true
 
-*   AR#new, AR#create, AR#create!, AR#update_attributes and AR#update_attributes! all accept a second hash as option that allows you
-    to specify which role to consider when assigning attributes. This is built on top of ActiveModel's
-    new mass assignment capabilities:
+    Backport of #8436 fix.
 
-        class Post < ActiveRecord::Base
-          attr_accessible :title
-          attr_accessible :title, :published_at, :as => :admin
-        end
+    *Carlos Antonio da Silva*
 
-        Post.new(params[:post], :as => :admin)
+*   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
 
-    assign_attributes() with similar API was also added and attributes=(params, guard) was deprecated.
+    *kennyj*
 
-    Please note that this changes the method signatures for AR#new, AR#create, AR#create!, AR#update_attributes and AR#update_attributes!. If you have overwritten these methods you should update them accordingly.
+*   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
 
-    *Josh Kalderimis*
+    *Yves Senn*
 
-*   default_scope can take a block, lambda, or any other object which responds to `call` for lazy
-    evaluation:
+*   Fix `pluck` to work with joins. Backport of #4942.
 
-        default_scope { ... }
-        default_scope lambda { ... }
-        default_scope method(:foo)
+    *Carlos Antonio da Silva*
 
-    This feature was originally implemented by Tim Morgan, but was then removed in favour of
-    defining a 'default_scope' class method, but has now been added back in by Jon Leighton.
-    The relevant lighthouse ticket is #1812.
+*   Fix a problem with `translate_exception` method in a non English environment.
+    Backport of #6397.
 
-*   Default scopes are now evaluated at the latest possible moment, to avoid problems where
-    scopes would be created which would implicitly contain the default scope, which would then
-    be impossible to get rid of via Model.unscoped.
+    *kennyj*
 
-    Note that this means that if you are inspecting the internal structure of an
-    ActiveRecord::Relation, it will *not* contain the default scope, though the resulting
-    query will do. You can get a relation containing the default scope by calling
-    ActiveRecord#with_default_scope, though this is not part of the public API.
+*   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.
 
-    *Jon Leighton*
+    *Alisdair McDiarmid*
 
-*   If you wish to merge default scopes in special ways, it is recommended to define your default
-    scope as a class method and use the standard techniques for sharing code (inheritance, mixins,
-    etc.):
+*   Prevent mass assignment to the type column of polymorphic associations when using `build`.
+    Fixes #8265.
+    Backport of #8291.
 
-        class Post < ActiveRecord::Base
-          def self.default_scope
-            where(:published => true).where(:hidden => false)
-          end
+    *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.
+
+    *Victor Costan*
+
+*   `#pluck` can be used on a relation with `select` clause.
+    Fixes #7551.
+    Backport of #8176.
+
+    Example:
+
+        Topic.select([:approved, :id]).order(:id).pluck(:id)
+
+    *Yves Senn*
+
+*   Use `nil?` instead of `blank?` to check whether dynamic finder with a bang
+    should raise RecordNotFound.
+    Fixes #7238.
+
+    *Nikita Afanasenko*
+
+*   Fix deleting from a HABTM join table upon destroying an object of a model
+    with optimistic locking enabled.
+    Fixes #5332.
+
+    *Nick Rogers*
+
+*   Use query cache/uncache when using ENV["DATABASE_URL"].
+    Fixes #6951.
+    Backport of #8074.
+
+    *kennyj*
+
+*   Do not create useless database transaction when building `has_one` association.
+
+    Example:
+
+        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.
+
+    *Nikita Afanasenko*
+
+*   Fix issue that raises `NameError` when overriding the `accepts_nested_attributes` in child classes.
+
+    Before:
+
+        class Shared::Person < ActiveRecord::Base
+          has_one :address
+
+          accepts_nested_attributes :address, :reject_if => :all_blank
         end
 
-    *Jon Leighton*
+        class Person < Shared::Person
+          accepts_nested_attributes :address
+        end
+
+        Person
+        #=> NameError: method `address_attributes=' not defined in Person
+
+    After:
+
+        Person
+        #=> Person(id: integer, ...)
+
+    Fixes #8131.
 
-*   PostgreSQL adapter only supports PostgreSQL version 8.2 and higher.
+    *Gabriel Sobrinho, Ricardo Henrique*
 
-*   ConnectionManagement middleware is changed to clean up the connection pool
-    after the rack body has been flushed.
 
-*   Added an update_column method on ActiveRecord. This new method updates a given attribute on an object, skipping validations and callbacks.
-    It is recommended to use #update_attribute unless you are sure you do not want to execute any callback, including the modification of
-    the updated_at column. It should not be called on new records.
+## Rails 3.2.12 (Feb 11, 2013) ##
+
+*   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.
+
     Example:
 
-        User.first.update_column(:name, "sebastian")         # => true
+        App.where(apikey: 0) # => SELECT * FROM users WHERE apikey = '0'
 
-    *Sebastian Martinez*
+    *Dylan Smith*
 
-*   Associations with a :through option can now use *any* association as the
-    through or source association, including other associations which have a
-    :through option and has_and_belongs_to_many associations
 
-    *Jon Leighton*
+## Rails 3.2.11 (Jan 8, 2013) ##
 
-*   The configuration for the current database connection is now accessible via
-    ActiveRecord::Base.connection_config. *fxn*
+*   Fix querying with an empty hash *Damien Mathieu* [CVE-2013-0155]
 
-*   limits and offsets are removed from COUNT queries unless both are supplied.
-    For example:
 
-        People.limit(1).count           # => 'SELECT COUNT(*) FROM people'
-        People.offset(1).count          # => 'SELECT COUNT(*) FROM people'
-        People.limit(1).offset(1).count # => 'SELECT COUNT(*) FROM people LIMIT 1 OFFSET 1'
+## Rails 3.2.10 (Jan 2, 2013) ##
 
-    *lighthouse #6262*
+*   CVE-2012-5664 options hashes should only be extracted if there are extra
+    parameters
 
-*   ActiveRecord::Associations::AssociationProxy has been split. There is now an Association class
-    (and subclasses) which are responsible for operating on associations, and then a separate,
-    thin wrapper called CollectionProxy, which proxies collection associations.
 
-    This prevents namespace pollution, separates concerns, and will allow further refactorings.
+## Rails 3.2.9 (Nov 12, 2012) ##
 
-    Singular associations (has_one, belongs_to) no longer have a proxy at all. They simply return
-    the associated record or nil. This means that you should not use undocumented methods such
-    as bob.mother.create - use bob.create_mother instead.
+*   Fix `find_in_batches` crashing when IDs are strings and start option is not specified.
 
-    *Jon Leighton*
+    *Alexis Bernard*
+
+*   Fix issue with collection associations calling first(n)/last(n) and attempting
+    to set the inverse association when `:inverse_of` was used. Fixes #8087.
+
+    *Carlos Antonio da Silva*
+
+*   Fix bug when Column is trying to type cast boolean values to integer.
+    Fixes #8067.
+
+    *Rafael Mendonça França*
+
+*   Fix bug where `rake db:test:prepare` tries to load the structure.sql into development database.
+    Fixes #8032.
+
+    *Grace Liu + Rafael Mendonça França*
+
+*   Fixed support for `DATABASE_URL` environment variable for rake db tasks. *Grace Liu*
+
+*   Fix bug where `update_columns` and `update_column` would not let you update the primary key column.
+
+    *Henrik Nyh*
+
+*   Decode URI encoded attributes on database connection URLs.
+
+    *Shawn Veader*
+
+*   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.
+
+    *Christian Seiler*
+
+*   Synchronize around deleting from the reserved connections hash.
+    Fixes #7955
+
+*   PostgreSQL adapter correctly fetches default values when using
+    multiple schemas and domains in a db. Fixes #7914
+
+    *Arturo Pie*
 
-*   Make has_many :through associations work correctly when you build a record and then save it. This
-    requires you to set the :inverse_of option on the source reflection on the join model, like so:
+*   Fix deprecation notice when loading a collection association that
+    selects columns from other tables, if a new record was previously
+    built using that association.
 
-    class Post < ActiveRecord::Base
-        has_many :taggings
-        has_many :tags, :through => :taggings
-    end
+    *Ernie Miller*
 
-    class Tagging < ActiveRecord::Base
-        belongs_to :post
-        belongs_to :tag, :inverse_of => :tagging # :inverse_of must be set!
-    end
+*   The postgres adapter now supports tables with capital letters.
+    Fix #5920
 
-    class Tag < ActiveRecord::Base
-        has_many :taggings
-        has_many :posts, :through => :taggings
-    end
+    *Yves Senn*
 
-    post = Post.first
-    tag = post.tags.build :name => "ruby"
-    tag.save # will save a Taggable linking to the post
+*   `CollectionAssociation#count` returns `0` without querying if the
+    parent record is not persisted.
+
+    Before:
+
+        person.pets.count
+        # SELECT COUNT(*) FROM "pets" WHERE "pets"."person_id" IS NULL
+        # => 0
+
+    After:
+
+        person.pets.count
+        # fires without sql query
+        # => 0
+
+    *Francesco Rodriguez*
+
+*   Fix `reset_counters` crashing on `has_many :through` associations.
+    Fix #7822.
+
+    *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.
+
+    *jrochkind*
+
+*   Rename field_changed? to _field_changed? so that users can create a field named field
+
+    *Akira Matsuda*, backported by *Steve Klabnik*
+
+*   Fix creation of through association models when using `collection=[]`
+    on a `has_many :through` association from an unsaved model.
+    Fix #7661.
+
+    *Ernie Miller*
+
+*   Explain only normal CRUD sql (select / update / insert / delete).
+    Fix problem that explains unexplainable sql. Closes #7544 #6458.
+
+    *kennyj*
+
+*   Backport test coverage to ensure that PostgreSQL auto-reconnect functionality
+    remains healthy.
+
+    *Steve Jorgensen*
+
+*   Use config['encoding'] instead of config['charset'] when executing
+    databases.rake in the mysql/mysql2. A correct option for a database.yml
+    is 'encoding'.
+
+    *kennyj*
+
+*   Fix ConnectionAdapters::Column.type_cast_code integer conversion,
+    to always convert values to integer calling #to_i. Fixes #7509.
+
+    *Thiago Pradi*
+
+*   Fix time column type casting for invalid time string values to correctly return nil.
+
+    *Adam Meehan*
+
+*   Fix `becomes` when using a configured `inheritance_column`.
+
+    *Yves Senn*
+
+*   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*
+
+*   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.
+
+    *Ravil Bayramgalin*
+
+*   Fix Column.microseconds and Column.fast_string_to_date 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.
+
+    *Rafael Mendonça França*
+
+*   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.
+
+    *kennyj*
+
+*   Allow store to work with an empty column.
+    Fix #4840.
+
+    *Jeremy Walker*
+
+*   Remove prepared statement from system query in postgresql adapter.
+    Fix #5872.
+
+    *Ivan Evtuhovich*
+
+*   Make sure `:environment` task is executed before `db:schema:load` or `db:structure:load`
+    Fixes #4772.
+
+    *Seamus Abshere*
+
+
+## Rails 3.2.8 (Aug 9, 2012) ##
+
+*   Do not consider the numeric attribute as changed if the old value is zero and the new value
+    is not a string.
+    Fixes #7237.
+
+    *Rafael Mendonça França*
+
+*   Removes the deprecation of `update_attribute`. *fxn*
+
+*   Reverted the deprecation of `composed_of`. *Rafael Mendonça França*
+
+*   Reverted the deprecation of `*_sql` association options. They will
+    be deprecated in 4.0 instead. *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
+
+    *Xavier Noria*
+
+*   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.
+
+    *Rafael Mendonça França*
+
+## Rails 3.2.7 (Jul 26, 2012) ##
+
+*   `:finder_sql` and `:counter_sql` options on collection associations
+    are deprecated. Please transition to using scopes.
 
     *Jon Leighton*
 
-*   Support the :dependent option on has_many :through associations. For historical and practical
-    reasons, :delete_all is the default deletion strategy employed by association.delete(*records),
-    despite the fact that the default strategy is :nullify for regular has_many. Also, this only
-    works at all if the source reflection is a belongs_to. For other situations, you should directly
-    modify the through association.
+*   `:insert_sql` and `:delete_sql` options on `has_and_belongs_to_many`
+    associations are deprecated. Please transition to using `has_many
+    :through`
 
     *Jon Leighton*
 
-*   Changed the behaviour of association.destroy for has_and_belongs_to_many and has_many :through.
-    From now on, 'destroy' or 'delete' on an association will be taken to mean 'get rid of the link',
-    not (necessarily) 'get rid of the associated records'.
+*   `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.
+
+    *Steve Klabnik*
+
+*   `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`.
 
-    Previously, has_and_belongs_to_many.destroy(*records) would destroy the records themselves. It
-    would not delete any records in the join table. Now, it deletes the records in the join table.
+    *Steve Klabnik*
 
-    Previously, has_many_through.destroy(*records) would destroy the records themselves, and the
-    records in the join table. [Note: This has not always been the case; previous version of Rails
-    only deleted the records themselves.] Now, it destroys only the records in the join table.
+## Rails 3.2.6 (Jun 12, 2012) ##
 
-    Note that this change is backwards-incompatible to an extent, but there is unfortunately no
-    way to 'deprecate' it before changing it. The change is being made in order to have
-    consistency as to the meaning of 'destroy' or 'delete' across the different types of associations.
+*   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.
 
-    If you wish to destroy the records themselves, you can do records.association.each(&:destroy)
+    CVE-2012-2695
+
+*   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.
 
     *Jon Leighton*
 
-*   Add :bulk => true option to change_table to make all the schema changes defined in change_table block using a single ALTER statement. *Pratik Naik*
+## Rails 3.2.5 (Jun 1, 2012) ##
 
-    Example:
+*   Restore behavior of Active Record 3.2.3 scopes.
+    A series of commits relating to preloading and scopes caused a regression.
 
-    change_table(:users, :bulk => true) do |t|
-        t.string :company_name
-        t.change :birthdate, :datetime
-    end
+    *Andrew White*
 
-    This will now result in:
 
-        ALTER TABLE `users` ADD COLUMN `company_name` varchar(255), CHANGE `updated_at` `updated_at` datetime DEFAULT NULL
+## Rails 3.2.4 (May 31, 2012) ##
 
-*   Removed support for accessing attributes on a has_and_belongs_to_many join table. This has been
-    documented as deprecated behaviour since April 2006. Please use has_many :through instead.
-    *Jon Leighton*
+*   Perf fix: Don't load the records when doing assoc.delete_all.
+    GH #6289. *Jon Leighton*
 
-*   Added a create_association! method for has_one and belongs_to associations. *Jon Leighton*
+*   Association preloading shouldn't be affected by the current scoping.
+    This could cause infinite recursion and potentially other problems.
+    See GH #5667. *Jon Leighton*
 
-*   Migration files generated from model and constructive migration generators
-    (for example, add_name_to_users) use the reversible migration's `change`
-    method instead of the ordinary `up` and `down` methods. *Prem Sichanugrist*
+*   Datetime attributes are forced to be changed. GH #3965
 
-*   Removed support for interpolating string SQL conditions on associations. Instead, you should
-    use a proc, like so:
+*   Fix attribute casting. GH #5549
 
-    Before:
+*   Fix #5667. Preloading should ignore scoping.
 
-        has_many :things, :conditions => 'foo = #{bar}'
+*   Predicate builder should not recurse for determining where columns.
+    Thanks to Ben Murphy for reporting this! CVE-2012-2661
 
-    After:
 
-        has_many :things, :conditions => proc { "foo = #{bar}" }
+## Rails 3.2.3 (March 30, 2012) ##
 
-    Inside the proc, 'self' is the object which is the owner of the association, unless you are
-    eager loading the association, in which case 'self' is the class which the association is within.
+*   Added find_or_create_by_{attribute}! dynamic method. *Andrew White*
 
-    You can have any "normal" conditions inside the proc, so the following will work too:
+*   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*
 
-        has_many :things, :conditions => proc { ["foo = ?", bar] }
+*   Update ActiveRecord::AttributeMethods#attribute_present? to return false for empty strings. *Jacobkg*
 
-    Previously :insert_sql and :delete_sql on has_and_belongs_to_many association allowed you to call
-    'record' to get the record being inserted or deleted. This is now passed as an argument to
-    the proc.
+*   Fix associations when using per class databases. *larskanis*
 
-*   Added ActiveRecord::Base#has_secure_password (via ActiveModel::SecurePassword) to encapsulate dead-simple password usage with BCrypt encryption and salting [DHH]. Example:
+*   Revert setting NOT NULL constraints in add_timestamps *fxn*
 
-        # Schema: User(name:string, password_digest:string, password_salt:string)
-        class User < ActiveRecord::Base
-          has_secure_password
-        end
+*   Fix mysql to use proper text types. Fixes #3931. *kennyj*
 
-        user = User.new(:name => "david", :password => "", :password_confirmation => "nomatch")
-        user.save                                                      # => false, password required
-        user.password = "mUc3m00RsqyRe"
-        user.save                                                      # => false, confirmation doesn't match
-        user.password_confirmation = "mUc3m00RsqyRe"
-        user.save                                                      # => true
-        user.authenticate("notright")                                  # => false
-        user.authenticate("mUc3m00RsqyRe")                             # => user
-        User.find_by_name("david").try(:authenticate, "notright")      # => nil
-        User.find_by_name("david").try(:authenticate, "mUc3m00RsqyRe") # => user
+*   Fix #5069 - Protect foreign key from mass assignment through association builder. *byroot*
 
 
-*   When a model is generated add_index is added by default for belongs_to or references columns
+## Rails 3.2.2 (March 1, 2012) ##
 
-    rails g model post user:belongs_to will generate the following:
+*   No changes.
 
-        class CreatePosts < ActiveRecord::Migration
-          def change
-            create_table :posts do |t|
-              t.belongs_to :user
-              t.timestamps
-            end
-            add_index :posts, :user_id
-          end
-        end
 
-    *Santiago Pastorino*
+## Rails 3.2.1 (January 26, 2012) ##
 
-*   Setting the id of a belongs_to object will update the reference to the
-    object. *#2989 state:resolved*
+*   The threshold for auto EXPLAIN is ignored if there's no logger. *fxn*
 
-*   ActiveRecord::Base#dup and ActiveRecord::Base#clone semantics have changed
-    to closer match normal Ruby dup and clone semantics.
+*   Call `to_s` on the value passed to `table_name=`, in particular symbols
+    are supported (regression). *Sergey Nartimov*
 
-*   Calling ActiveRecord::Base#clone will result in a shallow copy of the record,
-    including copying the frozen state.  No callbacks will be called.
+*   Fix possible race condition when two threads try to define attribute
+    methods for the same class. *Jon Leighton*
 
-*   Calling ActiveRecord::Base#dup will duplicate the record, including calling
-    after initialize hooks.  Frozen state will not be copied, and all associations
-    will be cleared.  A duped record will return true for new_record?, have a nil
-    id field, and is saveable.
 
-*   Migrations can be defined as reversible, meaning that the migration system
-    will figure out how to reverse your migration.  To use reversible migrations,
-    just define the "change" method.  For example:
+## Rails 3.2.0 (January 20, 2012) ##
 
-        class MyMigration < ActiveRecord::Migration
-          def change
-            create_table(:horses) do
-              t.column :content, :text
-              t.column :remind_at, :datetime
+*   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!`.
+
+    Before:
+
+        class Order < ActiveRecord::Base
+          def cancel!
+            transaction do
+              lock!
+              # ... cancelling logic
             end
           end
         end
 
-    Some things cannot be automatically reversed for you.  If you know how to
-    reverse those things, you should define 'up' and 'down' in your migration.  If
-    you define something in `change` that cannot be reversed, an
-    IrreversibleMigration exception will be raised when going down.
+    After:
 
-*   Migrations should use instance methods rather than class methods:
-        class FooMigration < ActiveRecord::Migration
-          def up
-            ...
+        class Order < ActiveRecord::Base
+          def cancel!
+            with_lock do
+              # ... cancelling logic
+            end
           end
         end
 
-    *Aaron Patterson*
+    *Olek Janiszewski*
+
+*   'on' and 'ON' boolean columns values are type casted to true
+    *Santiago Pastorino*
+
+*   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).
+
+    Example:
+      rake db:migrate SCOPE=blog
+
+    *Piotr Sarnacki*
+
+*   Migrations copied from engines are now scoped with engine's name,
+    for example 01_create_posts.blog.rb. *Piotr Sarnacki*
+
+*   Implements `AR::Base.silence_auto_explain`. This method allows the user to
+    selectively disable automatic EXPLAINs within a block. *fxn*
+
+*   Implements automatic EXPLAIN logging for slow queries.
+
+    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.
+
+    As of this writing there's support for SQLite, MySQL (mysql2 adapter), and
+    PostgreSQL.
+
+    *fxn*
+
+*   Implemented ActiveRecord::Relation#pluck method
+
+    Method returns Array of column value from table under ActiveRecord model
+
+        Client.pluck(:id)
+
+    *Bogdan Gusiev*
+
+*   Automatic closure of connections in threads is deprecated.  For example
+    the following code is deprecated:
+
+    Thread.new { Post.find(1) }.join
+
+    It should be changed to close the database connection at the end of
+    the thread:
+
+    Thread.new {
+      Post.find(1)
+      Post.connection.close
+    }.join
+
+    Only people who spawn threads in their application code need to worry
+    about this change.
+
+*   Deprecated:
+
+      * `set_table_name`
+      * `set_inheritance_column`
+      * `set_sequence_name`
+      * `set_primary_key`
+      * `set_locking_column`
+
+    Use an assignment method instead. For example, instead of `set_table_name`, use `self.table_name=`:
+
+         class Project < ActiveRecord::Base
+           self.table_name = "project"
+         end
+
+    Or define your own `self.table_name` method:
+
+         class Post < ActiveRecord::Base
+           def self.table_name
+             "special_" + super
+           end
+         end
+         Post.table_name # => "special_posts"
+
+    *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*
+
+*   Implemented ActiveRecord::Relation#explain. *fxn*
+
+*   Add ActiveRecord::Relation#uniq for generating unique queries.
+
+    Before:
+
+        Client.select('DISTINCT name')
+
+    After:
+
+        Client.select(:name).uniq
+
+    This also allows you to revert the unqueness in a relation:
+
+        Client.select(:name).uniq.uniq(false)
+
+    *Jon Leighton*
+
+*   Support index sort order in sqlite, mysql and postgres adapters. *Vlad Jebelev*
+
+*   Allow the :class_name option for associations to take a symbol (:Client) in addition to
+    a string ('Client').
+
+    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.
+
+    *Jon Leighton*
+
+*   In development mode the db:drop task also drops the test database. For symmetry with
+    the db:create task. *Dmitriy Kiriyenko*
+
+*   Added ActiveRecord::Base.store for declaring simple single-column key/value stores *DHH*
+
+        class User < ActiveRecord::Base
+          store :settings, accessors: [ :color, :homepage ]
+        end
+
+        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
+
+
+*   MySQL: case-insensitive uniqueness validation avoids calling LOWER when
+    the column already uses a case-insensitive collation. Fixes #561.
+
+    *Joseph Palermo*
+
+*   Transactional fixtures enlist all active database connections. You can test
+    models on different connections without disabling transactional fixtures.
 
-*   has_one maintains the association with separate after_create/after_update instead
-    of a single after_save. *fxn*
+    *Jeremy Kemper*
 
-*   The following code:
+*   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:
 
-        Model.limit(10).scoping { Model.count }
+        User.where(:first_name => "Scarlett").first_or_create!(:last_name => "Johansson")
 
-    now generates the following SQL:
+    *Andrés Mejía*
 
-        SELECT COUNT(*) FROM models LIMIT 10
+*   Fix nested attributes bug where _destroy parameter is taken into account
+    during :reject_if => :all_blank (fixes #2937)
 
-    This may not return what you want.  Instead, you may with to do something
-    like this:
+    *Aaron Christy*
 
-        Model.limit(10).scoping { Model.all.size }
+*   Add ActiveSupport::Cache::NullStore for use in development and testing.
 
-    *Aaron Patterson*
+    *Brian Durand*
 
-Please check [3-0-stable](https://github.com/rails/rails/blob/3-0-stable/activerecord/CHANGELOG) for previous changes.
+Please check [3-1-stable](https://github.com/rails/rails/blob/3-1-stable/activerecord/CHANGELOG.md) for previous changes.