Hi Mike, Thanks. If I read you correctly, I have 2 options:
1.) autogenerate --> proof-read migration script --> manually add the views to upgrade() and downgrade() 2.) Write custom extensions and invoke them in env.py --> autogenerate --> proof-read migration script Say I want to explore (1). Is it as simple as adding the following to my upgrade()? meta = Base.metadata vgbd_view = Table(“v_gbd”, meta, autoload=True, autoload_with=op.get_bind()) What would be in downgrade() then? Your opinion on version control makes sense. On our end we expect people of varying degrees of python experience to touch this schema migration pipeline, some even more noobs than me. Which is why there's incentive to remove as much manual work as possible. Much obliged. -- You received this message because you are subscribed to the Google Groups "sqlalchemy-alembic" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy-alembic+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
