When sqalchemy application starts, it automatically modifies database schema, so that database tables would reflect ORM models in python code. In my case it's very unwanted, because when I'm switching between different branches / writing new migrations / etc it's easy sometimes to accidentally run application in a "transitional" moment, so the DB gets broken by the attempt of sqlalchemy to "fix" the DB. By broken I mean detached from the last applied alembic_version, so that I can't even run a downgrade and have to fix it manually or use recovery.
So is there any native setting in sqalchemy to just raise / assert when real database schema does not match ORM models instead of automatically modifying the DB?