#33004: Inconsistent / Unexpected handling of assigning unsaved model to Generic
Foreign Key
-------------------------------------+-------------------------------------
Reporter: Finn Andersen | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: fk, gfk, generic | Triage Stage: Accepted
foreign key, validation |
Has patch: 0 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Finn Andersen):
* needs_docs: 0 => 1
* needs_tests: 0 => 1
Comment:
I think verification should be done upon save() not assignment (to align
with existing behaviour for FKs and enable saving of related model at
later point before calling save() of primary model)
--
Ticket URL: <https://code.djangoproject.com/ticket/33004#comment:3>
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.6b00cde4ba690871b23b4eaf9c7c1a77%40djangoproject.com.
