#28147: Saving parent object after setting on child leads to unexpected data
loss
-------------------------------------+-------------------------------------
Reporter: Erwin Junge | Owner: robinh00d
Type: Bug | Status: closed
Component: Database layer | Version: master
(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 felixxm):
Jon, thanks for the report. I agree that this behavior has changed, but
I'm not sure how we should deal with this.
[https://docs.djangoproject.com/en/2.2/ref/models/fields/#database-
representation Docs ] says that ''"your code should never have to deal
with the database column name"''. I'm not sure if will be able to fix this
without reverting this patch and whether we should. Any ideas?
--
Ticket URL: <https://code.djangoproject.com/ticket/28147#comment:16>
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/068.79b677503331f6f7a0c8cef7c6391b1f%40djangoproject.com.
