Rely on NameError#name instead of its error message

Format the datetime string according to the precision of the datetime field.

Conflicts:
	activerecord/CHANGELOG.md

Fixed automatic inverse_of for models nested in module

Conflicts:
	activerecord/CHANGELOG.md

Integration requests should work in contexts without setup and teardown

Changed ActiveRecord::Relation#update behavior so that it will work on Relation objects without giving id

Conflicts:
	activerecord/CHANGELOG.md

Updating guides for Rails 5.0

Incompatible to rounding behavior between MySQL 5.6 and earlier.

In 5.5, when you insert `2014-08-17 12:30:00.999999` the fractional part
is ignored. In 5.6, it's rounded to `2014-08-17 12:30:01`:

http://bugs.mysql.com/bug.php?id=68760

    warning: ambiguous first argument; put parentheses or a space even after
    `/' operator'`

Thanks @robin850.

Fix issue with reaping_frequency type.

This constant may be define for auxiliar gems like rails-html-sanitizer
and these methods call will fail.

Add --skip-action-mailer (or -M) to rails generate

This code was there just to convert entries generated in Rails
4.0.0.beta1 applications to a supported format.

It is almost unlikely that any existent application have this cache
entry format in their caches at the point that Rails 5 will be released
so we don't need this code anymore.

We should convert when @v is defined not @value.

The test was calling value first that already converts the entry so we
are not catching this bug.

So we can change the arity later.

A few of the tests weren't testing anything of value. The IP Address
tests are testing the type, not behavior of the connection adapter.
There are two CVE regression tests which are important, but don't have a
good place to go, so I've left them alone for now, as they call `quote`
and the focus right now is removing `column` from `type_cast`

The column itself has no actual impact on the return value. These were
actually testing the behavior of the type object, which is sufficiently
covered elsewhere.

The behavior tested by the removed lines is sufficiently covered
elsewhere.

The string encoding test wasn't using the types for anything. The
boolean casting test included logic that should be in the tests for the
types, and the string test was legitimately not testing anything useful.

The validator has access to richer type information

SQL has mechanisms we can use to copy data from one table into another.

As we move towards removing the types from the column objects, any
remaining places which have access to richer type information should be
using it.

The column is no longer used for anything besides type casting, which is
what we're trying to remove from the column entirely.

Update copyright notices to 2015 [ci skip]

Correctly use the response's status code calling head

Indent the list content by 4 spaces instead of 2 to match the other
changelog files. Also wrap the lines around 80 chars.

Finally update the documentation example with nit-picky things.