activerecord 3.1.9 → 3.2.12

data/CHANGELOG.md

@@ -1,525 +1,506 @@
-## Rails 3.1.9
+## Rails 3.2.12 (unreleased) ##
 
-*  CVE-2012-5664 ensure that options are never taken from the first parameter
+*   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.
 
-## Rails 3.1.8 (Aug 9, 2012)
+    Example:
 
-*   No changes.
+        App.where(apikey: 0) # => SELECT * FROM users WHERE apikey = '0'
 
-## Rails 3.1.7 (Jul 26, 2012)
+    *Dylan Smith*
 
-*   No changes.
+## Rails 3.2.11 (Jan 8, 2013) ##
 
-## Rails 3.1.6 (Jun 12, 2012)
+*   Fix querying with an empty hash *Damien Mathieu* [CVE-2013-0155]
 
-*   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.10 ##
 
-    CVE-2012-2695
+*   CVE-2012-5664 options hashes should only be extracted if there are extra
+    parameters
 
-## Rails 3.1.5 (May 31, 2012) ##
+## Rails 3.2.9 (Nov 12, 2012) ##
 
-*   Fix type_to_sql with text and limit on mysql/mysql2. Fix GH #3931.
+*   Fix issue with collection associations calling first(n)/last(n) and attempting
+    to set the inverse association when `:inverse_of` was used. Fixes #8087.
 
-*   only log an error if there is a logger. fixes #5226
+    *Carlos Antonio da Silva*
 
-*   fix activerecord query_method regression with offset into Fixnum
+*   Fix bug when Column is trying to type cast boolean values to integer.
+    Fixes #8067.
 
-*   predicate builder should not recurse for determining where columns.
-    Thanks to Ben Murphy for reporting this! CVE-2012-2661
+    *Rafael Mendonça França*
 
-## Rails 3.1.4 (unreleased) ##
+*   Fix bug where `rake db:test:prepare` tries to load the structure.sql into development database.
+    Fixes #8032.
 
-*   Fix a custom primary key regression *GH 3987*
+    *Grace Liu + Rafael Mendonça França*
 
-    *Jon Leighton*
+*   Fixed support for `DATABASE_URL` environment variable for rake db tasks. *Grace Liu*
 
-*   Perf fix (second try): don't load records for `has many :dependent =>
-    :delete_all` *GH 3672*
+*   Fix bug where `update_columns` and `update_column` would not let you update the primary key column.
 
-    *Jon Leighton*
+    *Henrik Nyh*
 
-*   Fix accessing `proxy_association` method from an association extension
-    where the calls are chained. *GH #3890*
+*   Decode URI encoded attributes on database connection URLs.
 
-    (E.g. `post.comments.where(bla).my_proxy_method`)
+    *Shawn Veader*
 
-    *Jon Leighton*
+*   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.
 
-*   Perf fix: MySQL primary key lookup was still slow for very large
-    tables. *GH 3678*
+    *Christian Seiler*
 
-    *Kenny J*
+*   Synchronize around deleting from the reserved connections hash.
+    Fixes #7955
 
-*   Perf fix: If a table has no primary key, don't repeatedly ask the database for it.
+*   PostgreSQL adapter correctly fetches default values when using
+    multiple schemas and domains in a db. Fixes #7914
 
-    *Julius de Bruijn*
+    *Arturo Pie*
 
-## Rails 3.1.3 (unreleased) ##
+*   Fix deprecation notice when loading a collection association that
+    selects columns from other tables, if a new record was previously
+    built using that association.
 
-*   Perf fix: If we're deleting all records in an association, don't add a IN(..) clause
-    to the query. *GH 3672*
+    *Ernie Miller*
 
-    *Jon Leighton*
+*   The postgres adapter now supports tables with capital letters.
+    Fix #5920
 
-*   Fix bug with referencing other mysql databases in set_table_name. *GH 3690*
+    *Yves Senn*
 
-*   Fix performance bug with mysql databases on a server with lots of other databses. *GH 3678*
+*   `CollectionAssociation#count` returns `0` without querying if the
+    parent record is not persisted.
 
-    *Christos Zisopoulos and Kenny J*
+    Before:
 
-## Rails 3.1.2 (unreleased) ##
+        person.pets.count
+        # SELECT COUNT(*) FROM "pets" WHERE "pets"."person_id" IS NULL
+        # => 0
 
-*   Fix problem with prepared statements and PostgreSQL when multiple schemas are used.
-    *GH #3232*
+    After:
 
-    *Juan M. Cuello*
+        person.pets.count
+        # fires without sql query
+        # => 0
 
-*   Fix bug with PostgreSQLAdapter#indexes. When the search path has multiple schemas, spaces
-    were not being stripped from the schema names after the first.
+    *Francesco Rodriguez*
 
-    *Sean Kirby*
+*   Fix `reset_counters` crashing on `has_many :through` associations.
+    Fix #7822.
 
-*   Preserve SELECT columns on the COUNT for finder_sql when possible. *GH 3503*
+    *lulalala*
 
-    *Justin Mazzi*
+*   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.
 
-*   Reset prepared statement cache when schema changes impact statement results. *GH 3335*
+    *jrochkind*
 
-    *Aaron Patterson*
+*   Rename field_changed? to _field_changed? so that users can create a field named field
 
-*   Postgres: Do not attempt to deallocate a statement if the connection is no longer active.
+    *Akira Matsuda*, backported by *Steve Klabnik*
 
-    *Ian Leitch*
+*   Fix creation of through association models when using `collection=[]`
+    on a `has_many :through` association from an unsaved model.
+    Fix #7661.
 
-*   Prevent QueryCache leaking database connections. *GH 3243*
+    *Ernie Miller*
 
-    *Mark J. Titorenko*
+*   Explain only normal CRUD sql (select / update / insert / delete).
+    Fix problem that explains unexplainable sql. Closes #7544 #6458.
 
-*   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*
+    *kennyj*
 
-    *Jon Leighton*
+*   Backport test coverage to ensure that PostgreSQL auto-reconnect functionality
+    remains healthy.
 
-*   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.
+    *Steve Jorgensen*
 
-    *Jon Leighton*
+*   Use config['encoding'] instead of config['charset'] when executing
+    databases.rake in the mysql/mysql2. A correct option for a database.yml
+    is 'encoding'.
 
-*   Fix adding multiple instances of the same record to a has_many :through. *GH #3425*
+    *kennyj*
 
-    *Jon Leighton*
+*   Fix ConnectionAdapters::Column.type_cast_code integer conversion,
+    to always convert values to integer calling #to_i. Fixes #7509.
 
-*   Fix creating records in a through association with a polymorphic source type. *GH #3247*
+    *Thiago Pradi*
 
-    *Jon Leighton*
+*   Fix time column type casting for invalid time string values to correctly return nil.
 
-*   MySQL: use the information_schema than the describe command when we look for a primary key. *GH #3440*
-    *Kenny J*
+    *Adam Meehan*
 
-## Rails 3.1.1 (October 7, 2011) ##
+*   Fix `becomes` when using a configured `inheritance_column`.
 
-*   Raise an exception if the primary key of a model in an association is needed
-    but unknown. Fixes #3207.
+    *Yves Senn*
 
-    *Jon Leighton*
+*   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.
 
-*   Add deprecation for the preload_associations method. Fixes #3022.
+    *Dave Desrochers*
 
-    *Jon Leighton*
+*   Round usec when comparing timestamp attributes in the dirty tracking.
+    Fixes #6975.
 
-*   Don't require a DB connection when loading a model that uses set_primary_key. GH #2807.
+    *kennyj*
 
-    *Jon Leighton*
+*   Use inversed parent for first and last child of has_many association.
 
-*   Fix using select() with a habtm association, e.g. Person.friends.select(:name). GH #3030 and
-    \#2923.
+    *Ravil Bayramgalin*
 
-    *Hendy Tanata*
+*   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.
 
-*   Fix belongs_to polymorphic with custom primary key on target. GH #3104.
+    *Ari Pollak*
 
-    *Jon Leighton*
+*   Fix `increment!`, `decrement!`, `toggle!` that was skipping callbacks.
+    Fixes #7306.
 
-*   CollectionProxy#replace should change the DB records rather than just mutating the array.
-    Fixes #3020.
+    *Rafael Mendonça França*
 
-    *Jon Leighton*
+*   Fix AR#create to return an unsaved record when AR::RecordInvalid is
+    raised. Fixes #3217.
 
-*   LRU cache in mysql and sqlite are now per-process caches.
+    *Dave Yeu*
 
-    * lib/active_record/connection_adapters/mysql_adapter.rb: LRU cache
-  	  keys are per process id.
-    * lib/active_record/connection_adapters/sqlite_adapter.rb: ditto
+*   Remove unnecessary transaction when assigning has_one associations with a nil or equal value.
+    Fix #7191.
 
-    *Aaron Patterson*
+    *kennyj*
 
-*   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'.
+*   Allow store to work with an empty column.
+    Fix #4840.
 
-*   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*
+    *Jeremy Walker*
 
-*   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.
+*   Remove prepared statement from system query in postgresql adapter.
+    Fix #5872.
 
-    *Jon Leighton*
+    *Ivan Evtuhovich*
 
-*   Don't send any queries to the database when the foreign key of a belongs_to is nil. Fixes
-    GH #2828. *Georg Friedrich*
+*   Make sure `:environment` task is executed before `db:schema:load` or `db:structure:load`
+    Fixes #4772.
 
-*   Fixed find_in_batches method to not include order from default_scope. See GH #2832 *Arun Agrawal*
+    *Seamus Abshere*
 
-*   Don't compute table name for abstract classes. Fixes problem with setting the primary key
-    in an abstract class. See GH #2791. *Akira Matsuda*
 
-*   Psych errors with poor yaml formatting are proxied. Fixes GH #2645 and
-    GH #2731
+## Rails 3.2.8 (Aug 9, 2012) ##
 
-*   Use the LIMIT word with the methods #last and #first. Fixes GH #2783 *Damien Mathieu*
+*   Do not consider the numeric attribute as changed if the old value is zero and the new value
+    is not a string.
+    Fixes #7237.
 
-## Rails 3.1.0 (August 30, 2011) ##
+    *Rafael Mendonça França*
 
-*   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.
+*   Removes the deprecation of `update_attribute`. *fxn*
 
-    *Jon Leighton*
+*   Reverted the deprecation of `composed_of`. *Rafael Mendonça França*
 
-*   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*
+*   Reverted the deprecation of `*_sql` association options. They will
+    be deprecated in 4.0 instead. *Jon Leighton*
 
-*   Deprecated the AssociationCollection constant. CollectionProxy is now the appropriate constant
-    to use, though be warned that this is not really a public API.
+*   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
 
-    This should solve upgrade problems with the will_paginate plugin (and perhaps others). Thanks
-    Paul Battley for reporting.
+    *Xavier Noria*
 
-    *Jon Leighton*
+*   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.
 
-*   ActiveRecord::MacroReflection::AssociationReflection#build_record has a new method signature.
+    *Rafael Mendonça França*
 
-    Before: def build_association(*options)
-    After:  def build_association(*options, &block)
+## Rails 3.2.7 (Jul 26, 2012) ##
 
-    Users who are redefining this method to extend functionality should ensure that the block is
-    passed through to ActiveRecord::Base#new.
+*   `:finder_sql` and `:counter_sql` options on collection associations
+    are deprecated. Please transition to using scopes.
 
-    This change is necessary to fix https://github.com/rails/rails/issues/1842.
+    *Jon Leighton*
 
-    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.
+*   `:insert_sql` and `:delete_sql` options on `has_and_belongs_to_many`
+    associations are deprecated. Please transition to using `has_many
+    :through`
 
     *Jon Leighton*
 
-*   AR#pluralize_table_names can be used to singularize/pluralize table name of an individual model:
+*   `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.
 
-        class User < ActiveRecord::Base
-          self.pluralize_table_names = false
-        end
+    *Steve Klabnik*
 
-    Previously this could only be set globally for all models through ActiveRecord::Base.pluralize_table_names. *Guillermo Iguaran*
+*   `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`.
 
-*   Add block setting of attributes to singular associations:
+    *Steve Klabnik*
 
-        class User < ActiveRecord::Base
-          has_one :account
-        end
+## Rails 3.2.6 (Jun 12, 2012) ##
 
-        user.build_account{ |a| a.credit_limit => 100.0 }
+*   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.
 
-    The block is called after the instance has been initialized. *Andrew White*
+    CVE-2012-2695
 
-*   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*
+*   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.
 
-*   CSV Fixtures are deprecated and support will be removed in Rails 3.2.0
+    *Jon Leighton*
 
-*   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:
+## Rails 3.2.5 (Jun 1, 2012) ##
 
-        class Post < ActiveRecord::Base
-          attr_accessible :title
-          attr_accessible :title, :published_at, :as => :admin
-        end
+*   Restore behavior of Active Record 3.2.3 scopes.
+    A series of commits relating to preloading and scopes caused a regression.
 
-        Post.new(params[:post], :as => :admin)
+    *Andrew White*
 
-    assign_attributes() with similar API was also added and attributes=(params, guard) was deprecated.
 
-    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.
+## Rails 3.2.4 (May 31, 2012) ##
 
-    *Josh Kalderimis*
+*   Perf fix: Don't load the records when doing assoc.delete_all.
+    GH #6289. *Jon Leighton*
 
-*   default_scope can take a block, lambda, or any other object which responds to `call` for lazy
-    evaluation:
+*   Association preloading shouldn't be affected by the current scoping.
+    This could cause infinite recursion and potentially other problems.
+    See GH #5667. *Jon Leighton*
 
-        default_scope { ... }
-        default_scope lambda { ... }
-        default_scope method(:foo)
+*   Datetime attributes are forced to be changed. GH #3965
 
-    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 attribute casting. GH #5549
 
-*   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.
+*   Fix #5667. Preloading should ignore scoping.
 
-    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.
+*   Predicate builder should not recurse for determining where columns.
+    Thanks to Ben Murphy for reporting this! CVE-2012-2661
 
-    *Jon Leighton*
 
-*   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.):
+## Rails 3.2.3 (March 30, 2012) ##
 
-        class Post < ActiveRecord::Base
-          def self.default_scope
-            where(:published => true).where(:hidden => false)
-          end
-        end
+*   Added find_or_create_by_{attribute}! dynamic method. *Andrew White*
 
-    *Jon Leighton*
+*   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*
 
-*   PostgreSQL adapter only supports PostgreSQL version 8.2 and higher.
+*   Update ActiveRecord::AttributeMethods#attribute_present? to return false for empty strings. *Jacobkg*
 
-*   ConnectionManagement middleware is changed to clean up the connection pool
-    after the rack body has been flushed.
+*   Fix associations when using per class databases. *larskanis*
 
-*   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.
-    Example:
+*   Revert setting NOT NULL constraints in add_timestamps *fxn*
 
-        User.first.update_column(:name, "sebastian")         # => true
+*   Fix mysql to use proper text types. Fixes #3931. *kennyj*
 
-    *Sebastian Martinez*
+*   Fix #5069 - Protect foreign key from mass assignment through association builder. *byroot*
 
-*   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.2 (March 1, 2012) ##
 
-*   The configuration for the current database connection is now accessible via
-    ActiveRecord::Base.connection_config. *fxn*
+*   No changes.
 
-*   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.1 (January 26, 2012) ##
 
-    *lighthouse #6262*
+*   The threshold for auto EXPLAIN is ignored if there's no logger. *fxn*
 
-*   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.
+*   Call `to_s` on the value passed to `table_name=`, in particular symbols
+    are supported (regression). *Sergey Nartimov*
 
-    This prevents namespace pollution, separates concerns, and will allow further refactorings.
+*   Fix possible race condition when two threads try to define attribute
+    methods for the same class. *Jon Leighton*
 
-    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.
 
-    *Jon Leighton*
+## Rails 3.2.0 (January 20, 2012) ##
 
-*   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:
+*   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!`.
 
-    class Post < ActiveRecord::Base
-        has_many :taggings
-        has_many :tags, :through => :taggings
-    end
+    Before:
 
-    class Tagging < ActiveRecord::Base
-        belongs_to :post
-        belongs_to :tag, :inverse_of => :tagging # :inverse_of must be set!
-    end
+        class Order < ActiveRecord::Base
+          def cancel!
+            transaction do
+              lock!
+              # ... cancelling logic
+            end
+          end
+        end
 
-    class Tag < ActiveRecord::Base
-        has_many :taggings
-        has_many :posts, :through => :taggings
-    end
+    After:
 
-    post = Post.first
-    tag = post.tags.build :name => "ruby"
-    tag.save # will save a Taggable linking to the post
+        class Order < ActiveRecord::Base
+          def cancel!
+            with_lock do
+              # ... cancelling logic
+            end
+          end
+        end
 
-    *Jon Leighton*
+    *Olek Janiszewski*
 
-*   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.
+*   'on' and 'ON' boolean columns values are type casted to true
+    *Santiago Pastorino*
 
-    *Jon Leighton*
+*   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).
 
-*   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'.
+    Example:
+      rake db:migrate SCOPE=blog
 
-    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.
+    *Piotr Sarnacki*
 
-    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.
+*   Migrations copied from engines are now scoped with engine's name,
+    for example 01_create_posts.blog.rb. *Piotr Sarnacki*
 
-    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.
+*   Implements `AR::Base.silence_auto_explain`. This method allows the user to
+    selectively disable automatic EXPLAINs within a block. *fxn*
 
-    If you wish to destroy the records themselves, you can do records.association.each(&:destroy)
+*   Implements automatic EXPLAIN logging for slow queries.
 
-    *Jon Leighton*
+    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.
 
-*   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*
+    As of this writing there's support for SQLite, MySQL (mysql2 adapter), and
+    PostgreSQL.
 
-    Example:
+    *fxn*
 
-    change_table(:users, :bulk => true) do |t|
-        t.string :company_name
-        t.change :birthdate, :datetime
-    end
+*   Implemented ActiveRecord::Relation#pluck method
 
-    This will now result in:
+    Method returns Array of column value from table under ActiveRecord model
 
-        ALTER TABLE `users` ADD COLUMN `company_name` varchar(255), CHANGE `updated_at` `updated_at` datetime DEFAULT NULL
+        Client.pluck(:id)
 
-*   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*
+    *Bogdan Gusiev*
 
-*   Added a create_association! method for has_one and belongs_to associations. *Jon Leighton*
+*   Automatic closure of connections in threads is deprecated.  For example
+    the following code is deprecated:
 
-*   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*
+    Thread.new { Post.find(1) }.join
 
-*   Removed support for interpolating string SQL conditions on associations. Instead, you should
-    use a proc, like so:
+    It should be changed to close the database connection at the end of
+    the thread:
 
-    Before:
+    Thread.new {
+      Post.find(1)
+      Post.connection.close
+    }.join
 
-        has_many :things, :conditions => 'foo = #{bar}'
+    Only people who spawn threads in their application code need to worry
+    about this change.
 
-    After:
+*   Deprecated:
+
+      * `set_table_name`
+      * `set_inheritance_column`
+      * `set_sequence_name`
+      * `set_primary_key`
+      * `set_locking_column`
 
-        has_many :things, :conditions => proc { "foo = #{bar}" }
+    Use an assignment method instead. For example, instead of `set_table_name`, use `self.table_name=`:
 
-    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.
+         class Project < ActiveRecord::Base
+           self.table_name = "project"
+         end
 
-    You can have any "normal" conditions inside the proc, so the following will work too:
+    Or define your own `self.table_name` method:
 
-        has_many :things, :conditions => proc { ["foo = ?", bar] }
+         class Post < ActiveRecord::Base
+           def self.table_name
+             "special_" + super
+           end
+         end
+         Post.table_name # => "special_posts"
 
-    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.
+    *Jon Leighton*
 
-*   Added ActiveRecord::Base#has_secure_password (via ActiveModel::SecurePassword) to encapsulate dead-simple password usage with BCrypt encryption and salting [DHH]. Example:
+*   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*
 
-        # Schema: User(name:string, password_digest:string, password_salt:string)
-        class User < ActiveRecord::Base
-          has_secure_password
-        end
+*   Implemented ActiveRecord::Relation#explain. *fxn*
 
-        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
+*   Add ActiveRecord::Relation#uniq for generating unique queries.
 
+    Before:
 
-*   When a model is generated add_index is added by default for belongs_to or references columns
+        Client.select('DISTINCT name')
 
-    rails g model post user:belongs_to will generate the following:
+    After:
 
-        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
+        Client.select(:name).uniq
 
-    *Santiago Pastorino*
+    This also allows you to revert the unqueness in a relation:
 
-*   Setting the id of a belongs_to object will update the reference to the
-    object. *#2989 state:resolved*
+        Client.select(:name).uniq.uniq(false)
 
-*   ActiveRecord::Base#dup and ActiveRecord::Base#clone semantics have changed
-    to closer match normal Ruby dup and clone semantics.
+    *Jon Leighton*
 
-*   Calling ActiveRecord::Base#clone will result in a shallow copy of the record,
-    including copying the frozen state.  No callbacks will be called.
+*   Support index sort order in sqlite, mysql and postgres adapters. *Vlad Jebelev*
 
-*   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.
+*   Allow the :class_name option for associations to take a symbol (:Client) in addition to
+    a string ('Client').
 
-*   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:
+    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.
 
-        class MyMigration < ActiveRecord::Migration
-          def change
-            create_table(:horses) do
-              t.column :content, :text
-              t.column :remind_at, :datetime
-            end
-          end
-        end
+    *Jon Leighton*
 
-    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.
+*   In development mode the db:drop task also drops the test database. For symmetry with
+    the db:create task. *Dmitriy Kiriyenko*
 
-*   Migrations should use instance methods rather than class methods:
-        class FooMigration < ActiveRecord::Migration
-          def up
-            ...
-          end
+*   Added ActiveRecord::Base.store for declaring simple single-column key/value stores *DHH*
+
+        class User < ActiveRecord::Base
+          store :settings, accessors: [ :color, :homepage ]
         end
 
-    *Aaron Patterson*
+        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.