Skip to content

Handle database migrations more gracefully #32

@leon-wbr

Description

@leon-wbr

Database migrations are handled in different places in the application currently, and in different ways. Flask-Security provides a fairly simple solution out-of-the-box through SQLAlchemy's ORM. If we switch to that ORM as well, we could use it just as the extension does.

But until then, where and how do we want to handle migrations?

Do we create a flask migrate command or just use flask init?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions