"Returns true if the specified attribute has been set by the user or by
a database load and is neither nil nor empty?"

Fixes #1613

This is a first implementation, EXPLAIN is highly
dependent on the database and I have made some
compromises.

On one hand, the method allows you to run the most
common EXPLAIN and that's it. If you want EXPLAIN
ANALYZE in PostgreSQL you need to do it by hand.

On the other hand, I've tried to construct a string
as close as possible to the ones built by the
respective shells. The rationale is that IMO the
user should feel at home with the output and
recognize it at first sight. Per database.

I don't know whether this implementation is going
to work well. Let's see whether people like it.

This is to avoid confusing newbies, and to be consistent with the fact
that other options like :foreign_key already allow a symbol or a string.

Preserve SELECT columns on the COUNT for finder_sql when possible

Building the conditions of a nested through association could
potentially modify the conditions of the through and/or source
association.

This is a Bad Thing.

If a record is removed from a has_many :through, all of the join records
relating to that record should also be removed from the through
association's target.

(Previously the records were removed in the database, but only one was
removed from the in-memory target array.)

Fixes #3425.

Fixes creating records in a through association with a polymorphic source
type.

This change reduces churn in the db/development_structure.sql file when using :sql as
active_record.schema_format, and makes comparing diffs much easier.

Test ensures the output SQL-statements are lexically ordered by version.

Removed here 0d0176c4

Postgres: Do not attempt to deallocate a statement if the connection is no longer active.

Use broken YAML that will fail with Syck as well as Psych. Fixes test_broken_yaml_exception in fixtures_test.rb on Ruby 1.8.7.

Cherry-pick from 3-1-stable: b8d46924

Only use LOWER for mysql case insensitive uniqueness check when column has a case sensitive collation.

You can use multiple databases in your tests without disabling transactional fixtures.

An association between two models cannot be made if a relevant key is
unknown, so fail fast rather than generating invalid SQL. Fixes #3207.

This reverts commit ee2be435.

Add tests for prepared statements with multiple schemas in
postgreSQL.