#26384: migrations fail with Python 2.7 and Django > 1.9
----------------------------+--------------------------------------
Reporter: brian | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.9
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 brian):
Suspect the failure on mysql is that mysql doesn't like having the primary
key renamed.
The failure with sqlite looks like some sort of regression in Django 1.9.
No idea if is it feasible to fix or not.
Apologies if any of this was documented somewhere and I missed it...
I plan to work around this for now by squashing the migrations and
removing the rename.
--
Ticket URL: <https://code.djangoproject.com/ticket/26384#comment:3>
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.3e53aa58530621e7b7bea7888e771f7f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
