How about we raise a validation error on UNIQUE CharField fields greater than 255 characters for all MySQL 5.0 implementations.
I think the docs should be updated as well telling people that it's not best practice to use CharField for fields that need more than 255 characters (or at least put a note in there so MySQL users no that they can't mix 255+ character CharField and UNIQUE). Even from a typical web usage standpoint, it seems that fields with more than 255 characters are better handled under the TextField model. The only reason I'm trying to be a stickler about this is because this code is ending up in what are meant to portable external libraries (django-app-plugins) that are being redistributed into larger projects (pinax). I'll move to Postgres today :-) Thanks, Adam On Oct 16, 7:18 pm, "Dj Gilcrease" <[EMAIL PROTECTED]> 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 -~----------~----~----~----~------~----~------~--~---
