Maya Alembic Caching Guide: Boost Viewport Performance
Learn how to eliminate viewport lag in Maya by using Alembic (.abc) caching to bake complex rig deformations into high-performance geometry streams.
Loading…
ReadMeFeed / Community knowledge
#alembic
Real questions. Useful conversations. Find the people who know your stack.
Airflow 2.6 db upgrade failure leaves no supported rollback path — how to recover the metadata database safely?
Failed airflow db upgrade on 2.6.x When an Airflow upgrade applies Alembic migrations via airflow db upgrade and one script fails midway, the metadata database can be left in a partially migrated state. As of Airflow 2.6.x there is no built-in rollback command — no airflow db rollback exists, and Alembic's downgrade is not exposed through the Airflow CLI. Co
Flask‑Migrate Autogenerate vs Manual SQL Scripts: Which yields safer rollbacks for complex schema changes?
Goal To guarantee that a database schema change in a Flask 2.x application can be rolled back without data loss or orphaned columns. Constraint Column type changes and other non‑trivial alterations often require custom logic. Alembic’s autogenerate may miss these, while manual SQL scripts lack an automatic reverse path unless explicitly written. Uncertainty
Alembic Downgrade vs. Metadata Database Restore for Failed Upgrades
Schema Recovery Strategies When performing an Apache Airflow upgrade, the airflow db upgrade command applies incremental schema revisions via Alembic. If a migration fails mid-process, the metadata database may be left in an inconsistent state, necessitating a recovery action before the scheduler or webserver can be safely restarted. Recovery Constraints The
SQLAlchemy Session and Alembic Migrations: Can rollback() Safely Recover After a Failed Schema Change?
Scenario An application runs Alembic migrations and ordinary ORM work through SQLAlchemy 2.x Sessions against both PostgreSQL and MySQL. When a migration fails partway through, the recovery code calls session.rollback() and continues using the same Session and its mapped objects. Uncertainty PostgreSQL supports transactional DDL, so a failed ALTER TABLE can
sqlalchemyOpenStack expand/contract migrations: no enforced window before rollback becomes impossible
Goal I am planning an upgrade of an OpenStack service (Nova/Neutron-style, Alembic-managed schema) and want a rollback path that does not depend solely on restoring a database backup. My understanding is that expand migrations are additive and safe to roll back from, while contract migrations drop columns and are effectively irreversible, and that most proje
openstack