为什么我在 alembic 迁移方面遇到问题

Kli*_*mud 5 python sqlalchemy flask alembic

项目结构(仅包含数据库迁移的目录):

--db_manage:
  alembic.ini
  --alembic:
    env.py
    script.py.mako
    README
    --versions:
      #migration files
Run Code Online (Sandbox Code Playgroud)

当我尝试运行 command: 时python db_manage/alembic/env.py,我有如下响应:

Traceback (most recent call last):
  File "db_manage/alembic/env.py", line 8, in <module>
    config = context.config
AttributeError: module 'alembic.context' has no attribute 'config'
Run Code Online (Sandbox Code Playgroud)

在哪种情况下我有这个问题?
PS
文件alembic.ini

# A generic, single database configuration.

[alembic]
# path to migration scripts
script_location = alembic

# template used to generate migration files
# file_template = %%(rev)s_%%(slug)s

# max length of characters to apply to the
# "slug" field
#truncate_slug_length = 40

# set to 'true' to run the environment during
# the 'revision' command, regardless of autogenerate
# revision_environment = false

# set to 'true' to allow .pyc and .pyo files without
# a source .py file to be detected as revisions in the
# versions/ directory
# sourceless = false

# version location specification; this defaults
# to numus/versions.  When using multiple version
# directories, initial revisions must be specified with --version-path
# version_locations = %(here)s/bar %(here)s/bat numus/versions

# the output encoding used when revision files
# are written from script.py.mako
# output_encoding = utf-8

sqlalchemy.url = postgresql://test:oe50yxXOspYDsaXSO7Gf@localhost/test


# Logging configuration
[loggers]
keys = root,sqlalchemy,alembic

[handlers]
keys = console

[formatters]
keys = generic

[logger_root]
level = WARN
handlers = console
qualname =

[logger_sqlalchemy]
level = WARN
handlers =
qualname = sqlalchemy.engine

[logger_alembic]
level = INFO
handlers =
qualname = alembic

[handler_console]
class = StreamHandler
args = (sys.stderr,)
level = NOTSET
formatter = generic

[formatter_generic]
format = %(levelname)-5.5s [%(name)s] %(message)s
datefmt = %H:%M:%S
Run Code Online (Sandbox Code Playgroud)

文件env.py

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

# 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 = None

# 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, target_metadata=target_metadata, literal_binds=True)

    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.

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

    with connectable.connect() as connection:
        context.configure(
            connection=connection,
            target_metadata=target_metadata
        )

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

if context.is_offline_mode():
    run_migrations_offline()
else:
    run_migrations_online()
Run Code Online (Sandbox Code Playgroud)

Ilj*_*ilä 6

您尝试调用迁移工具的方式有两个错误。首先,您应该使用alembic脚本而不是尝试env.py直接运行。从教程

env.py- 这是一个 Python 脚本,只要调用 alembic 迁移工具就会运行。至少,它包含配置和生成 SQLAlchemy 引擎的指令,从该引擎获取连接以及事务,然后调用迁移引擎,使用连接作为数据库连接的来源。

其次,虽然您可以将您的alembic.ini位置保留在任何位置,但默认行为是查看当前目录:

Alembic 将一个文件alembic.ini放入当前目录。这是alembic脚本在调用时查找的文件。这个文件可以在任何地方,或者在alembic通常调用脚本的同一目录中,或者如果在不同的目录中,可以使用运行器的--config选项指定alembic

因此,如果它保存在其他地方,则必须使用-c, 或--config开关指示 alembic 位置。例如:

alembic --config db_manage/alembic.ini
Run Code Online (Sandbox Code Playgroud)

  • @CharlieOConor 因为你**没有问**。相反,你写了一篇长篇大论,完全超出了这个特定问答的重点,我认为其他负面反馈也与咆哮有关。 (2认同)
  • 无论如何,你确实说得有道理。我认为“两全其美”的解决方案是具有适用于通常情况的命令行和配置的工具,并由实现逻辑的库支持。 (2认同)