#28147: Saving parent object after setting on child leads to unexpected data
loss
-------------------------------------+-------------------------------------
Reporter: Erwin Junge | Owner: robinh00d
Type: Bug | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by robinh00d):
* needs_better_patch: 1 => 0
Comment:
Disregard my comment above, I just realised I tested everything wrong.
`class child` in `many_to_one/models` does not have a nullable parent.
I've ran the test again and the outcome is as described in the
description.
I have made updates to the previously proposed PR to rectify the issue.
I have submitted the PR:
[https://github.com/django/django/pull/11383 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/28147#comment:10>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.99ac1b0eba40842e71adf2c467636ac8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
