adapter, fixed from #16057 [ci skip]

[ci skip] /sqlite/i --> SQLite

[ci skip] add guide for ActiveModel::Naming

Prior to this commit shallow resources would only generate paths for
non-direct children (with a nested depth greater than 1).

Take the following routes file.

    resources :blogs do
      resources :posts, shallow: true do
        resources :comments do
          resources :tags
        end
      end
    end

This would generate shallow paths for `tags` nested under `posts`,
e.g `/posts/:id/tags/`, however it would not generate shallow paths
for `comments` nested under `posts`, e.g `/posts/:id/comments/new`.

This commit changes the behaviour of the route mapper so that it
generate paths for direct children of shallow resources, for example
if you take the previous routes file, this will now generate
shallow paths for `comments` nested under `posts`, .e.g
`posts/:id/comments/new`.

This was the behaviour in Rails `4.0.4` however this was broken in
@jcoglan's fix for another routes related issue[1].

This also fixes an issue[2] reported by @smdern.

[1] https://github.com/rails/rails/commit/d0e5963
[2] https://github.com/rails/rails/issues/15783

active_record: Type cast booleans and durations for string columns.

[ci skip] link directly to ActionMailer Previews documentation

[ci skip] Concludes changelog links in the bottom.

This way when we do next release notes, this would be easier to copy and change.

This reverts commit a0309775.

This needs more work before it would work correctly on master.

Fixed issue with ActiveRecord serialize object as JSON

Conflicts:
	activerecord/CHANGELOG.md
	activerecord/lib/active_record/attribute_methods/serialization.rb

If our connection is explicitly non-strict, tell MySQL

One of the author fixture we have ("david") references an author address by ID.
Since we disable FK checks when inserting fixtures, this is all fine until we
try to update it, at which point MySQL would complain about the missing row
referenced by the `author_address_id`.

[Godfrey Chan, Matthew Draper]

We default to making the connection strict, but have historically relied
on the MySQL default when we want it to be non-strict. On some (recent?)
versions of MySQL, new connections default to being strict, so if we've
been told 'strict:false', we're obliged to pass that on.

This fixes a test failure that we've seen turn up on relatively-new
development machines, so we do already have a test covering it.

This reverts commit e84799d9, e31104c1 and e6ca8e2c

Use the type object for quoting PG Ranges

Removed mentions of non-existent methods, also added a mention for
`Date.current`, which is analagous to `Time.current`. Closes #16061.

Add a `required` option to singular associations

In addition to defining the association, a `required` association will
also have its presence validated.

Before:

```ruby
belongs_to :account
validates_presence_of :account
```

After:

```ruby
belongs_to :account, required: true
```

This helps to draw a distinction between types of validations, since
validations on associations are generally for data integrity purposes,
and aren't usually set through form inputs.

Revert "Use a type object for type casting behavior on SQLite3"

Remove symbolized_path_parameters.

Use a type object for type casting behavior on SQLite3

Add `:all` argument to `count` in `reset_counters`

Conflicts:
	activerecord/CHANGELOG.md

Improve token_and_options regex and test

Add arel to the controller template [ci skip]

Add test coverage for the action mailer

[ci skip] /javascript/ -> JavaScript - cover whole app

After find-via-reload, the record is not new

Do not load rails without loading bundler