#34151: Adding explicit primary key with different type doesn't update related
ManyToManyFields.
-------------------------------------+-------------------------------------
Reporter: STANISLAV LEPEKHOV | Owner: (none)
Type: Bug | Status: new
Component: Migrations | Version: 4.1
Severity: Normal | Resolution:
Keywords: migrations pk uuid | Triage Stage: Accepted
relation |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carol Naranjo):
Maybe a more accurate but verbose title for this issue would be
"Inconsistent DB state after applying a migration that failed silently:
Adding explicit primary key with different type doesn't update related
ManyToManyFields."
---
Furthermore, and at this point this is not regarding this specific issue.
While investigating the current one and testing with sqlite I faced the
issue that I later described in the ticket #37006. For which I opened this
PR [https://github.com/django/django/pull/21073] and is waiting a second
review round. In that PR, the autodetector will recognize the alter
operations instead of the recreation, so if merged, that PR will also
avoid running into this issue in the first place.
--
Ticket URL: <https://code.djangoproject.com/ticket/34151#comment:29>
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/0107019dbf1f51a8-a4b234b1-0083-4b65-8dff-29dcaad711e2-000000%40eu-central-1.amazonses.com.
