#27377: Clarify that prepopulated_fields doesn't work with OneToOneField
-------------------------------------+-------------------------------------
Reporter: Malik A. Rumi | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
prepopulated_fields, admin.py |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* needs_better_patch: => 0
* needs_tests: => 0
* easy: 0 => 1
* needs_docs: => 0
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
`OneToOneField` is a subclass of `ForeignKey`, so as far as I see,
[https://github.com/django/django/blob/f734e2d4b2fc4391a4d097b80357724815c1d414/django/contrib/admin/checks.py#L399-L406
a system check error] will occur. I guess the error message could be
clarified since it confused you.
As far as getting answers to usage questions goes, please
[wiki:TicketClosingReasons/UseSupportChannels].
--
Ticket URL: <https://code.djangoproject.com/ticket/27377#comment:1>
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.50ccc9a4f07ad40d6939da0d24d5fc2c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.