#22352: GeoQuerySet methods: support lookups on reversed o2o relationships as
field_name
-------------------------------------+-------------------------------------
Reporter: pchiquet | Owner: anonymous
Type: New feature | Status: closed
Component: GIS | Version: master
Severity: Normal | Resolution: wontfix
Keywords: geodjango, | Triage Stage: Accepted
GeoQuerySet |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by pembo13):
Replying to [comment:9 claudep]:
> I have tested this with my branch which replaces `GeoQuerySet` methods
by model functions (#24214). And this was not a problem at all, be it with
OneToOne or with OneToMany relations. The syntax will be
`User.objects.all().annotate(dist=distance('userlocation__point',
Point(1,1)))`
>
> I'll close this one as won't fix, as I think it is not worth working on
to-be-deprecated code. The aforementioned branch is waiting for someone
knowledgeable with Oracle GIS to write the Oracle support.
So what do we about this in Django 1.8?
--
Ticket URL: <https://code.djangoproject.com/ticket/22352#comment:16>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.7871bd9f3bc6a653bee53a8d786c8422%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
