In order to use spatially-enabled Django models, the Django DATABASE settings must use django.contrib.gis.db.backends.postgis as the engine. However, pg-database-utils then requests a postgis dialect from SQLAlchemy, which fails with:
Since this library is specific to postgresql databases, is it even necessary to get the engine/dialect from settings? Couldn't 'postgres` be hard-coded?
In order to use spatially-enabled Django models, the Django
DATABASE
settings must usedjango.contrib.gis.db.backends.postgis
as the engine. However,pg-database-utils
then requests apostgis
dialect from SQLAlchemy, which fails with:Since this library is specific to postgresql databases, is it even necessary to get the engine/dialect from settings? Couldn't 'postgres` be hard-coded?