On Tue, 2006-09-19 at 20:54 +0000, gkelly wrote:
> I think this may be a bug (or feature request).
>
> If I define a ForeignKey field 'my_field' in a class and set
> Meta.list_display = ('my_field','other_field') and Meta.verbose_name =
> 'My Verbose Field'
>
> then in the Admin site, the heading for 'my_field' doesn't use the
> verbose_name, but rather the python variable name for the ForeignKey
> field.
> I think it should use the verbose_name. Is there a reason it can't?
There are a few reasons it can't/shouldn't behave like that:
Firstly, because it would be inconsistent. All fields take an optional
first positional argument that is the verbose name to use for that
field. This is true for ForeignKey fields just as for all other fields.
If you don't specify that name, it will use the name of the attribute in
the model, just as you are seeing.
Secondly, we can't use the model name by default because you might have
more than one ForeignKey in the model pointing to the other model, so
there would be an immediate name consufion.
Finally, you have named the attribute the way you have for a reason. If
you wanted to name it after the target class, you would have done so, so
we respect the attribute naming choice you made.
If you always want the display name to track the related model's name,
you could probably set it to OtherModel.Meta.verbose_name and it would
work, I suspect, if you want the two to always track each other.
Cheers,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@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-users
-~----------~----~----~----~------~----~------~--~---
