need more checks for alembic_version in autogen

[sqlalchemy-bot]

Migrated issue, originally created by Michael Bayer (@zzzeek)

if meta.reflect() is used to get all tables, then alembic_version is in the given metadata being compared, so need to skip on this end as well as when autogen reads from the DB.

[sqlalchemy-bot]

Changes by Michael Bayer (@zzzeek):

• added labels: autogenerate - detection

[sqlalchemy-bot]

Michael Bayer (@zzzeek) wrote:

• If the "alembic_version" table is present in the target metadata,
  autogenerate will skip this also. Pull request courtesy
  Dj Gilcrease. fixes need more checks for alembic_version in autogen #28
• The :paramref:.EnvironmentContext.configure.version_table
  and :paramref:.EnvironmentContext.configure.version_table_schema
  arguments are now honored during the autogenerate process, such that
  these names will be used as the "skip" names on both the database
  reflection and target metadata sides. fixes hard coded 'alembic_version' in _produce_net_changes of autogenerate.py #77

→ 9650ccf

[sqlalchemy-bot]

Changes by Michael Bayer (@zzzeek):

• changed status to closed