Code

Changes between Initial Version and Version 1 of Ticket #18866, comment 10


Ignore:
Timestamp:
09/23/13 06:58:35 (7 months ago)
Author:
toyg
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18866, comment 10

    initial v1  
    33The problem is that verbose_name is used to generate the auth_permission table; the "name" field in that table is set to varchar(50) (at least on PostgreSQL), but this record actually includes sentences ("Can add <verbose_name>", "Can delete <verbose_name>" and so on); so '''the actual practical limit is 39 characters for verbose_name'''. This is a weird number, common knowledge is that verbose_name can be up to 50 characters.  
    44 
    5 So the real fix is either to widen that field to 61 or more (50 + "Can delete ", which is 11 characters), or document that the limit is 39 on non-sqlite backends. 
     5So the real fix is either to widen that field to 61 or more (50 + "Can delete ", which is 11 characters), or document that the limit is 39 on non-sqlite backends (sqlite doesn't really enforce limits to text fields). 
    66 
    77I have a test and a fix for the validator to spot values that are too long, but there's no point in submitting a pull request if this point isn't settled first.