#18012: Propagate reverse foreign keys from proxy models to base class
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: charettes
Type: | Status: assigned
Cleanup/optimization |
Component: Database layer | Version: 1.4
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by carljm):
To clarify what I meant by "this ticket is mostly a result of seeking too
much equivalence between the DB schema and the models API": the entire
point of proxy classes is that they are _not_ equivalent to their base
class in terms of their Python behavior and API. FK reverse descriptors
(although their data is provided by an underlying schema in which there is
no distinction between a proxy and its base) are part of the Python
behavior and API, so it is entirely reasonable and expected that a proxy
class might have different relation descriptors attached to it than its
base class does.
That's why I believe that this ticket should simply be closed without
changes, though (as I said) if others feel strongly that the behavior
should be changed, I won't stand in the way.
--
Ticket URL: <https://code.djangoproject.com/ticket/18012#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.2f15fe27f377bf757594938507f35f40%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
