sqlalchemy-migrate/migrate/changeset
Mike Bayer e9175a37ce Set autoincrement to False when modifying to non-Integer datatype
Starting in SQLAlchemy 1.1, the rules for when "autoincrement=True"
may be set on a column are more strict.  The migrate tests are
testing the alteration of a column from Integer to String
and then regenerating; this means we need to set autoincrement
to False as well.   A related issue in SQLAlchemy 1.1 is
also being fixed (see https://bitbucket.org/zzzeek/sqlalchemy/issues/3835/),
however this fix is not needed in order for the tests to pass here.

Change-Id: Ibd3a75fff13312411df87e17b6e5764865d69728
2016-10-20 17:47:19 -04:00
..
databases Fix ibmdb2 index name handling 2015-03-16 15:21:03 +00:00
__init__.py Update tests and reqs for SQLA 1.0 2015-07-01 20:01:52 +00:00
ansisql.py Port to Python3 2014-04-09 17:32:52 +02:00
constraint.py drop SQLAlchemy < 0.6 compatibility code 2011-10-28 10:59:10 +02:00
schema.py Set autoincrement to False when modifying to non-Integer datatype 2016-10-20 17:47:19 -04:00
util.py Update tests and reqs for SQLA 1.0 2015-07-01 20:01:52 +00:00