Matt,
That's a good point you brought up: if there's a ForeignKey to a model
with a geographic field, then the model with the ForeignKey requires
GeoManager to construct geographic queries on related objects (even if
the model itself does not have geographic fields).
The GeoManager overrides the
> Coercion of the type you describe is not required for any field
> currently supported. I would be hesitant to include coercion as a core
> part of the framework unless there is a generic need to coerce
> database values into Python values in some way other than that
> performed by the database b
> It's sleeping right now. The upcoming refactoring of Django's QuerySet
> mechanism looks like it'll make working with other ORMs a bit easier,
> so if someone wants to come back and revisit it then it'd be a bit
> less of an ambitious project ;)
Is there any place (e.g. a trac page) where inter
