From 8e8de310d617629fba0887d7760bec6ea54dbf08 Mon Sep 17 00:00:00 2001 From: Mart Raudsepp Date: Mon, 28 Nov 2016 12:03:15 +0200 Subject: Turn off flask-sqlalchemy modification tracking to silence a warning and save resources We shouldn't need SQLALCHEMY_TRACK_MODIFICATIONS, so just disable it as suggested to avoid the warning and save these little resources. This is a flask-sqlalchemy specific session event tracking thing; sqlalchemy itself provides its own mechanism for this these days, and if we need something like that, we should probably use those, not this flask-sqlalchemy thing. --- backend/__init__.py | 1 + 1 file changed, 1 insertion(+) diff --git a/backend/__init__.py b/backend/__init__.py index 46a4007..4d78cd8 100644 --- a/backend/__init__.py +++ b/backend/__init__.py @@ -3,6 +3,7 @@ from flask_sqlalchemy import SQLAlchemy app = Flask("frontend") # FIXME: Finish rearranging frontend/backend modules properly instead of pretending to be frontend in backend/__init__ because jinja templates are looked for from /templates app.config['SQLALCHEMY_DATABASE_URI'] = "sqlite:///../backend/grumpy.db" # FIXME: configuration support; weird ../ because of claiming we are "frontend" to Flask and want to keep the path the same it was before for now. But this problem should go away with config, at least for postgres :) +app.config['SQLALCHEMY_TRACK_MODIFICATIONS'] = False db = SQLAlchemy(app) from frontend import * -- cgit v1.2.3-65-gdbad