#9347: verbose_name option is missing in Model Field reference
------------------------------------+---------------------------------------
Reporter: marcoberi | Owner: nobody
Status: new | Milestone: post-1.0
Component: Documentation | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Comment (by ramiro):
Karen,
Replying to [comment:4 kmtracey]:
> Any field can have a verbose_name specified. Not sure why you think it
is restricted to relationship fields? The difference between specifying
it for non-related and related is you ''may'' simply specify it as the
first positional argument for any field that is not a !ForeignKey,
!ManyToManyField or !OneToOneField; that is you are not required to use
the verbose_name keyword. But you certainly can.
It' because the wording used here:
http://docs.djangoproject.com/en/dev/topics/db/models/#verbose-field-names
I know that, strictly speaking, that section doesn't say ''normal'' fields
don't support `verbose_name` but it only mentions they support usage of
the first positional argument and contrast them agains the
''relationship'' fields. I hadn't looked up at the code that's why I
wrote `AFAIK`.
--
Ticket URL: <http://code.djangoproject.com/ticket/9347#comment:5>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
