#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 YashRaj1506):
My question here is, having Foreignkey keep a unsaved object, is this a
behaviour we should keep? should this raise a error too when saved with
`save()` ? or we need to adapt the behaviour of `genericforeignkeys` so
that it can also keep an unsaved object? I just looked at this ticket, so
i lack a bit more deeper depth into this problem. I will do my research
but i am open to other peoples opinion on this.
--
Ticket URL: <https://code.djangoproject.com/ticket/35965#comment:5>
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/010701940a41ff1c-40a51ac7-3c6c-4cf6-aca0-20a8d4010341-000000%40eu-central-1.amazonses.com.
