I opened up a ticket regarding a bug in the django-app-plugin with regards to the indexed CharField being too large for MySQL 5.0:
http://code.google.com/p/django-app-plugins/issues/detail?id=11 I think that maybe Django's handling of this should be examined more generally for one of the following options. 1) Django should disallow CharFields max-length>255. 2) Django should silently use TEXT as the datatype when CharField is greater than 255. 3) Django should silently use TEXT as the datatype when CharField is greater than 255 and max-length>255. 3) Django should disallow unique=true and max-length>255. Other thoughts? I literally just moved over from PHP this week so I'm probably not in a great position to be committing patches although I'm fine with that. Otherwise, I would appreciate feedback and a direction on this. Thanks, Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
