How do I know if I can disable SQLALCHEMY_TRACK_MODIFICATIONS?
The above answers look good. However, I wanted to point out this line in the Flask-SQLAlchemy documentation because I was still getting these warnings after setting SQLALCHEMY_TRACK_MODIFICATIONS = False in my application config.
On this page: http://flask-sqlalchemy.pocoo.org/2.3/config/
The following configuration values exist for Flask-SQLAlchemy. Flask-SQLAlchemy loads these values from your main Flask config which can be populated in various ways. Note that some of those cannot be modified after the engine was created so make sure to configure as early as possible and to not modify them at runtime.
In other words, make sure to set up your app.config before creating your Flask-SQLAlchemy database.
For example, if you are configuring your application to set SQLALCHEMY_TRACK_MODIFICATIONS = False:
from flask import Flask
app = Flask(__name__)
app.config['SQLALCHEMY_TRACK_MODIFICATIONS'] = False
db = SQLAlchemy(app)
Jeff Widman's detailed explanation is simply perfect.
Since I had some copy'n'paste fights before getting this right I'd like to make it easier for the next one that will be in my shoes.
The needed configuration must be added in your code, between:
app = Flask(__name__)
and:
db = SQLAlchemy(app)
If you want to enable track modifications add:
app.config['SQLALCHEMY_TRACK_MODIFICATIONS'] = True
Otherwise, if you are not using this feature, you may want to change the value to False:
app.config['SQLALCHEMY_TRACK_MODIFICATIONS'] = False
This will silence the warning anyway since you're explicitly setting the parameter in your configuration.
The final result should look similar to this example:
from flask import Flask
app = Flask(__name__)
app.config['SQLALCHEMY_TRACK_MODIFICATIONS'] = False
db = SQLAlchemy(app)
Note
Please keep in mind that currently (July 2022) SQLALCHEMY_TRACK_MODIFICATIONS defaults to None so there is no risk of memory loss related if you don't configure it.
Anyhow, if you want to suppress the warning, you will have to choose between True and False in your config.
Thanks to Jeff Widman for this added suggestion and details.
Most likely your application doesn't use the Flask-SQLAlchemy event system, so you're probably safe to turn off. You'll need to audit the code to verify--you're looking for anything that hooks into models_committed or before_models_committed. If you do find that you're using the Flask-SQLAlchemy event system, you probably should update the code to use SQLAlchemy's built-in event system instead.
The default value as of Flask-SQLAlchemy 2.1 is None, which is a falsy value, so the event system is disabled. In older versions, the default value was True, so you'll need to explicitly disable it.
However, in both cases, the warning won't be silenced until this is explicitly set to False. To do that, add:
SQLALCHEMY_TRACK_MODIFICATIONS = False
to your app config.
Background--here's what the warning is telling you:
Flask-SQLAlchemy has its own event notification system that gets layered on top of SQLAlchemy. To do this, it tracks modifications to the SQLAlchemy session. This takes extra resources, so the option SQLALCHEMY_TRACK_MODIFICATIONS allows you to disable the modification tracking system.
The rationale for the change is three-fold:
Not many people use Flask-SQLAlchemy's event system, but most people don't realize they can save system resources by disabling it. So a saner default is to disable it and those who want it can turn it on.
The event system in Flask-SQLAlchemy has been rather buggy (see issues linked to in the pull request mentioned below), requiring additional maintenance for a feature that few people use.
In v0.7, SQLAlchemy itself added a powerful event system including the ability to create custom events. Ideally, the Flask-SQLAlchemy event system should do nothing more than create a few custom SQLAlchemy event hooks and listeners, and then let SQLAlchemy itself manage the event trigger.
You can see more in the discussion around the pull request that started triggering this warning.