#22319: ValueError: Related model cannot be resolved
---------------------------------+--------------------------------------
Reporter: efrinut@… | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by debugger22):
I think this bug is still there in Django 1.9.3. Yesterday, I just added
`null=True, blank=True` to a `ForeignKey` field and executed `python
manage.py migrate` after `makemigrations` and it refused to migrate
stating the same error.
--
Ticket URL: <https://code.djangoproject.com/ticket/22319#comment:24>
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/075.242b0b4c729ab0d83f014e49c9bcf193%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
