#9431: UNIQUE index on VARCHAR(256+) causes failure on MySQL 5.0 with InnoDB
tables, a slightly higher threshold for MyISAM
---------------------------------------------------+------------------------
          Reporter:  adamnelson                    |         Owner:  adamnelson
            Status:  new                           |     Milestone:            
         Component:  Database layer (models, ORM)  |       Version:  1.0       
        Resolution:                                |      Keywords:  mysql     
             Stage:  Accepted                      |     Has_patch:  0         
        Needs_docs:  0                             |   Needs_tests:  0         
Needs_better_patch:  0                             |  
---------------------------------------------------+------------------------
Comment (by adamnelson):

 I agree although I can't find anywhere where there is a minimum version
 number for MySQL on Django in any of the official docs or even in the base
 object.  After trudging through the lists, I see talk of deprecating MySQL
 4.0 nearly 2 years ago but it seems to be a dead topic.  Ostensibly MySQL
 3.23 would even work in the current codebase since MySQLdb supports it.  I
 honestly don't think that anybody could run Django 1.0 on MySQL 4.0 using
 many of the core Django apps currently out there without running into
 serious problems - mostly related to the lack of robust unicode support
 before 4.1.

 MySQL 4.1 would be the only reasonable minimum but virtually nobody is
 using it which is why I think MySQL 5.0 is the realistic minimum.  I'll
 send my previous email to the group as I can't imagine that anybody would
 be able to run Django 1.0 on MySQL 4.0 in a reliable fashion right now and
 MySQL 5.0 has been stable for 3 years.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/9431#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@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-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to