#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: 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:"266e7e0eccf1d109e8c64c7bc5e612a538ad618a" 266e7e0e]: {{{ #!CommitTicketReference repository="" revision="266e7e0eccf1d109e8c64c7bc5e612a538ad618a" Refs #28147 -- Added test for saving nullable ForeignKey with to_field attribute after saving parent. }}} -- Ticket URL: <https://code.djangoproject.com/ticket/28147#comment:13> 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.ed37d72029e789e03f394c6ea1b7d78c%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.