#36364: Migration executor cannot handle AlterField operation on ForeignObject
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: composite primary | Triage Stage:
key | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* severity: Release blocker => Normal
Comment:
Setting back to Normal, realized we have this disclaimer:
> Django doesn’t support migrating to, or from, a composite primary key
after the table is created.
Perhaps this is an "optimization" ticket then.
--
Ticket URL: <https://code.djangoproject.com/ticket/36364#comment:1>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070196971ee066-e437e60c-c833-479d-83ac-9174931b9d21-000000%40eu-central-1.amazonses.com.