Change History (2)

figured it out: its because a GeoManager is required if any part of the query needs spatial lookups.

I expected that since Apt has a GeoManager that it would be used for queries on its fields.

I guess if the join is happening on another model's fields then the manager for that other model should be used.
otherwise its force me to add a geo manager to a class that has no geo fields, but that's not too bad.