#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: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
That makes sense. I went through the
[https://github.com/django/django/pull/8434/files#diff-
507b415116b409afa4f723e41a759a9eR665 PR proposed here] and I noticed the
`.pk` usage was probably missing `to_field` usages.
I guess we could add a regression test for the nullable foreign key case
though
e.g.
{{{#!python
author = Author()
book = Book(nullable_author=author)
author.save()
book.save()
}}}
Thoughts on that robinh00d?
--
Ticket URL: <https://code.djangoproject.com/ticket/28147#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.23647aaf7b7d2e6868a753287297c12c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
