support for partial/filtered indices on SQL Server 2008
Rails 4 compatible UUID Support
Merge pull request #327 from romuloceccon/filtered_indices_support

Add support for SQL Server's filtered indices
Fixed selecting DISTINCT rows from a table when ordering by a column that is not
part of the SELECT list where the join creates at least one extra row.

While previously the test suite combined with Rails 4.0.0 looked like it worked, the
constructed SQL would return incorrect values for
FinderTest#test_find_with_order_on_included_associations_with_construct_finder_sql_for_association_limiting_and_is_distinct.
By using a GROUP BY and MAX()/MIN() in the ORDER BY with no DISTINCT call, the order
of the returned rows was not necessarily correct.

With Rails 4.0.1, a related bug was fixed that introduces a new method,
columns_for_distinct. Unfortunately by adding the columns from the ORDER BY clause
to the SELECT list, the DISTINCT nature of the queries was altered. This combined
with a test limiting the results to only 2 records, exposed the bug.

From testing various SQL constructs to solve the issue, I ended up determining that
to properly return a single value from the related table used in the ORDER BY, a
query with a subquery utilizing ROW_NUMBER() and DENSE_RANK() was needed. The
ROW_NUMBER() was partitioned over the originally requested columns, and then the
outer query would filter the results to just the first row of each partition.
DENSE_RANK() was used to generate a proper ordering of the partitions in relation
to each other.

In the process I also determined that extra code, plus an extra test, was necessary
to ensure that when such a construct was generated using both a limit and offset,
that the results would be correct also.

See https://github.com/rails-sqlserver/activerecord-sqlserver-adapter/issues/306
for further discussion, plus example queries and results.
Merge pull request #329 from veracross/fix-distinct-plus-limit

Fix for Issue #306 - DISTINCT + TOP + ORDER BY Associated Table
Merge pull request #328 from agios/uuid

Rails 4 compatible UUID Support
fix schema_dumper test for UUID
only style changes
moved SQLServerColumn and Activerecord::Base to their own files
moved SQLServerAdapter back and split up the connect method
added pry
better handling of updates with identiy column.  Room for improvement.
The tests now run with rails 4.1.0

removing duplicate standard_dump
Fixed bind type casting to re-set the casted value back to the bind, fixed bind parameter tests to work with SQL server
Added the :authors fixture to AdapterTest to fix a failure in test_select_methods_passing_a_association_relation
Type casting is now happening, so the test regex needs to be updated
The test test_to_sql_on_eager_join was seeing slightly different result in that the SQL was embedded in a call to sp_executesql, which seems ok to me
Rails 4.1 seems to use strings for database config keys nows
Fix how we are checking bind tests, can't use coerce since the test methods are defined in an if block
Fixed tests in rails/activerecord/test/cases/connection_adapters/connection_handler_test.rb by setting the RAILS_ENV to 'default_env'