#26186: When extending from abstract model, ForeignKey points to wrong
application
-------------------------------------+-------------------------------------
Reporter: skyjur | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.9
(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):
In your example both `app_B.Model2.model1` and `app_A.Model2.model1` are
pointing to `app_B.Model1` because `app_B`'s models module was imported
first (because of the order of `INSTALLED_APPS`) and triggered the import
of `app_A.abstract`.
No version of Django allowed you to make `Model2` point to their
respective `Model1`. The only thing that changed in Django 1.9.2 is that
lazy related references defined on abstract models are now bound to the
application in which they are defined.
--
Ticket URL: <https://code.djangoproject.com/ticket/26186#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/064.8c55a7201d337b5423af836ad2724f0a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
