GeoDjango's queryset API allows for specifying a field_name that should be used for the specific method used. The keyword is, however, limited to fields on the same model itself.
According to the documentation PostGIS is the only backend that supports calculations on related models such as: stores__location. This currently limits the template tag to be only usable with PostGIS.
This need to be solved. Ideally with a solution that works for every backend although it might be better to leverage the PostGIS internal handling on that backend and have a fallback for others.
GeoDjango's queryset API allows for specifying a
field_name
that should be used for the specific method used. The keyword is, however, limited to fields on the same model itself.According to the documentation PostGIS is the only backend that supports calculations on related models such as:
stores__location
. This currently limits the template tag to be only usable with PostGIS.This need to be solved. Ideally with a solution that works for every backend although it might be better to leverage the PostGIS internal handling on that backend and have a fallback for others.