#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: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by charettes):
In order to fix #26186 the patch for this ticket is planed to be reverted
in Django 1.9.3.
The suggested approach for the issue reported here is to bound your app
relative reference to an application (`app_label.ConcreteModel` in your
reported case) because what we initially thought as a new behavior
introduced in Django 1.9 has been possible since at least Django 1.2 given
the appropriate setup.
In order to support both use cases it was decided that app relative lazy
relationships should be resolved against their concrete model's
`app_label` and an explicit `app_label` should be added to the lazy
relationship if the abstract model was meant to be used in a foreign
application while maintaining a relationship to a specific application's
model.
--
Ticket URL: <https://code.djangoproject.com/ticket/25858#comment:12>
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.59ee0d7a67ab0c0e40cb1cdc252dfc61%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
