#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 artscoop):
This may not be a regression, but I'm sure it's a bug. The `field_name`
exposes the possibility to span across relationships. It works with
`ForeignKey`s, but not with `OneToOneField`s, which does not make much
sense. (The bug occurs because of the way the {{{"field__field__etc"}}}
relationship span is processed).
If a fix won't make it to Django 1.8 (there is a fix here:
[https://github.com/django/django/compare/master...pchiquet:ticket_22352])
I can still have a look at the dev version of Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/22352#comment:13>
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.76de2b39dcefb5d027a190f0a9ad55c8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
