#25168: Document how to avoid foreign key constraint error after upgrade to 1.8
--------------------------------------+-------------------------
Reporter: rwillmer | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Keywords: foreign key
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+-------------------------
I hit this problem myself, and eventually figured out that it was because
I hadn't created the fake install of the initial migrations for all my
apps in my Django project.
I've seen and answered a few questions caused by this on StackOverflow, so
I suspect it may be a common problem. e.g.
http://stackoverflow.com/questions/29483119/django-1-8-syncdb-not-working-
throwing-a-foreign-key-constraint-error
http://stackoverflow.com/questions/28561458/django-mysql-error-when-
creating-tables
--
Ticket URL: <https://code.djangoproject.com/ticket/25168>
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/051.061c718f24c54b8cb58b16be243136e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
