Turn off a warning in sqlalchemy
Question:
I’m using sqlalchemy with reflection, a couple of partial indices in my DB make it dump warnings like this:
SAWarning: Predicate of partial index i_some_index ignored during reflection
into my logs and keep cluttering. It does not hinder my application behavior. I would like to keep these warnings while developing, but not at production level. Does anyone know how to turn this off?
Answers:
Python’s warning module provides a handy context manager that catches warnings for you.
Here’s how to filter out the SQLAlchemy warning.
import warnings
from sqlalchemy import exc as sa_exc
with warnings.catch_warnings():
warnings.simplefilter("ignore", category=sa_exc.SAWarning)
# code here...
As for development vs production, you can just have this warning wrap around your application’s entry point or an external script that invokes your application in your production environment.
Usually, I solve this by having an environment variable that executes a slightly different code path than when developing, for example, wrapping around different middleware etc.
the warning means you did a table or metadata reflection, and it’s reading in postgresql indexes that have some complex condition which the SQLAlchemy reflection code doesn’t know what to do with. This is a harmless warning, as whether or not indexes are reflected doesn’t affect the operation of the application, unless you wanted to re-emit CREATE statements for those tables/indexes on another database.
I’m using sqlalchemy with reflection, a couple of partial indices in my DB make it dump warnings like this:
SAWarning: Predicate of partial index i_some_index ignored during reflection
into my logs and keep cluttering. It does not hinder my application behavior. I would like to keep these warnings while developing, but not at production level. Does anyone know how to turn this off?
Python’s warning module provides a handy context manager that catches warnings for you.
Here’s how to filter out the SQLAlchemy warning.
import warnings
from sqlalchemy import exc as sa_exc
with warnings.catch_warnings():
warnings.simplefilter("ignore", category=sa_exc.SAWarning)
# code here...
As for development vs production, you can just have this warning wrap around your application’s entry point or an external script that invokes your application in your production environment.
Usually, I solve this by having an environment variable that executes a slightly different code path than when developing, for example, wrapping around different middleware etc.
the warning means you did a table or metadata reflection, and it’s reading in postgresql indexes that have some complex condition which the SQLAlchemy reflection code doesn’t know what to do with. This is a harmless warning, as whether or not indexes are reflected doesn’t affect the operation of the application, unless you wanted to re-emit CREATE statements for those tables/indexes on another database.