#14922: Failure with spatial queries spanning a foreign key join
-----------------------------------+----------------------------------------
Reporter: crucialfelix | Owner: nobody
Status: closed | Milestone:
Component: GIS | Version: 1.2
Resolution: invalid | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Changes (by crucialfelix):
* status: new => closed
* resolution: => invalid
Comment:
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.
--
Ticket URL: <http://code.djangoproject.com/ticket/14922#comment:2>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
