Remove sqlite specific`supports_autoincrement?` which always defaults to true
fixed a doc bug in the CHANGELOG.md s/does no longer depend on/no longer depends on/
Use ActiveRecord::Base#update! instead of #update_attributes!
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.
Assert presence of "frozen" in error message, not the full MRI message.

Related to all the other issues regarding message independent assertions
to make Rails compatible with other Ruby implementations other than MRI.

The best way here would be to have a specific error raised when modifying
frozen objects, like FrozenObjectError or something. But since Ruby
doesn't provide such a thing, we must limit the assertion to the lowest
common denominator, which is word "frozen".
Allow methods arity below -1 in assert_responds.

Every method from MRI's core classes is written in C. This means
Method#arity always returns -1 for methods with a variable number of
arguments. This is not the case with Rubinius, where, for example
Array#slice! is implemented in Ruby and has arity -2, since is
defined as def slice!(start, length = undefined)
Fixes #11773 when using includes combined with select, the select statement was overwritten.
Fix wrong variable name used in the select_day method documentation

The variable name created in the example is `my_date`, the methods  were using `my_time` instead.
Keep code consistent with previous code blocks.

[ci skip]
decouple the `join_constraints` method from the parent pointer
pull parent and alias tacker from the nodes.

For now, we'll set the tables on the nodes manually.
remove dead code / make duplicate code more obvious
cache the primary key / typcast lookup on the stack
belongs_to can be treated the same way as has_one
reflections know if they are collections, so ask

We don't need to poke at the macro to figure out if we should look for a
cached record or not
fix variable name. we're constructing a model, not an association
we always have a reflection and it is on the node
extract conditional to the caller
we always have a model now
push up the loaded target checking