#32332: Saving parent object after setting on child leads to data loss for
parents
with non-numeric primary key.
-------------------------------------+-------------------------------------
Reporter: Charlie DeTar | Owner: Hasan
| Ramezani
Type: Bug | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"b36beec2086da34b7bb8fee0001edf47a41716fb" b36beec]:
{{{
#!CommitTicketReference repository=""
revision="b36beec2086da34b7bb8fee0001edf47a41716fb"
[3.2.x] Fixed #32332 -- Fixed loss of parent with non-numeric pk when
saving child after parent.
Follow up to 519016e5f25d7c0a040015724f9920581551cab0.
Backport of 7cba92ec55a5d05450261f375830619870ca84fa from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32332#comment:8>
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/066.e6f15b49e80b4241d1a3ce7600888289%40djangoproject.com.
