#25858: Deriving from abstract model with foreign key to model in same app
broken
on Django 1.9
-------------------------------------+-------------------------------------
Reporter: kaedroho | Owner: charettes
Type: Bug | Status: assigned
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Release blocker | 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 timgraham):
I guess there's a small design decision about whether or not it could
possibly be a useful "feature" to have the option of using the model name
only in the `ForeignKey` to be able to refer to a local model in the app
in which the abstract model is actually used and to require an `app_label`
in the `ForeignKey` otherwise?
--
Ticket URL: <https://code.djangoproject.com/ticket/25858#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.223d6ea7c47a80b552bb9dea81f646e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
