#13137: GenericForeignKey does not allow content type PK 0
-------------------------------------+-------------------------------------
Reporter: devesine | Owner: woodlee
Type: Bug | Status: assigned
Component: | Version: master
contrib.contenttypes | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: contenttype | Needs documentation: 0
genericforeignkey | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by ramiro):
I'd say close this ticket as ''wontfix'' because ContentType is an
'internal' model over which the user has no control so its IntegerField id
PK follows the usual semantics of a Django model regarding it having a
value of 0 meaning the model has no corresponding DB record.
So the only scenario in which CT could have a 0 PK is an edge-case one and
IMHO it's not worth to special-case PK semantics of CT for it.
--
Ticket URL: <https://code.djangoproject.com/ticket/13137#comment:14>
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 post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
