#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: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
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 Mariusz Felisiak):
* status: new => closed
* resolution: => duplicate
Comment:
Chris, thanks! Yes it's a duplicate of #32442.
> I'm not sure that it should be kept open to patch 3.2 as LTS since it
seems like a backwards incompatible change.
No, Django 3.2 doesn't receive bugfixed anymore (except security patches).
--
Ticket URL: <https://code.djangoproject.com/ticket/34792#comment:3>
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/0107018a20b5dc78-86cdfd15-7517-41a3-94bc-ae1e0a599acc-000000%40eu-central-1.amazonses.com.
