That is happened with `distinct`, and that is not only happened on MyS
L, but also on PostgreSQL, SQL Server, and Oracle.

[ci skip]

In e8546aba, the Getting Started guide
was updated to reflect the removal of CoffeeScript stubs being generated
by the controller generator. However, the comment above the table of
generated files wasn't updated, so it incorrectly remained "This creates
five files and one empty directory". This fixes it to now say "This
creates four files and one empty directory".

This reverts commit 6b69ae51, reversing
changes made to 84bd9ada.

Reason: We already use "happen" a lots for callbacks and validations.

https://github.com/rails/rails/pull/35324#issuecomment-465096483

[ci skip]

Change 'happen' to a more technical term

[ci skip]

This reverts commit b46601b5, reversing
changes made to 4e6737f1.

This reverts commit 141f50ef, reversing
changes made to 317efa5c.

Reason: `add_foreign_key` and `remove_foreign_key` are implemented at
#35212.

[ci skip]

Swap `#users` jQuery selector to correct position and prevent the escaping of HTML.

[ci skip]

Changes the Getting Started guide explanation for
`ActionController::MissingExactTemplate` error, to reflect the current message.

Follow up for #29286, #35148

[ci skip]

During the development of #33145, I have named a few concepts in the
code as `whitelisted`. We decided to stay away from the term and I
adjusted most of the code afterwards, but here are the cases I forgot to
change.

I also found a case in the API guide that we could have cleaned up as
well.

[ci skip]

[ci skip]

Follow-up to #35055.

and suggest a workaround

Don't upsize images smaller than the specified dimensions.

That would allow us to test broadcasting made with channel, e.g.:

```ruby
class ChatRelayJob < ApplicationJob
  def perform_later(room, msg)
    ChatChannel.broadcast_to room, message: msg
  end
end
```

To test this functionality we need to know the underlying stream name
(to use `assert_broadcasts`), which relies on `channel_name`.

We had to use the following code:

```ruby
assert_broadcasts(ChatChannel.broadcasting_for([ChatChannel.channel_name, room]), 1) do
  ChatRelayJob.perform_now
end
```

The problem with this approach is that we use _internal_ API (we shouldn't care about `channel_name` prefix
in our code).

With this commit we could re-write the test as following:

```ruby
 assert_broadcasts(ChatChannel.broadcasting_for(room), 1) do
   ChatRelayJob.perform_now
 end
```

Since we use [workspaces](https://yarnpkg.com/lang/en/docs/workspaces/)
`yarn install` from the root should install all the javascript dependencies.