#33004: Inconsistent / Unexpected handling of assigning unsaved model to Generic
Foreign Key
-------------------------------------+-------------------------------------
Reporter: Finn Andersen | Owner: Sarah
| Boyce
Type: Bug | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: fk, gfk, generic | Triage Stage: Ready for
foreign key, validation | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"cd4da34fc1f1df08f593e461b2f670bfd61d0d2f" cd4da34f]:
{{{
#!CommitTicketReference repository=""
revision="cd4da34fc1f1df08f593e461b2f670bfd61d0d2f"
Fixed #33004 -- Made saving objects with unsaved GenericForeignKey raise
ValueError.
This aligns to the behaviour of OneToOneField and ForeignKey fields.
Thanks Jonny Park for the initial patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33004#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701804b861b33-cac679b4-1366-40d5-ba5b-d0c6e274e62c-000000%40eu-central-1.amazonses.com.
