#26320: Multi-table inheritance pointer merged with another OneToOneField
-------------------------------------+-------------------------------------
Reporter: BertrandBordage | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
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 timgraham):
The current behavior
[https://github.com/django/django/blob/de8a11ba18d5902c668d4db47c38c9c6bdf9c1da/tests/model_inheritance_regress/models.py#L48-L51
is tested]. Checking `field.remote_field.parent_link` as suggested breaks
that test and a few others.
--
Ticket URL: <https://code.djangoproject.com/ticket/26320#comment:4>
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/073.7dbd088fb64896294d195b954159efb3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
