#10811: Assigning unsaved model to a ForeignKey leads to silent failures
-------------------------------------+-------------------------------------
Reporter: Glenn | Owner:
Type: Bug | anubhav9042
Component: Database layer | Status: assigned
(models, ORM) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timo):
It looks like you got to roughly the same place as Aymeric did in his
attempt to solve this (running into problems with InlineModelAdmin). I'm
not really inclined to look into it myself since Aymeric already tried and
it's not clear fixing this ticket will yield much benefit -- from an
earlier comment: "Jacob thinks that wontfixing on the basis that a) the
problem is complicated b) the current behavior might be useful isn't the
answer, because it's still a bug that can result in data loss, no matter
how much we document it."
--
Ticket URL: <https://code.djangoproject.com/ticket/10811#comment:22>
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/063.2004ba7b7585886be2b884177244b082%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
