Comment 7 for bug 1519171

Hi Ann -

can you please provide a code example, or at least what backend you're referring to? Alembic type comparison rules are necessarily affected by backend since the current DB type is first the result of SQLAlchemy creating that type previously, and then round-tripping through reflection from that backend. Also comparison of types is off by default unless a value is specified for the "compare_type" flag is set on the environment.

For the typical targets of MySQL and SQLite the "BigInteger" type should be generating a type of BIGINT which would compare differently upon reflection to INTEGER. A real bug report at https://bitbucket.org/zzzeek/alembic would be most helpful thanks!