#22048: Document ways of checking for OneToOneField
--------------------------------------+------------------------------------
Reporter: EvilDMP | Owner: code22
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed
Keywords: afraid-to-commit | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"ec08d62a20f55cfdfb9fbd21d8bc5627c54337c7"]:
{{{
#!CommitTicketReference repository=""
revision="ec08d62a20f55cfdfb9fbd21d8bc5627c54337c7"
Fixed #22048 - Enhanced docs to cover nonexistent one-to-one
relationships.
Thanks EvilDMP for the suggestion.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/22048#comment:7>
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.714d937bcbad4921853f3d18d72198fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
