Opened 16 years ago
Closed 13 years ago
#4748 closed (wontfix)
contrib.auth: Increase length of names of permissions
Reported by: | 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 |
Description
Hi,
here is a small patch to increase the length of permission names. We
hit 53 characters. 100 should be save.
Attachments (1)
Change History (11)
Changed 16 years ago by
Attachment: | models_py.diff added |
---|
comment:1 Changed 16 years ago by
Component: | Uncategorized → Admin interface |
---|---|
Has patch: | set |
Owner: | changed from Jacob to Adrian Holovaty |
comment:2 Changed 16 years ago by
comment:3 Changed 16 years ago by
Summary: | contrib/auth: Increase length of names of permissions → contrib.auth: Increase length of names of permissions |
---|---|
Triage Stage: | Unreviewed → Design decision needed |
comment:5 Changed 16 years ago by
Cc: | remco@… added |
---|
comment:6 Changed 15 years ago by
Keywords: | dbchange added |
---|---|
Triage Stage: | Design decision needed → Accepted |
comment:7 Changed 15 years ago by
Cc: | hv@… added |
---|
comment:8 Changed 15 years ago by
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 Changed 13 years ago by
Needs tests: | set |
---|---|
Patch needs improvement: | set |
Triage Stage: | Accepted → Ready for checkin |
Test should be updated with 50+ character permission name
comment:11 Changed 13 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
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.
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.