#35965: GenericForeignKeys lose the assigned unsaved object after the object is
saved
-------------------------------------+-------------------------------------
Reporter: Willem Van Onsem | Owner:
| YashRaj1506
Type: Bug | Status: assigned
Component: | Version: 5.1
contrib.contenttypes |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Clifford Gama):
We allow model instances to reference unsaved objects, even though saving
them isn't permitted, because this behavior is essential for use cases
like inline formsets, where related objects can be linked to an instance
that is being created in another form.
--
Ticket URL: <https://code.djangoproject.com/ticket/35965#comment:6>
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 visit
https://groups.google.com/d/msgid/django-updates/01070195cd0b8ab9-dcd9b485-7e1f-4afc-b35f-e84c0366f6f8-000000%40eu-central-1.amazonses.com.
