#36183: Model o2o inheritance with abstract models does not "evaluate" a lazy
relationship
-------------------------------------+-------------------------------------
Reporter: BeryCZ | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by BeryCZ):
Hello Simon, thank you for your response.
The re-organization of the models isnt really a solution, because in my
case the abstracts are in a reusable app and then models are project
specific. I dont like to have concrete models in a reusable app and never
be able to rewrite them, but I should have the `AbstractPageType` in the
reusable app already.
I would really like if it was possible to define the parent_link's field
name in the abstract, so I don't have to define it on all PageType models,
because `page` is much more comfortable to work with than `page_ptr`.
--
Ticket URL: <https://code.djangoproject.com/ticket/36183#comment:5>
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/01070194fddfd379-07e27a8e-bb7d-4108-92f0-94dbc98e9a89-000000%40eu-central-1.amazonses.com.