Using public send instead of send for the PerThreadRegistry module.
Prevents you from accidentally calling a protected method.
Merge pull request #10165 from wangjohn/public_send_for_instance

Using public send instead of send for the PerThreadRegistry module.
Searching for rails executable correctly

 * Current logic of finding Rails executable in parent directory is
   not returning full path of executable if it is found in one of the
   parent directories
 * To compensate for this, we have to call exec_app_rails recursively
   until the executable is found or we cant do 'chdir' anymore
 * This solution finds the correct executable path from parent
   directory(s) recursively
Merge pull request #10157 from prathamesh-sonpatki/app_loader

Searching for rails executable correctly
code review of 22e5ab3
Revert "Merge pull request #10158 from steveklabnik/issue_10125"

This reverts commit fa3ef8e82ab2f96cf15ef9bc885b2468fad77621, reversing
changes made to e0af93dd3a5eeee2e2a67b05f34afb66cc80c00b.

Reason: Routes, Active Record and the rendering stack should not depend
on the default locale
While merging relations preserve context for joins

Fixes #3002. Also see #5494.

```
class Comment < ActiveRecord::Base
  belongs_to :post
end

class Author < ActiveRecord::Base
  has_many :posts
end

class Post < ActiveRecord::Base
  belongs_to :author
  has_many :comments
end
```

`Comment.joins(:post).merge(Post.joins(:author).merge(Author.where(:name => "Joe Blogs"))).all` would
fail with `ActiveRecord::ConfigurationError: Association named 'author' was not found on Comment`.

It is failing because `all` is being called on relation which looks like this after all the merging:
`{:joins=>[:post, :author], :where=>[#<Arel::Nodes::Equality: ....}`. In this relation all the context that
`Post` was joined with `Author` is lost and hence the error that `author` was not found on `Comment`.

Ths solution is to build JoinAssociation when two relations with join information are being merged. And later
while building the arel use the  previously built `JoinAssociation` record in `JoinDependency#graft` to
build the right from clause.

Thanks to Jared Armstrong (https://github.com/armstrjare) for most of the work. I ported it to make it
compatible with new code base.
Merge pull request #10164 from neerajdotname/3002-final

While merging relations preserve context for joins
Added statement cache
Revert "Merge pull request #6226 from gnufied/master"

This reverts commit 9bf1a0db4acbbf9e8e6f707250269185224e7efe, reversing
changes made to fed97091b9546d369a240d10b184793d49247dd3.

Conflicts:
	activerecord/test/cases/transaction_callbacks_test.rb

Reason: This fix introduces another issue described at #8937, so we are
reverting it to restore the behavior of 3-2-stable.

We will fix both issues when we come out with a better solution
remove_duplicate_results! should be protected
rdoc for some of the methods in JoinDependency
converge three lines into one
Merge pull request #10168 from neerajdotname/simple_improvements

Simple improvements
Merge pull request #10152 from Noemj/statement_cache

Statement cache

Conflicts:
	activerecord/CHANGELOG.md
Editorial pass over generated Gemfile

* When run with default options, no repeated blank lines
* Every gem has a comment, perhaps a generic one, but a comment nonetheless
* Most comments used to start with "Use", some with "To use" => made consistent
Merge pull request #10170 from rubys/editorial_pass_over_generated_gemfile

Editorial pass over generated Gemfile
Remove warning

warning: `*' interpreted as argument prefix
application loader refactor and test suite complete rewrite
fixes remaining lowercase "rails"