auth framework shouldn't write verbose_name values in permission tables but actual model names

[akat.metin@…]

django.contrib.auth framework's writes it's permissions in a column of type varchar(50). This caused quite a lot of troubles until I figured out that it doesn't write there the actual model names, but the value of class Meta: verbose_name. Aren't verbose names just for that reason - to be able to grow quite long?

[Simon Greenhill]

Well, it's verbose_name not write_me_an_essay, but I'll see what others think.

[Russell Keith-Magee]

The purpose of verbose name is to provide a human readable name when the demagicked model name doesn't work, especially with respect to case and spacing. As such, verbose name and the model name should always be of approximately the same length. If you've got model names hitting 50 characters, I pity your users :-)