questions about the alembic.

[9ovn]

If there's a models file inside each app as shown in the structure, how can I configure env.py or databases.py so that Alembic can detect all the tables in those models.py files? Currently, I'm manually importing each models file in env.py.

[zhanymkanov]

With SQLAlchemy Core, I just store all models in database.py, and then use that metadata in alembic's env.py. Storing all models in one file is simple, because it doesn't require importing all models manually.

Separation by models.py in each module is for ORM-based apps.

[pydevup]

I created a models registry.
Created orm folder in src and inside it the __init__.py file imported all models.

__init__.py file:

from src.auth.models import User
from src.models import BaseModel

__all__ = ["BaseModel"]

and inside alembic env.py file:

from src.orm import BaseModel
target_metadata = BaseModel.metadata

[0-th]

I use a variant of the approaches in the previous responses, where I create a Base class with metadata in src/database.py:

from sqlalchemy import MetaData
metadata = MetaData(naming_convention=DB_NAMING_CONVENTION)

class Base(MappedAsDataclass, AsyncAttrs, DeclarativeBase):
    metadata = metadata

i use this Base in all my models.py then re-import from there into src/__init__.py:

from src.auth.models import Base as AuthBase
__all__ = ["AuthBase"]

this ensures the models in the imported models.py modules are registered.

then in alembic env.py module:

from src.database import metadata

target_metadata = metadata