Changed update to use prepared statements

Raising an ActiveRecordError when one tries to use touch on a new record object

object that has not yet been persisted. This behavior follows the
precedent set by update_columns.

This reverts commit 046e27a7.
Check https://github.com/rails/rails/pull/8815#issuecomment-14026122 for
details.

AS JSON encoder: remove monkey patch of Array

Added `ActiveSupport::TimeWithZone#to_r` for `Time#at` compatibility.

Closes #9404

Taking the wise advice of @carlosantoniodasilva

don't apply invalid ordering when preloading hmt associations.

closes #8663.

When preloading a hmt association there two possible scenarios:

1.) preload with 2 queries: first hm association, then hmt with id IN ()
2.) preload with join: hmt association is loaded with a join on the hm association

The bug was happening in scenario 1.) with a normal order clause on the hmt association.
The ordering was also applied when loading the hm association, which resulted in the error.

This patch only applies the ordering the the hm-relation if we are performing a join (2).
Otherwise the order will only appear in the second query (1).

update the example for `after_commit` in the guides.

This is a follow up to #9356.

Remove `--builder` option from `rails` command

Ability to use a custom builder by passing `--builder` (or `-b`) has
been removed. Consider using application template instead. See this
guide for more detail:
http://guides.rubyonrails.org/rails_application_templates.html

remove config.auto_explain_threshold_in_seconds

We discussed that the auto explain feature is rarely used.
This PR removes only the automatic explain. You can still display
the explain output for any given relation using `ActiveRecord::Relation#explain`.

As a side-effect this should also fix the connection problem during
asset compilation (#9385). The auto explain initializer in the `ActiveRecord::Railtie`
forced a connection.

Updated doc to clarify about update_all and delete_all

[ci skip]

Point to the Protected Attributes gem to those who want a smoothly
upgrade path before to change to use Strong Parameters.

[ci skip]

delete_all will call callbacks if depdent option is specified as
:destroy. This behavior is not very clear from the documetation and
hence issue #7832 was raised.

closes #7832

The connection url parssing don't accept the socket option

We should only type cast when we need to use.

Related to 4b005fb3

Revert "move config.assets.precompile into config/application.rb"

This reverts commit 304f4d4c.

As it turns out everything should behave as it did and we don't
need to move this configuration option.

multiple actions for :on option with `after_commit` and `after_rollback`

test case to prevent duplicated associations with custom PK.

closes #9201

Address failure test_rename_column_with_multi_column_index with Oracle

because of Oracle database index length spec.

also rename the test-case class inside columns_test.rb

Reason: on a second thought, minitest prints a seed as run option
regardless of the test order, and it actually calls srand, so
albeit it might be misleading I believe, it is the way it is and
should be left that way.

This reverts commit c15862ae.