do not create memo objects since we'll just throw them away
combine move_regexp and move_string so we only loop over states once
push move_string in to `move`
Merge branch 'rmc'

* rmc:
  push move_string in to `move`
  combine move_regexp and move_string so we only loop over states once
  do not create memo objects since we'll just throw them away
  only ask if `t` is empty once.
Changed 'so' to 'see'
Allow postgresql enum_test to be run in random order.

Creating and dropping similar tables within the same connection causes postgresql to look up old values in the cache of tables which have already been dropped.
Merge pull request #14560 from abwinkler999/typo-in-RELEASING_RAILS

Changed 'so' to 'see'
Merge pull request #14550 from tgxworld/fix_failing_enum_test_random_order

Allow postgresql enum_test to be run in random order.
cleanup, `reset_pg_session` in range_test.rb

Also do not use transactional fixtures. We drop the type and the
table after every run, so there is nothing for the transaction to clean up.
PostgreSQL, Support for materialized views. [Dave Lee & Yves Senn]

Expand the query used in #table_exists? to include materialized views in the
kinds of relations it searches.
We can conditional define the tests depending on the adapter or
connection.
Merge pull request #14565 from rajcybage/conditional_test_cases

We can conditional define the tests depending on the adapter or connection.
DRY AS::SafeBuffer a bit using existing helper
Fixed small documentation typo

Using `Rails.application.config.cookies_serializer :hybrid` throws an exception, fixed to `=`.
Merge pull request #14568 from alex88/patch-1

Fixed upgrade guide typo
Merge pull request #14529 from rwz/master

ActiveSupport::SafeBuffer#prepend inconsistency
Use asert_deprecated
Revise 'sqlite3:' URL handling for smoother upgrades

Restore the 4.0 behaviour for 'sqlite3:///', but deprecate it. We'll
change to the absolute-path interpretation in 4.2.

The current "correct" spellings for in-memory, relative, and absolute
URLs, respectively, are:

    sqlite3::memory:
    sqlite3:relative/path
    sqlite3:/full/path

Substantially reverses/defers fbb79b517f3127ba620fedd01849f9628b78d6ce.
Uncovered by @guilleiguaran while investigating #14495, though that
sounds like a different issue.
Complete change of `sqlite3:///` path handling

That which was now relative is now absolute.
Move require to actual file

Change to require all active_support/deprecation since that's the actual
entry point for the deprecation methods.