#18866: model Meta verbose_name too long error message not obvious
------------------------------+------------------------------------
Reporter: elena | Owner: toyg
Type: Bug | Status: closed
Component: contrib.auth | Version: 1.4
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+------------------------------------
Changes (by joaoxsouls <joaoxsouls@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"1ab27e9a65015373a49688f3ff6723cf85d5de56"]:
{{{
#!CommitTicketReference repository=""
revision="1ab27e9a65015373a49688f3ff6723cf85d5de56"
Fixed #18866 -- added validation error for verbose_name longer than 39
characters
Added a validation error check when creating the permissions for model, to
avoid
cryptic database error when the verbose_name is longer than 39 characters
thanks elena for reporting it
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/18866#comment:14>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.c8c47deff035132cc535aba72bd8fe30%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
