Skip to content

SQLAlchemy and Flask application context #3

@ghost

Description

I get some issue with managing multiple SQLAlchemy db schema on my models when migration. I think, this is because of the flask application factory and application context design, referred from http://piotr.banaszkiewicz.org/blog/2012/06/29/flask-sqlalchemy-init_app/ .

Flask-SQLAlchemy has two usage modes.

Option 1

Binding the instance to a very specific Flask application

app = Flask(__name__)
db = SQLAlchemy(app)

Option 2

Create the object once and configure the application later to support it

db = SQLAlchemy()

def create_app():
    app = Flask(__name__)
    db.init_app(app)
    return app

The Openedoo core uses option 1, change the core to option 2 to help you make models migration in this module.

suggestions are welcome.

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