#35991: Migrations crash on SQLite when renaming part of CompositePrimaryKey.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"c534b6c4938cd817e5d7903dce15a689a4862a99" c534b6c]:
{{{#!CommitTicketReference repository=""
revision="c534b6c4938cd817e5d7903dce15a689a4862a99"
Fixed #35991 -- Fixed crash when adding non-nullable field after renaming
part of CompositePrimaryKey on SQLite.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/35991#comment:9>
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/01070194082ff126-0fb15a15-571e-48f4-b61a-9fc11b00cd60-000000%40eu-central-1.amazonses.com.