#34151: Adding explicit primary key with different type doesn't update related
ManyToManyFields.
-------------------------------------+-------------------------------------
Reporter: STANISLAV LEPEKHOV | Owner: Bhuvnesh
Type: Bug | Status: assigned
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 STANISLAV LEPEKHOV):
Replying to [comment:11 Bhuvnesh]:
> STANISLAV, With a default uuid value you cannot insert previous values
of id in the new table ? So you can only change pk to uuid field when the
db is empty ? Correct me if i'm wrong.
The essence of the problem is that I cannot correctly change the DATA TYPE
for the pk field (including with an empty database). If I have an integer
data type and there is a m2m field in another model containing pk of these
objects, then when changing the data type to uuid, there will be no
changes in the m2m table after migration (the type int, int will remain
there)
--
Ticket URL: <https://code.djangoproject.com/ticket/34151#comment:12>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/0107018650b9f001-e80d6c02-d779-4ddd-a5dc-1c7ee7ef8252-000000%40eu-central-1.amazonses.com.
