Merged zzzeek/sqlalchemy into master
Support mssql_clustered option in mssql dialect for both Table and PrimaryKeyConstraint
Fix a typo in the relationship docs

The text refers to ``boston_addresses``, while the code sample uses
``addresses``.
Remove support for mssql_clustered on Table
Support mssql_clustered option on UniqueConstraint (plus docs and test)
Bug Fix: Stop generating bad sql if an empty UniqueConstraint() is given
Merge branch 'patch-msql-pkc-clustered' of bitbucket.org:dharland/sqlalchemy into m
- changelog for pullreq:11
- be specific about version 0.9.2
credit to Derek Harland
- implement kwarg validation and type system for dialect-specific
arguments; [ticket:2866]
- add dialect specific kwarg functionality to ForeignKeyConstraint, ForeignKey
akiban-> foundationdb
- some test fixes
- clean up some shenanigans in reflection
- alter behavior such that dialect_kwargs is still immutable, but
now represents exactly the kwargs that were passed, and not the defaults.
the defaults are still in dialect_options.  This allows repr() schemes such as that
of alembic to not need to look through and compare for defaults.
Merge pull request #59 from wichert/doc-relationship-typo

Fix a typo in the relationship docs
fix typo
Remove uneeded import from code example

This had me reread the code twice to see if I missed why the import was
present.
- ensure ordering is fully maintained, [ticket:2914]
- repair signature for base get_unique_constraints() method
- test_autoincrement_col still needs reflection overall
- simplify the mechanics of PrimaryKeyConstraint with regards to reflection;
reflection now updates the PKC in place.
- support the use case of the empty PrimaryKeyConstraint in order to specify
constraint options; the columns marked as primary_key=True will now be gathered
into the columns collection, rather than being ignored. [ticket:2910]
- add validation such that column specification should only take place
in the PrimaryKeyConstraint directly, or by using primary_key=True flags;
if both are present, they have to match exactly, otherwise the condition is
assumed to be ambiguous, and a warning is emitted; the old behavior of
using the PKC columns only is maintained.
- further refine this so that the ordering of columns is maintained as
sent to the primary key constraint; existing tests in the PG dialect
confirm this.