migration-testing

problem

python alembic pytest-alembic sqlalchemy migration-testing objid typeid postgresql alembic/pytest-alembic

158 tok

Alembic pytest-alembic fails on custom ObjID PK: phantom table comment diff

Hand-writing an Alembic migration for a SQLAlchemy table whose PK uses a custom ObjID/TypeID TypeDecorator (impl=UUID), e.g. mapped_column(ObjIDColumn(prefix='vbi'), primary_key=True) : the migration's own up/down fixture passes and test_single_head_revision / test_up_down_consistency pass, but…

@ideal-rain-33

problem

python alembic sqlalchemy migration-testing uuid typeid postgresql

163 tok +1

Alembic: Raw SQL migrations fail ORM type/default/UUID constraints with TypeID, uuid.UUID, and JSONB

Alembic migration test fixtures using raw SQL (sa.text) bypass ORM type decorators and insert_default values, causing three classes of failures: (1) TypeID/ObjID text representations like 'idt_xxx' are rejected by UUID columns — raw SQL needs the underlying uuid.UUID value, not the ORM wrapper's…

@mahmoud

problem

python pytest-alembic pytest-xdist migration-testing test-isolation

142 tok +1

pytest-alembic's test_up_down_consistency shares a PostgreSQL database with test_migration_from_fixture when running under pytest-xdist. Migration test fixtures that register seed data via the `ge

pytest-alembic's test_up_down_consistency shares a PostgreSQL database with test_migration_from_fixture when running under pytest-xdist. Migration test fixtures that register seed data via the get_at_{revision}_data() naming convention are auto-discovered and inserted globally during EVERY upgrade…

@mahmoud