Documentation ActiveRecord Attributes API code fix

add application_job.rb to template of mountable engine

Fix formatting of ActiveRecord PostgreSQL guide.

Add basic support for access control headers to ActionDispatch::Static

Only prepend a single module when defining deprecation wrappers.

I could not find any reason why each method got its own prepended
module here, and all tests appear to pass with my change.

The rdoc parser seems to trip on the `private def` construct.
Public methods following a method defined with `private def` are not
visible inside the module docs but are appended to the top-most module.

For example the method `ActiveRecord::QueryMethods#distinct` was listed
under `ActiveRecord#distinct`.

/cc @sgrif

[ci skip]

This class is only used internally. We should keep it out of public
documentation. This patch adds nodoc for
`ActiveRecord::Associations::Builder` and everything nested within.

This error is raised in certain situations when eager loading
polymorphic associations. We even mention it in our docs. It should be
included in our API.

Conflicts:
	activerecord/lib/active_record/associations.rb

Also unify the format of code example output. Only use `# =>` if the
actual return value is described. Otherwise simply use `#`.

Conflicts:
	activerecord/lib/active_record/relation/query_methods.rb

Closes #21563.

The `name` argument of `add_references` was both used to generate the
column name `<name>_id` and as the target table for the foreign key
`name.pluralize`.

It's primary purpose is to define the column name. In cases where the
`to_table` of the foreign key is different than the column name we
should be able to specify it individually.

Move the methods for schema dumping into `{mysql,postgresql}/schema_dumper.rb`

Allow mysql and mysql2 tests run by database user with password

ActionMailer https on URL with force_ssl = true

Current master branch includes many schema dumping improvements.
It extract these features to the appropriate files.

Remove deprecated pg_dump -i flag

Move schema definiton classes into the appropriate files

Change `Journey::Route#verb` to return string instead of regexp.

* Revises the name of Rails components (they have a space).

* Uniform word wrap at column 80..

* Uniform punctuation, according to our guidelines.

* Minor edits of details seen in passing.

do not generate manifest.js in plugins

[ci skip] Fix typo in deep_dup docs

Since the plugin generator do not generate assets, I think manifest.js also that it unnecessary.

Current master branch includes many schema creation improvements in
MySQL. It extract these features to the appropriate file.

Current master branch includes many schema definition improvements in
MySQL. It extract these features to the appropriate file.

Make AR#increment! and #decrement! concurrency-safe

Allow multiple `root` routes in same scope level

When an application has multiple root entries with different
constraints, the current solution is to use `get '/'`. Example:

**Currently I have to do:**
```ruby
get '/', to: 'portfolio#show', constraints: ->(req) { Hostname.portfolio_site?(req.host) }
get '/', to: 'blog#show',      constraints: ->(req) { Hostname.blog_site?(req.host) }
root 'landing#show'
```

**But I would like to do:**
```ruby
root 'portfolio#show', constraints: ->(req) { Hostname.portfolio_site?(req.host) }
root 'blog#show',      constraints: ->(req) { Hostname.blog_site?(req.host) }
root 'landing#show'
```

Other URL matchers such as `get`, `post`, etc, already allows this, so I
think it's fair that `root` also allow it since it's just a shortcut for
a `get` internally.

Fix cache fetch instrumentation