我正在寻找一种将 Alembic 与 SQLAlchemy 集成的方法。我需要的是一种让 Alembic 检测到我在 models.py 中所做的任何更改的方法当我运行 alembic revision -m "<message_here>" 时自动更新它到 MySQL 数据库中和 alembic upgrade head .

这是我目前拥有的。

这是我的应用程序目录结构。

/myapplication
    models.py
    __init__.py
    app.py
    /migrations
        env.py
        script.py.mako
        /versions

models.py包含以下内容。

from sqlalchemy import Column, Integer, String
from sqlalchemy.ext.declarative import declarative_base

Base = declarative_base()

class User(Base):
    """ `User` stores the basic info about a user
    """
    __tablename__ = 'user'
    id = Column(Integer, primary_key=True)
    name = Column(String(255), nullable=False)
    phone = Column(String(15), nullable=False)

我已经配置了我的 alembic.ini使用我的数据库凭据 sqlalchemy.url

我的 env.py 中有以下内容

from __future__ import with_statement
from alembic import context
from sqlalchemy import engine_from_config, pool
from logging.config import fileConfig
from myapplication import models

# this is the Alembic Config object, which provides
# access to the values within the .ini file in use.
config = context.config

# Interpret the config file for Python logging.
# This line sets up loggers basically.
fileConfig(config.config_file_name)

# add your model's MetaData object here
# for 'autogenerate' support
# from myapp import mymodel
# target_metadata = mymodel.Base.metadata
target_metadata = models.Base.metadata

# other values from the config, defined by the needs of env.py,
# can be acquired:
# my_important_option = config.get_main_option("my_important_option")
# ... etc.

def run_migrations_offline():
    """Run migrations in 'offline' mode.

    This configures the context with just a URL
    and not an Engine, though an Engine is acceptable
    here as well.  By skipping the Engine creation
    we don't even need a DBAPI to be available.

    Calls to context.execute() here emit the given string to the
    script output.

    """
    url = config.get_main_option("sqlalchemy.url")
    context.configure(url=url)

    with context.begin_transaction():
        context.run_migrations()

def run_migrations_online():
    """Run migrations in 'online' mode.

    In this scenario we need to create an Engine
    and associate a connection with the context.

    """
    engine = engine_from_config(
                config.get_section(config.config_ini_section),
                prefix='sqlalchemy.',
                poolclass=pool.NullPool)

    connection = engine.connect()
    context.configure(
                connection=connection,
                target_metadata=target_metadata
                )

    try:
        with context.begin_transaction():
            context.run_migrations()
    finally:
        connection.close()

if context.is_offline_mode():
    run_migrations_offline()
else:
    run_migrations_online()

但是当运行迁移时使用

alembic revision -m "initial"

它说

Generating
migrations/versions/2d9d8de1aa80_initial.py...done

但是当我打开 migrations/versions/9aa5864e4c8_initial.py ，这就是我所看到的。

"""initial

Revision ID: 2d9d8de1aa80
Revises: None
Create Date: 2013-02-23 12:21:52.389906

"""

# revision identifiers, used by Alembic.
revision = '2d9d8de1aa80'
down_revision = None

from alembic import op
import sqlalchemy as sa


def upgrade():
    pass


def downgrade():
    pass

当我运行命令 alembic upgrade head 时，版本文件与我期望它创建并稍后与 MySQL 同步的表无关。 .如何配置 Alembic 以便在运行 alembic revision 时命令，它从 models.py 中选择模式并生成一个版本文件？我想我在这里遗漏了一些微不足道的东西。不知道是什么!

最佳答案

您想使用 --autogenerate 标志运行修订子命令，以便它检查模型的更改。

alembic revision --autogenerate -m "some message"

确保您了解 limitations of the autogenerate option .

关于sqlalchemy - 将 Alembic 与 SQLAlchemy 集成，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/15038036/