Of course they don't. That's the whole point of running alembic, isn't it?
Whenever I decide to change something in my DB, I update my models and the
alembic script so that the next upgrade will make my models reflect my DB
structure.
Did I get it wrong?
On Tuesday, September 1, 2015 at 5:13:13
I'm afraid I don't understand the issue. It sounds like you have
concerns that your SQLAlchemy models do not always correspond to the
state of the DB?
On Tue, Sep 1, 2015, at 03:07 AM, Ofir Herzas wrote:
> I've been working with sqlalchemy/alembic for several years now, but just
> recently stumbl
I've been working with sqlalchemy/alembic for several years now, but just
recently stumbled on an important issue.
Here is how I use to work:
1. Issue
Base.metadata.create_all(engine)
to make sure that missing tables are created
2. check the current revision by issuing
context.get_current_revi
