We need to re-order the bind parameters since the AST returned by the
relation will have the where statement as the first bp, which breaks on
PG.

MySQL reports the column name as `"MAX(developer_id)"`. PG will report
it as `"max"`

Add link to API Documentation Guidelines [ci skip]

Link to the "English" section to specify American English be used for the Guides
[ci skip]

It was transitively relying on the vertex model being loaded

In practical terms, this allows serialized columns and tz aware columns
to be used in wheres that go through joins, where they previously would
not behave correctly. Internally, this removes 1/3 of the cases where we
rely on Arel to perform type casting for us.

There were two non-obvious changes required for this. `update_all` on
relation was merging its bind values with arel's in the wrong order.
Additionally, through associations were assuming there would be no bind
parameters in the preloader (presumably because the where would always
be part of a join)

[Melanie Gilman & Sean Griffin]

Remove redundant substitute index when constructing bind values

Remove redundant require of file

This slightly simplifies the code, and reduces the number of times we
need to iterate over the attributes by one.

This file was required inside 'test/validators/namespace/email_validator.rb'
that's already required here. Therefore I removed the redundant required.

[ci skip]

add missing space.[ci skip]

[ci skip] Fix line break on asset pipeline guide 

fixes this :

![http://i.imgur.com/86scI3a.png](http://i.imgur.com/86scI3a.png))

Skip setting sequence on a table create if the value is 0 since it will start the first value at 1 anyway.
This fixes the PG error 'setval: value 0 is out of bounds for sequence vms_id_seq...' encountered when migrating a new DB.

BugzID: 15452,9772,13475,16850

We end up re-ordering them either way when we construct the Arel AST (in order
to deal with rewhere, etc), so we shouldn't bother giving it a number in the
first place beforehand.

Nothing is directly using the columns for the default values anymore.
This step helps us get closer not not mutating the columns hash.

Fixes #17170

Explicit route test class

Merge pull request #17305 from ziggythehamster/activerecord-connectionhandling-RAILS_ENV-without-rails

If Rails is not defined, check ENV["RAILS_ENV"] and ENV["RACK_ENV"] in ActiveRecord::ConnectionHandling

AM README fixes [ci skip]

- Wrapped text in setting defaults section. Also added break, to a sentence.
[ci skip]

We had accidentally gone one power of two too far. In addition, we need
to handle minimum values as well as the maximum.

Fixes #14180
Fixes #17461

* use public_send instead of send to avoid calling private
  methods in form helpers

Treat strings greater than int max value as out of range

Sufficiently large integers cause `find` and `find_by` to raise
`StatementInvalid` instead of `RecordNotFound` or just returning `nil`.
Given that we can't cast to `nil` for `Integer` like we would with junk
data for other types, we raise a `RangeError` instead, and rescue in
places where it would be highly unexpected to get an exception from
casting.

Fixes #17380

Masked authenticity token section, finder options details, misc typos [ci skip]

It is internal use only. This is to avoid conflicting with users' method
names. Fixes #17458

Arel has changed so that `.sum` no longer aliases `SUM(the_column)` to
`sum_id`. This means the type returned by the adapter will be at the key
`"SUM(the_column)"`. Longer term, we should eventually be able to retain
type information from the AR::Base subclasses used in joined queries

Fixes #17455