symbolize_keys => symbolize_keys! on new hash;

"There're" => There are for better readability
Merge pull request #10264 from cconstantine/master

Postgresql array columns don't properly escape single quote strings when loading fixtures
destroys association records before saving/inserting new association records

fixes bug introduced by  #3329
These are the conditions necessary to reproduce the bug:
- For an association, autosave => true.
- An association record is being destroyed
- A new association record is being created.
- There is a unique index one of the association's fields.
- The record being created has the same value as the record being
destroyed on the indexed field.

Before, the deletion of records was postponed until after all
insertions/saves.  Therefore the new record with the identical value in
the indexed field caused a non-unique value error to be thrown at the database
level.

With this fix, the deletions happen first, before the insertions/saves.
Therefore the record with the duplicate value is gone from the database
before the new record is created, thereby avoiding the non-uniuqe value
error.
Merge pull request #10183 from jholton/fix_association_auto_save

autosave_association issue that occurs when table has unique index
fix HashWithIndifferentAccess#to_hash behaviour
Revert "Merge pull request #10183 from jholton/fix_association_auto_save"

This reverts commit e8727d37fc49d5bf9976c3cb5c46badb92cf4ced, reversing
changes made to d098e1c24bc145e0cc14532348436e14dc46d375.

Reason: it broke the mysql build
Merge branch 'master' of github.com:rails/rails
Merge pull request #10265 from wangjohn/documenting_actionview

Adding documentation to Renderer
Merge pull request #10267 from vipulnsward/use_destructive_method

symbolize_keys => symbolize_keys! on new hash; change sentence
fix respond_to? for non selected column

fixes #4208

If a query selects only a few columns and gives custom names to
those columns then respond_to? was returning true for the non
selected columns. However calling those non selected columns
raises exception.

    post = Post.select("'title' as post_title").first

In the above case when `post.body` is invoked then an exception is
raised since `body` attribute is not selected. Howevere `respond_to?`
did not behave correctly.

    pos.respond_to?(:body) #=> true

Reason was that Active Record calls `super` to pass the call to
Active Model and all the columns are defined on Active Model.

Fix is to actually check if the data returned from the db contains
the data for column in question.
Merge pull request #10211 from neerajdotname/4208

fix respond_to? for non selected column
Simplify ERB example code
There are now 6 request methods including PATCH
Typo Fix in AR CHANGELOG [ci skip]
Merge pull request #10273 from prathamesh-sonpatki/AR-typos

Typo Fix in AR CHANGELOG [ci skip]
Rewrites a CHANGELOG entry.

The entry is basically copy & paste of the commit message, but the CHANGELOG
has a different purpose than Git history, it just communicates what is new:

* No need to explain why did the bug happen (unless it is truly relevant).

* No need to explain how was the bug fixed.

* Whether the user gives new names to columns does not really matter, use of
  select to cherry-pick a column for example also presented that behaviour.
  Non-selected attributes are the key, either because they were not included
  in the selected list, or because they were but with a different alias.

* In the case of an attribute alias, what you really want to depict is that
  respond_to? returns false for the original attribute name.
if singletons belong to the contract, test them

Object#respond_to? returns singletons and thus we inherit that contract.
The implementation of the predicate is good, but the test is only
checking boolean semantics, which in this case is not enough.
Increase readability of ternary statement in build method
Merge pull request #10275 from buddhamagnet/master

Increase readability of ternary statement in build method
fix typos