#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 BertrandBordage):
@timgraham: Sure! Since this is a rare use case, do you think it could be
a `RemovedInDjango110Warning` introduced in 1.9.4? Or maybe it’s too
soon?
--
Ticket URL: <https://code.djangoproject.com/ticket/26320#comment:8>
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.bbfc09e1e213033b6850de2121ee47ce%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
