diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2016-10-20 17:47:19 -0400 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2016-10-20 17:47:19 -0400 |
| commit | e9175a37ce0b0b0e87ad728c8a6a10bed100065b (patch) | |
| tree | 0db022ca9d340411f4e4d299ad002119d01f14a2 /migrate/changeset/databases/postgres.py | |
| parent | d58469a6ae19f6a2db0465785b6de6c6dfc23c93 (diff) | |
| download | sqlalchemy-migrate-e9175a37ce0b0b0e87ad728c8a6a10bed100065b.tar.gz | |
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
Diffstat (limited to 'migrate/changeset/databases/postgres.py')
0 files changed, 0 insertions, 0 deletions