#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):
Hi Jacob, let me clarify. The result in comment:22 is not by applying the
changes in comment:20, but rather by applying the changes in the original
report and in comment:6. (comment:20 was only my alternative attempt to
reproduce the issue when I didn't know which database was used).
That is, the issue before django 6.0 was when changing both field type AND
name in 1 step, which will result in a database in an inconsistent state
regarding the foreign keys.
After django 6.0 the migration script is the same, but the execution will
fail, which will at least leave the database in a consistent state.
--
Ticket URL: <https://code.djangoproject.com/ticket/34151#comment:28>
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/0107019dbf151792-a5bd2534-8ff4-4854-a9b3-74758150d5ac-000000%40eu-central-1.amazonses.com.
