#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 charettes):
Replying to [comment:6 timgraham]:
> I'm okay with requiring `parent_link=True` but could we let it go
through the deprecation cycle?
In the light of the existing tests I suppose we should just to be extra
safe even if the test model's `check()` method returns multiple errors and
the model is simply unusable with the ORM as `field.primary_key is True`
and `field.remote_field.parent_link is False`.
--
Ticket URL: <https://code.djangoproject.com/ticket/26320#comment:7>
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.f8e25fbcaf783d2e00525f8a1963050e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
