do not rely on reflection applying naming conventions

[sqlalchemy-bot]

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

the naming convention feature added in 735889f068c58f8a278dcfe5bda7496624339026 will require adjustment per SQLAlchemy issue https://bitbucket.org/zzzeek/sqlalchemy/issues/3818/naming-convention-should-not-fire-off-on. Reflection should not be applying naming constraints and Alembic's feature here will need to use some new flag, e.g. apply_naming_conventions. Base this on detection of version 1.2 or whatever we put it in.

[sqlalchemy-bot]

Michael Bayer (@zzzeek) wrote:

specifically, the batch feature turns on naming convention and expects the reflected objects to use those names. batch would need to pass an additional flag to reflection apply_naming_conventions so that it gets the names applied to objects coming back from sqlite.