Automated Action 783583b234 Fix database migration import path issue
Updated migrations/env.py to import Base from app.database.session
instead of app.models, fixing the 'cannot import name Base' error.
2025-05-31 21:25:06 +00:00

112 lines
3.3 KiB
Python

import os
import sys
from logging.config import fileConfig
from pathlib import Path
from alembic import context
from sqlalchemy import engine_from_config, pool
# Add the project root directory to the Python path
# This ensures that the 'app' module can be imported correctly
project_root = str(Path(__file__).parents[1].absolute())
if project_root not in sys.path:
sys.path.insert(0, project_root)
# For containerized environments where the app might be in a different location
container_paths = [
"/app/repo", # Common container path
"/app", # Another common container path
]
for container_path in container_paths:
if os.path.exists(container_path) and container_path not in sys.path:
sys.path.insert(0, container_path)
# Now we can import our application modules
try:
from app.core.config import settings # noqa: F401 - Used in later operations
# Import Base from database.session where it's defined
from app.database.session import Base
except ImportError as e:
print(f"Error importing app modules: {e}")
print(f"Current sys.path: {sys.path}")
print("Looking for app module in these directories:")
for path in sys.path:
if os.path.isdir(path):
print(f" - {path}: {os.listdir(path)}")
raise
# 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.
if config.config_file_name is not None:
fileConfig(config.config_file_name)
# add your model's MetaData object here
# for 'autogenerate' support
target_metadata = 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() -> None:
"""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,
dialect_opts={"paramstyle": "named"},
)
with context.begin_transaction():
context.run_migrations()
def run_migrations_online() -> None:
"""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:
is_sqlite = connection.dialect.name == "sqlite"
context.configure(
connection=connection,
target_metadata=target_metadata,
render_as_batch=is_sqlite, # Important for SQLite
compare_type=True,
)
with context.begin_transaction():
context.run_migrations()
if context.is_offline_mode():
run_migrations_offline()
else:
run_migrations_online()