This makes it easier to see what the documentation refers to.

It also means that we are not doing unnecessary work for delegations
that have no args / splats / block / etc.

This doesn't change the exernal behavior, but it moves some code around
to where I think it properly belongs.

This method explicitly loads the records and then returns `self`.

Rather than deciding between "do I want an array or a relation?",
most people are actually asking themselves "do I want to eager load
or lazy load?" Therefore, this method provides a way to explicitly
eager-load without having to switch from a `Relation` to an array.

Example:

    @posts = Post.where(published: true).load

This reverts commit 3803fcce.

Conflicts:
	activerecord/CHANGELOG.md

It will be deprecated only in 4.0, and removed properly in 4.1.

has_secure_password should not raise a 'digest missing' error if the calling class has specified for validations to be skipped.

Change AR's CHANGELOG, because it is related to e35c67ae

[ci skip]

The use_schema_cache_dump configuration moved to ActiveRecord.

Extract dependency check logic that raises ArgumentError in case of an
invalid :dependent option given to an association.

Closes #7054

Move the logic for validation check to the same method, and cache
dependent option in a variable to reuse inside the dependency
configuration methods instead of relying on the options hash.

Restoring documentation for env_config

Updated scaffold_controller generator docs #7146

It was just a copy of the controller generator documentation which was
misleading.  It doesn't accept arguments for views.  This seems more
descriptive as well.

Respect 80 char limit. #7147

Made a nicer paragraph #7147

Follow code conventions in metal/live

https://www.owasp.org/index.php/XSS_%28Cross_Site_Scripting%29_Prevention_Cheat_Sheet#RULE_.231_-_HTML_Escape_Before_Inserting_Untrusted_Data_into_HTML_Element_Content
Closes #7215

has_secure_password should not raise a 'digest missing' error if the calling class has specified for validations to be skipped.

small fix typo in collection proxy

Make ActiveSupport::Inflector locale aware and multilingual

AR::Relation#order: make new order prepend old one.

    User.order("name asc").order("created_at desc")
    # SELECT * FROM users ORDER BY created_at desc, name asc

This also affects order defined in `default_scope` or any kind of associations.

The Inflector is currently not very supportive of internationalized
websites. If a user wants to singularize and/or pluralize words based on
any locale other than English, they must define each case in locale
files. Rather than create large locale files with mappings between
singular and plural words, why not allow the Inflector to accept a
locale?

This patch makes ActiveSupport::Inflector locale aware and uses `:en`` unless
otherwise specified. Users will still be provided a list of English (:en)
inflections, but they may additionally define inflection rules for other
locales. Each list is kept separately and permanently. There is no reason to
limit users to one list of inflections:

    ActiveSupport::Inflector.inflections(:es) do |inflect|
      inflect.plural(/$/, 's')
      inflect.plural(/([^aeéiou])$/i, '\1es')
      inflect.plural(/([aeiou]s)$/i, '\1')
      inflect.plural(/z$/i, 'ces')
      inflect.plural(/á([sn])$/i, 'a\1es')
      inflect.plural(/é([sn])$/i, 'e\1es')
      inflect.plural(/í([sn])$/i, 'i\1es')
      inflect.plural(/ó([sn])$/i, 'o\1es')
      inflect.plural(/ú([sn])$/i, 'u\1es')

      inflect.singular(/s$/, '')
      inflect.singular(/es$/, '')

      inflect.irregular('el', 'los')
    end

    'ley'.pluralize(:es)   # => "leyes"
    'ley'.pluralize(:en)   # => "leys"
    'avión'.pluralize(:es) # => "aviones"
    'avión'.pluralize(:en) # => "avións"

A multilingual Inflector should be of use to anybody that is tasked with
internationalizing their Rails application.
Signed-off-by: NDavid Celis <david@davidcelis.com>

Fix nodoc in metal/live [ci skip]

fix typo in metal/live [ci skip]

update_column was suggested as replacement of update_attribute at the
last release of 3-2-stable, so deprecating it now will confuse the
users.

class_attribute is a building block and using define_method
can be much slower for such basic method definitions.

This reverts commit d59208d7.

Refactor ActionDispatch::Http::Cache::Response#cache_control_headers