ah no, now I get it: geo queries requires a GeoManager. so even though the starting class does not have gis fields, it needs a GeoManager in order to build queries addressing fields on the other model.
I'm not sure what should happen, the error messaging is very misleading, but once you know the reason I supposed it makes sense. 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. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
