#36183: Model o2o inheritance with abstract models does not "evaluate" a lazy
relationship
-------------------------------------+-------------------------------------
Reporter: BeryCZ | Owner: (none)
Type: New feature | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):
* resolution: => wontfix
* stage: Accepted => Unreviewed
* status: new => closed
* type: Bug => New feature
Comment:
IMO `AbstractPageType` is tightly coupled to `Page` as it overrides the
inheritance behavior of sub-classing `Page`. Having `AbstractPageType` be
defined in the same place as `Page` is reasonable. All models that want to
inherit this, inherit from `Page` anyway, so this doesn't cause things
like circular imports.
-------
I agree that this is a request to support a niche use case that has never
been supported by Django before, hence will categorize this as a new
feature request.
The recommended path forward is to now propose and discuss this with the
community and gain consensus. To do that, please consider starting a new
conversation on the [https://forum.djangoproject.com/c/internals/5 Django
Forum], where you'll reach a broader audience and receive additional
feedback.
Feature requests are closed until there is an agreement to add the
support. Hence, I'll close the ticket for now, but if the community agrees
this should be supported, please return to this ticket and reference the
forum discussion so we can re-open it. For more information, please refer
to [https://docs.djangoproject.com/en/stable/internals/contributing/bugs-
and-features/#requesting-features the documented guidelines for requesting
features].
----
On options 2-4, all are fine to me and I don't think there's a rush. We
could make a decision and create a new ticket for any combination of these
--
Ticket URL: <https://code.djangoproject.com/ticket/36183#comment:15>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701953bd04cc0-c9f9c977-1f4e-4285-91cb-16dc4fd9791a-000000%40eu-central-1.amazonses.com.
