Opened 17 years ago

Closed 14 years ago

#4748 closed (wontfix)

contrib.auth: Increase length of names of permissions

Reported by: Thomas Güttler <hv@…> Owned by: nobody
Component: contrib.admin Version: dev
Severity: Keywords: dbchange
Cc: remco@…, hv@… Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: yes Patch needs improvement: yes
Easy pickings: no UI/UX: no



here is a small patch to increase the length of permission names. We
hit 53 characters. 100 should be save.

Attachments (1)

models_py.diff (565 bytes ) - added by Thomas Güttler <hv@…> 17 years ago.

Download all attachments as: .zip

Change History (11)

by Thomas Güttler <hv@…>, 17 years ago

Attachment: models_py.diff added

comment:1 by Thomas Güttler <hv@…>, 17 years ago

Component: UncategorizedAdmin interface
Has patch: set
Owner: changed from Jacob to Adrian Holovaty

comment:2 by Adrian Holovaty, 17 years ago

This is technically a backwards-incompatible change to the database table layout, so if we do this, we'll have to provide instructions for people to convert their tables.

comment:3 by Simon G. <dev@…>, 17 years ago

Summary: contrib/auth: Increase length of names of permissionscontrib.auth: Increase length of names of permissions
Triage Stage: UnreviewedDesign decision needed

comment:4 by James Bennett, 17 years ago

#4129 was a duplicate, but also has a patch.

comment:5 by remco@…, 17 years ago

Cc: remco@… added

comment:6 by Jacob, 17 years ago

Keywords: dbchange added
Triage Stage: Design decision neededAccepted

comment:7 by Thomas Güttler, 16 years ago

Cc: hv@… added

comment:8 by Thomas Güttler, 16 years ago

If you don't want to modify django code, you can use a post_syncdb signal hook.

I created a django snippet, to increase the length after syndb is run:

comment:10 by Adam Nelson, 14 years ago

Needs tests: set
Patch needs improvement: set
Triage Stage: AcceptedReady for checkin

Test should be updated with 50+ character permission name

comment:11 by Malcolm Tredinnick, 14 years ago

Resolution: wontfix
Status: newclosed

This would cause problems for every single existing installation of this application (since the underlying database would need to be changed). Changing model field constraints is only to be done if no other option is available. In this case, we're not at that point yet.

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