Merged zzzeek/alembic into master
Ensure a commit is followed by a GO
Merged in dharland/alembic/patch-mssql-final-go (pull request #13)

MSSQL Batch generator should ensure a COMMIT is followed by the batch separator
- 0.6.2
- changelog for pullreq 13
- test adjustments to account for SQLAlchemy pullreq #7, MSSQL DROP INDEX syntax
- Added new argument ``mssql_drop_foreign_key`` to
:meth:`.Operations.drop_column`.  Like ``mssql_drop_default``
and ``mssql_drop_check``, will do an inline lookup for a
single foreign key which applies to this column, and drop it.
For a column with more than one FK, you'd still need to explicitly
use :meth:`.Operations.drop_constraint` given the name,
even though only MSSQL has this limitation in the first place.
- Fixed an issue with unique constraint autogenerate detection where
a named ``UniqueConstraint`` on both sides with column changes would
render with the "add" operation before the "drop", requiring the
user to reverse the order manually.
- reorganize the index/unique autogenerate test into individual test cases;
ideally the whole test suite would be broken out like this for those big
tests
fix incorrect var for log message
Just a space wrapping `...`.

This eases, for example, selecting the path when the text us double clicked on a console.
Merged in s0undt3ch/alembic (pull request #14)

Just a space wrapping `...`
since msg() right-trims, move the space to the subsequent message
- repair the autogen index test which apparently wasn't running for Postgresql
due to a hardcoded sqlite_db()
- get autogen index test cleaned up, working on Postgresql and MySQL
- rework the autogen index/unique constraint logic to consider both sets of
objects together, and work up all new rules for deduping, comparison.
Add new rules specific to MySQL and SQLite and expand the flexibility surrounding
the "dupe unique index/unique constraint" thing to work around MySQL doing it
in both directions, handles #157
- add a lot more tests and try to emphasize no false positives
- more for #157:
- the ``op.create_table()`` directive will be auto-generated with
  the ``UniqueConstraint`` objects inline, but will not double them
  up with a separate ``create_unique_constraint()`` call, which may
  have been occurring.  Indexes still get rendered as distinct
  ``op.create_index()`` calls even when the corresponding table was
  created in the same script.
- the inline ``UniqueConstraint`` within ``op.create_table()`` includes
  all the options like ``deferrable``, ``initially``, etc.  Previously
  these weren't rendering.
- fixed the index tests to make sure the connection closes after each test
- _render_unique_constraint() and _add_unique_constraint() both call into
a common function now
- call _alembic_autogenerate_prefix within the add_index/drop_index renders
- Fixed bug in the not-internally-used :meth:`.ScriptDirectory.get_base`
method which would fail if called on an empty versions directory.
- move out "render" types of tests into new test_autogen_render
- clean out test_autogenerate
- start pinning some tests to 0.9, don't need to pin to 0.7 anymore
- Autogenerate for ``op.create_table()`` will not include a
  ``PrimaryKeyConstraint()`` that has no columns.
- don't need a full string test for boolean/check constraint autogen
- 0.6.2 release
try out paramlinks
0.1.1
up