#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 robinh00d): Running the failed testcase mentioned in the description raises an integrity error. {{{django.db.utils.IntegrityError: NOT NULL constraint failed: many_to_one_child.parent_id}}}. This is working as intended. I believe this can be closed as it was fixed by #29896 -- Ticket URL: <https://code.djangoproject.com/ticket/28147#comment:7> 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.847ea399fac4a31ff3c8a3e8dd5b0c1c%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.