#36183: Model o2o inheritance with abstract models does not "evaluate" a lazy
relationship
-------------------------------------+-------------------------------------
Reporter: BeryCZ | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Thanks Sarah!
In that case it means that #20883 never truly worked but there has been
partial broken support for in `main` for over 13 years (since 1.7).
I guess that leaves us with a few non-mutually exclusive options
1. Add proper support for this pattern
2. Document that he correct way to do this is to have the abstract model
defining the parent link subclass the concrete model and add tests for it
(abstract MTI) (see comment:3)
3. Revert tested support for it since it never really worked and the tests
were very shallow
4. Revert uncovered code once 3. is applied
Given this has been flying under the radar for years and that users in the
wild might have been using 2 (which works just fine) I'd favor all options
but 1.
--
Ticket URL: <https://code.djangoproject.com/ticket/36183#comment:11>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019538bb76a8-e7c4807d-92d9-43be-9fa1-2e0c0be9b57b-000000%40eu-central-1.amazonses.com.
