#34151: Adding explicit primary key with different type doesn't update related
ManyToManyFields.
-------------------------------------+-------------------------------------
Reporter: STANISLAV LEPEKHOV | Owner: Carol
| Naranjo
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
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* resolution: fixed =>
* status: closed => new
Comment:
Hi Carol, thanks for the triage. Did you bisect the behavior change to a
specific commit? I tried to check your triage result, but when running the
changes described in comment:20, I get `AlterField` & `AlterField` as
described there, not `RemoveField` & `AlterField` as described in
comment:22. Also, I see no difference all the way back to 4.2. Let's keep
this open until someone else can confirm your triage.
--
Ticket URL: <https://code.djangoproject.com/ticket/34151#comment:25>
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/0107019db4b82a52-b4de9b8b-bfc8-4857-9869-86fade346506-000000%40eu-central-1.amazonses.com.