On Fri, 2008-10-17 at 06:25 -0700, adamiis111 wrote: > Malcom, > > Thanks for the well-explained response. It's a bit more complicated > than that though as this is only an issue if the field uses a UNIQUE > index. It is an issue up through the latest and greatest stable MySQL > (tested on 5.0.45 and no bug fixes at MySQL up through 5.0.67) and "./ > manage.py validate" triggers 0 errors with a model using > CharText(255+) and UNIQUE and using the mysql database type.
Then you should open a ticket, even better if it includes a patch, so that behaviour similar to that already in django/db/backends/mysql/validation.py is done for those fields and those MySQL versions as well. Again, MySQL-specific validation is quite appropriate here. > > As an aside, are most people using Postgres? Who knows? There's no way of answering a question like that reliably. Also, raw numbers don't tell the whole story, since the usefulness of a database backend varies depending on the domain it's being used in. > Should I switch to that > for the best tested database for Django? *shrug* MySQL is a supported backend for Django. Bugs in Django's support of MySQL should be fixed and if we aren't throwing and error for the case you describe and if it is a real limitation of MySQL, we should be doing so, as mentioned above. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
