#34792: Creating and saving a model using a custom primary key field can yield a
bad "id" value on the instance
-------------------------------------+-------------------------------------
Reporter: mike w | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: field, custom | Triage Stage:
fields | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by camuthig):
* cc: camuthig (added)
Comment:
I can reproduce this in version 3.2, but not in 4.0+.
It looks like this is a duplicate of #32442 and was resolved there. I'm
just starting out triaging tickets, but I believe this should be resolved
as a duplicate. I'm not sure that it should be kept open to patch 3.2 as
LTS since it seems like a backwards incompatible change. Can someone with
more experience please confirm?
--
Ticket URL: <https://code.djangoproject.com/ticket/34792#comment:2>
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/0107018a2076701f-b95fde8b-2da0-4098-933d-a4b9c949fe8e-000000%40eu-central-1.amazonses.com.
