#33004: Inconsistent / Unexpected handling of assigning unsaved model to Generic
Foreign Key
-------------------------------------+-------------------------------------
Reporter: Finn Andersen | Owner: Jonny
| Park
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: fk, gfk, generic | Triage Stage: Accepted
foreign key, validation |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:8 wtzhu]:
> The code I defined is as follows. I have verified that the data already
exists in the database after I save the object of Grade, but I can not use
it to save the object of Stu.
This is not related with `GenericForeignKey` please create a separate
ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/33004#comment:9>
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/068.5b072805c10f421ef70a21aa6012794f%40djangoproject.com.
