alembic

How can I insert some seed data in my first migration? If the migration is not the best place for this, then what is the best practice? """empty message Revision ID: 384cfaaaa0be Revises: None Create Date: 2013-10-11 16:36:34.696069 """ # revision identifiers, used by Alembic. revision = '384cfaaaa0be' down_revision = None from alembic import op import sqlalchemy as sa def upgrade(): ### commands auto generated by Alembic - please adjust! ### op.create_table('list_type', sa.Column('id', sa.Integer(), nullable=False), sa.Column('name', sa.String(length=80), nullable=False), sa

Does alembic upgrade head run inside a transaction so that all database alterations succeed, or fail? If not, why was it designed this way? My understanding is alembic runs inside a transaction for databases that support it, like Postgres. If you're on a database that does not support this ( cough MySQL cough ), you can't use this functionality. Alessandro Cosentino That's something you can decide within the env.py , which is where you customize the behaviour of the migrations to suit your setup. You can see how to make sure your upgrades happen in a transaction from the template provided as

My model looks like class Category(UserMixin, db.Model): __tablename__ = 'categories' uuid = Column('uuid', GUID(), default=uuid.uuid4, primary_key=True, unique=True) name = Column('name', String, nullable=False) parent = Column('parent', String, nullable=False) created_on = Column('created_on', sa.types.DateTime(timezone=True), default=datetime.utcnow()) __table_args__ = (UniqueConstraint('name', 'parent'),) def __init__(self, name, parent): self.name = name self.parent = parent def __repr__(self): return '<Category:%s:%s:%s>' % ( self.uuid, self.name, self.category_type) where GUID is custom

I'm using Alembic as migration tool and I'm launching the following pseudo script on an already updated database (no revision entries for Alembic, the database schema is just up to date). revision = '1067fd2d11c8' down_revision = None from alembic import op import sqlalchemy as sa def upgrade(): op.add_column('box', sa.Column('has_data', sa.Boolean, server_default='0')) def downgrade(): pass It gives me the following error only with PostgreSQL behind (it's all good with MySQL): INFO [alembic.migration] Context impl PostgresqlImpl. INFO [alembic.migration] Will assume transactional DDL. INFO

I am trying to use Alembic for the first time and want to use --autogenerate feature described here My project structure looks like project/ configuration/ __init__.py dev.py test.py core/ app/ models/ __init__.py user.py db/ alembic/ versions/ env.py alembic.ini I am using Flask and SQLAlchemy and their Flask-SQLAlchemy extension. my model User looks like class User(UserMixin, db.Model): __tablename__ = 'users' # noinspection PyShadowingBuiltins uuid = Column('uuid', GUID(), default=uuid.uuid4, primary_key=True, unique=True) email = Column('email', String, nullable=False, unique=True)

I would like to modify some database data as part of an alembic upgrade. I thought I could just add any code in the upgrade of my migration, but the following fails: def upgrade(): ### commands auto generated by Alembic - please adjust! ### op.add_column('smsdelivery', sa.Column('sms_message_part_id', sa.Integer(), sa.ForeignKey('smsmessagepart.id'), nullable=True)) ### end Alembic commands ### from volunteer.models import DBSession, SmsDelivery, SmsMessagePart for sms_delivery in DBSession.query(SmsDelivery).all(): message_part = DBSession.query(SmsMessagePart).filter(SmsMessagePart.message