#27311: Assigning ForeignKey fields in migrations
-------------------------------------+-------------------------------------
Reporter: Odero | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.10
Severity: Normal | Resolution:
Keywords: migrations, | Triage Stage:
foreignkey | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Odero):
I discovered that it was a caching issue. I have caching enabled by
default. It seems that whenever the item is fetched it creates and returns
the cached version which is of the *real* type i.e. the one you'd get by
doing
{{{
from app1.models import A
}}}
which is different from what you'd get by doing
{{{
apps.get_model('app1', 'A')
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27311#comment:4>
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/063.60cdf798a4816b81277d518ef15ec80b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
