The specific problem was already fixed at http://code.google.com/p/django-app-plugins/issues/detail?id=11
I was speaking of the more general problem about what Pinax's stance with regards to these type of limitations. From the limited feedback, it sounds like our minimum standard will be UTF8 for all applications - which means that apps/libs that can't work on the current stable MySQL using the UTF8 character set would have to be patched in order to be included. As for the indexing of the hash, I think that's kind of overkill. It would reduce the column (including index) size by about 3/4 but it would add processing overhead . Anyway, this is only a table used to hold no more than 100 records since it's just a glue table to connect plugins to eachother. Still, I don't own the app so I don't have write privileges to it. It's bundled into Pinax :-) Thanks, Adam On Oct 19, 11:58 pm, Ian Holsman <[EMAIL PROTECTED]> wrote: > With MySQL it depends on the character set you are creating the table with. > for example with mysql 5.0.45: > > mysql> create table foo ( x varchar(999), primary key (x)) character set > = 'latin1'; > Query OK, 0 rows affected (0.00 sec) > > mysql> create table foo2 ( x varchar(999), primary key (x)) character > set = 'utf8'; > ERROR 1071 (42000): Specified key was too long; max key length is 999 bytes > > mysql> create table foo2 ( x varchar(255), primary key (x)) character > set = 'utf8'; > Query OK, 0 rows affected (0.01 sec) > > So.. if you can live without the benefit of UTF8 you can achieve your > result. > > personally I think you should look at your DB-design, as indexes on > large fields are expensive in terms of space used and time to retrieve > results. you could possibly index the MD5 of the field (32 bytes), and > then search for duplicates on that key. it might be faster and cheaper > on the disk. > > regards > Ian > > Dj Gilcrease wrote: > > The max length of a varchar field is Database dependent > > > MySQL it is 255 > > MSSQL it is 2^31-1 (2gb) > > PostgreSQL it is ~ 2^20-1 (1gb) > > > MySQL 4.1 and greater supposedly changes any varchar or char field > > with a max length or greater to 255 to a TEXT field which can hold ~ > > 1gb > > > Dj Gilcrease > > OpenRPG Developer > > ~~http://www.openrpg.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
