fixing the double ORDER BY
Rails 3.1 support for postgresql
Naive attempt to support ARel 2.2
The most important change works for all adapters: ARel now passes a TreeManager instead of the parsed SQL to adapters; This was handled by calling #to_sql on the manager (if the object actually responds to that) deep inside #substitute_parameters, which should cover all types of statements. Also, the global Arel::Visitors::VISITORS is deprecated, and instead each adapter should respond to :visitor_for returning an appropriate visitor. The MySQL adapter was changed to do that, but other adapters are still using the deprecated API.
Another fix to fetching indexes
up to ten columns in a multi-column index. This is wrong, because Postgres supports up to 32 columns in an index, and this may change. Ideally, I'll rewrite this logic completely based on postgresql_adapter in active record.
Quick fix for column order when fetching indexes
…implications. See http://www.postgresql.org/docs/9.0/static/indexes-multicolumn.html This fixes the issue where the Postgres adapter would ignore the column order when getting an index.
Include index length information for MySQL on connection#indexes
Added bindings support