Fixed typo in documentation
Fixed return strings in documentation
Directory name in RUNNING_UNIT_TESTS.rdoc [ci skip]
[ci skip] Add explanation on Rack::Sendfile and fix serve static files setting.
Merge pull request #12440 from arunagw/minor-fix-running-unit-test-file

Directory name in RUNNING_UNIT_TESTS.rdoc [ci skip]
Merge pull request #12437 from websiteswithclass/master

Fixed typo in documentation
add regression test for set_inverse_instance on add_to_target
wrap logging around the actual query call itself.

This is to be consistent with the way the mysql2 adapter times queries
stop adding singleton methods to the PG connection
stop adding singleton methods to the mysql2 adapter
stop adding singleton methods to the SQLite3 connection
rm LogIntercepter
prepare the statement inside the begin / rescue block
log every sql statement, even when they error
log the statement name along with the SQL
instrumenter can't be cached because the app could be called from
different threads.
Just change ENV and restore it afterwards.

Stubbing ENV[] is not safe outside MRI. At some point after the
stubbing has occurred a backtrace is printed to the ActiveSupport
warning log: there Rubinius accesses ENV['RBX_NOCOLOR'] to determine
if it should print the backtrace with colors or not, causing the
stub to fail. Other implementations might access ENV in a different
way too, we just can't predict it.
The only thing we can do here is to actually set the ENV with what
we want and restore it afterwards.
this code is never used, remove it
remove more dead code

We control the inputs to `construct`, so the wrong type shouldn't be
passed in ever.
extract the string handling part to a method.

We know the structure passed in to the `construct` method will be a
hash, so we don't need to test it all the time.  The key value will be a
symbol or string, so handle it with the special method