#27581: Second-level proxy fails to inherit reverse relation from parent proxy
-------------------------------------+-------------------------------------
Reporter: Shai | Owner: nobody
Berger |
Type: Bug | Status: new
Component: Database | Version: 1.8
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Double proxy models are, as has been noted before, a questionable design
decision, but they should still work (the reason here: we need more than
one Admin interface for the parent proxy class). We have, basically, this:
{{{
class A(models.Model):
pass
class B(A):
class Meta:
proxy=True
class F(models.Model):
b = models.ForeignKey(B, related_name="bffs")
class C(B):
class Meta:
proxy=True
}}}
and when we try
{{{
qset = C.objects.filter(bffs__in=whatever)
}}}
we get "bffs not recognized, options are ..."
Not sure if this still happens with master, will try to repro later.
--
Ticket URL: <https://code.djangoproject.com/ticket/27581>
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/048.49ac3fc75369a7c19f04167c5564cd6b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
