The current example

    add_index :person_articles, :article, unique: true

Does not work, the `:article` column does not exist as it will be
a join table (based on the prior example) so should use :article_id

The documentation seems to suggest that it will allow an article to
be added only once to a person via the join table, what actually
occurs is that it only allows the article to be added to one person,
at which point it should be a `belongs_to` association.

Also changed the new example to use readings based on the prior example

Fix wrong timezone mapping for Switzerland (no deprecation warn) [22233]

Remove a blank line from a template for plugin `routes.rb`

Add schema dumping support for PostgreSQL geometric data types

Not passing `native_database_types` to `TableDefinition`

Add text template for source code

Since they are nodoc there is no need to be protected.

We are already filtering the keys in the assign_headers_to_message
method so we can just update the filter.

Refactor ActionMailer::Base

Move the desc one level up

Remove valgrind note about linux only support

Update the valgrind debugging documentation to remove the notes about being
linux only as 3.11.0[1] introduces preliminary support for Mac OSX 10.11 (El
Capitan).

[1]: http://valgrind.org/docs/manual/dist.news.html

don't package test files in plugin gemspec

`set_field_encoding` is only needed for `MysqlAdapter`

Not needed for `Mysql2Adapter` and `AbstractMysqlAdapter`.

This reverts commit 65a61ab7, reversing
changes made to 14314ca1.

This PR broke the build

Update and fix forbidden attributes test issues caused by AC::Parameters change

Test if each_object(singleton_class) works, since JRuby added it.

Fix improper value types used to instantiate a Template in AV::NullResol...

ActionMailer::Base can unregister interceptor(s).

Clearer comment and variable name on IP spoofing

As was pointed out by #17128, our blacklist of mutation methods was
non-exhaustive (and would need to be kept up to date with each new
version of Ruby). Now that `Relation` includes `Enumerable`, the number
of methods that we actually need to delegate are pretty small. As such,
we can change to explicitly delegating the few non-mutation related
methods that `Array` has which aren't on `Enumerable`

Fixes #22376.

JRuby 9.0.5.0 will support ObjectSpace.each_object against a
class's singleton class, since that's essentially just walking an
internal subclasses structure we already maintain. This test was
too narrow, requiring that each_object support an arbitrary class
but only actually needing it to work against a class's singleton.

This improves performance of Class.descendants by nearly two orders
of magnitude when run against JRuby 9.0.5.0:

```ruby
5.times { puts Benchmark.measure { 100_000.times { Numeric.descendants } } }
```

Before:

```
 11.510000   0.140000  11.650000 ( 10.082384)
  9.990000   0.020000  10.010000 (  9.931233)
 10.520000   0.040000  10.560000 ( 10.502978)
 10.290000   0.030000  10.320000 ( 10.276027)
 10.000000   0.030000  10.030000 (  9.942429)
```

After:

```
  1.380000   0.040000   1.420000 (  0.365850)
  0.210000   0.000000   0.210000 (  0.149574)
  0.180000   0.020000   0.200000 (  0.141094)
  0.140000   0.000000   0.140000 (  0.140634)
  0.190000   0.010000   0.200000 (  0.147962)
```

Simplify `RailsGuides::Generator#select_only` a bit

[ci skip] Add `Translating Rails Guides` to contributing_to_ruby_on_r…

Fix race condition testing for job execution order

On most filesystems file ctime is limited to 1 second granularity, which means that on
faster computers multiple simple jobs (for instance dummy TestJob) can finish within the
same second.

The execution order test in ActiveJob integration tests relies on multiple TestJobs
writing files then comparing the ctime. As a result integration tests would sometimes
fail as the ctime of the files written by these TestJobs could have coincidental ctimes
making the comparison for job order fail.

This commit adds a far more precise execution time (to the extent that the Ruby Time
class allows) to the file created by TestJob, and updates the execution order assertion
to use it, removing the race condition.

Docrails is private now (6cb1b672),
anyone who does not have access right to docrails can't read
"Translating Rails Guides" in wiki of docrails.
To prevent someone from giving up to translate, publish them on Rails Guide.

The main goal is to improve readability, but as a side effect this commit makes the method a bit faster.

Erroneously removed in 58910dc7.

The stubbing was a regression test to ensure `time_zone_select` wasn't implemented with
`grep`. Rename the test and add a comment to make the intent clearer.

We never touch the index, so don't bother.

When calling `test_time_zone_select_with_priority_zones_as_regexp` it would
define `=~` on the fake zones, but it would never be cleaned up because of
the zone cache.

Nuke it so `test_time_zone_select_with_priority_zones_as_regexp_using_grep_finds_no_zones`
accidentally find any zones because of `=~` being implemented.