need more checks for alembic_version in autogen

Issue #28 resolved
Michael Bayer
repo owner created an issue

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.

Comments (2)

  1. Michael Bayer reporter
    • If the "alembic_version" table is present in the target metadata, autogenerate will skip this also. Pull request courtesy Dj Gilcrease. fixes #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 #77

    → <<cset 9650ccfb6841>>

  2. Log in to comment