Opened 8 years ago

Closed 8 years ago

#7375 closed (wontfix)

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

Reported by: akat.metin@… Owned by: nobody
Component: Contrib apps Version: master
Severity: Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

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?

Change History (2)

comment:1 Changed 8 years ago by Simon Greenhill

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset
Triage Stage: UnreviewedDesign decision needed

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

comment:2 Changed 8 years ago by Russell Keith-Magee

Resolution: wontfix
Status: newclosed

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 :-)

Note: See TracTickets for help on using tickets.
Back to Top