#17573: Documentation misses MySQL 5.5 switch InnoDB as default storage engine
----------------------------------------+--------------------
Reporter: Lenz Hirsch <hirsch@…> | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.3
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------------+--------------------
The Django documentation states here
https://docs.djangoproject.com/en/1.0/ref/databases/#storage-engines "The
default engine is MyISAM ...". This is not true since MySQL Version 5.5.
InnoDB is the default now. See: http://dev.mysql.com/doc/refman/5.5/en
/innodb-default-se.html
In consequence also manage.py syndb creates InnoDB tables by default.
This can lead to misleading error messages of manage.py (which is not the
fault of manage.py) like:
Failed to install index for ... model: Specified key was too long; max key
length is 767 bytes
Although this messages indicates the index could not be installed it is!
The index gets automatically shortened to 255 bytes and is therefore no
full "covering index" but a "prefix index" which seams not to be a real
performance issue.
Maybe some of these facts could be incorporated to the django
documentation to help MySQL users that will tend to stumble about this
error more often the more MySQL 5.5 is used.
--
Ticket URL: <https://code.djangoproject.com/ticket/17573>
Django <https://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
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
