According to the guide, ":save" value for the "on:" validation helper
was available like below

    validates :name, presence: true, on: :save

but this was never available according to the implementation of the
valid? method, which is below

    # Runs all the validations within the specified context. Returns
+true+ if
    # no errors are found, +false+ otherwise.
    #
    # If the argument is +false+ (default is +nil+), the context is set
to <tt>:create</tt> if
    # <tt>new_record?</tt> is +true+, and to <tt>:update</tt> if it is
not.
    #
    # Validations with no <tt>:on</tt> option will run no matter the
context. Validations with
    # some <tt>:on</tt> option will only run in the specified context.
    def valid?(context = nil)
      context ||= (new_record? ? :create : :update)
      output = super(context)
      errors.empty? && output
    end

So the documentation was always wrong since the PR proposed by
@neerajdotname  ( #10287 ) was rejected.

Add Time#to_s(:iso8601) for easy conversion of times to the iso8601 format for easy Javascript date parsing

grab executable from rubygems

This reverts commit 10259c3e.

reason: this causes rake test_mysql and test_mysql2 fail

Changed stylesheet load order in the stylesheet manifest generator.

Cleanup of class_name

fix order dependent test related to migration

make test order independent by resetting timezone

reset default timezone and make test order independent

make test not depend on order

Don't think class name is needed as by default belongs_to :select will be linked to Select class.

`NestedThroughAssociationsTest` adds records to `member_details` table.
When test performs `@member_details[0]` then the order of record
is not guaranteed. Hence it is best to start with a clean slate by
deleting unwanted records.

fix order dependent test

If the order in which tests are executed is changed then test fails.
This commit ensures that all migrations are run before ensuring that
there are no pending migration.

`ReflectionTest` uses column information in tests and those tests break
if tests are run in random order.

Minor refactor - Uses Enumerable#to_a instead of iterate and add to an array

array

Update Rails 3.2.x guide link [ci skip]

To share a certain logic across other examples, let's add a sample SQL
code generated by the given Ruby code

Excluding action_view/vendor in API[ci skip]

sorry @robin850.
Thanks @fxn

These folder not exists in system

This reverts commit 700c6c65.

Bot the `sqlite3` and `sqlite3-ruby` gems exist.
https://rubygems.org/gems/sqlite3
https://rubygems.org/gems/sqlite3-ruby

In fact, they both point to the same github repository.
https://github.com/luislavena/sqlite3-ruby

However, the last one hasn't been released since 2011, while the first
one keeps getting regular releases.

As done here d7fc97d3