#27377: Clarify that prepopulated_fields doesn't work with OneToOneField
-------------------------------------+-------------------------------------
Reporter: Malik A. Rumi | Owner: Henry
Type: | Dang
Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.10
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
prepopulated_fields, admin.py |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"12c1d6fe8f03f068f6010e3c8e0f441bf2567e7c" 12c1d6f]:
{{{
#!CommitTicketReference repository=""
revision="12c1d6fe8f03f068f6010e3c8e0f441bf2567e7c"
Refs #27377 -- Fixed reverse query name clash in test model.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27377#comment:10>
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/067.8e4e2cec3eac4e5ab14eab0074888857%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
