[Django] #24132: auth_permission name field is too short

11 views
Skip to first unread message

Django

unread,
Jan 11, 2015, 5:53:11 PM1/11/15
to django-...@googlegroups.com
#24132: auth_permission name field is too short
-------------------------------+--------------------
Reporter: mark0978 | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.auth | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------
CREATE TABLE `auth_permission` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(50) NOT NULL,
`content_type_id` int(11) NOT NULL,
`codename` varchar(100) NOT NULL,
)

codename and name are almost identical fields, except name has added
spaces and the string "Can" stuck in front of it. Why then is the
codename field varchar(100) and the name field varchar(50).

Right now this is causing me grief because one of the model names is long
enough to make the name field more than 50 characters.

Now that migrations are part of the core of Django, this should be easy to
fix.

--
Ticket URL: <https://code.djangoproject.com/ticket/24132>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Jan 11, 2015, 5:54:04 PM1/11/15
to django-...@googlegroups.com
#24132: auth_permission name field is too short
-------------------------------+--------------------------------------

Reporter: mark0978 | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.auth | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by mark0978):

* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0


Old description:

> CREATE TABLE `auth_permission` (
> `id` int(11) NOT NULL AUTO_INCREMENT,
> `name` varchar(50) NOT NULL,
> `content_type_id` int(11) NOT NULL,
> `codename` varchar(100) NOT NULL,
> )
>
> codename and name are almost identical fields, except name has added
> spaces and the string "Can" stuck in front of it. Why then is the
> codename field varchar(100) and the name field varchar(50).
>
> Right now this is causing me grief because one of the model names is long
> enough to make the name field more than 50 characters.
>
> Now that migrations are part of the core of Django, this should be easy
> to fix.

New description:

{{{


CREATE TABLE `auth_permission` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`name` varchar(50) NOT NULL,
`content_type_id` int(11) NOT NULL,
`codename` varchar(100) NOT NULL,
)
}}}


codename and name are almost identical fields, except name has added
spaces and the string "Can" stuck in front of it. Why then is the
codename field varchar(100) and the name field varchar(50).

Right now this is causing me grief because one of the model names is long
enough to make the name field more than 50 characters.

Now that migrations are part of the core of Django, this should be easy to
fix.

--

--
Ticket URL: <https://code.djangoproject.com/ticket/24132#comment:1>

Django

unread,
Jan 11, 2015, 7:44:23 PM1/11/15
to django-...@googlegroups.com
#24132: auth_permission name field is too short
-------------------------------+--------------------------------------
Reporter: mark0978 | Owner: nobody
Type: Uncategorized | Status: closed
Component: contrib.auth | Version: 1.7
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by MarkusH):

* status: new => closed
* resolution: => duplicate


Comment:

Duplicate of #8162. Fixed in 1.8

--
Ticket URL: <https://code.djangoproject.com/ticket/24132#comment:2>

Reply all
Reply to author
Forward
0 new messages