MySQL DB creation fails because of key length
|Assignee:||Carlos Martín||% Done:|
|Category:||Core & System|
|Target version:||Release 3.2 - S0|
|Affected Versions:||OpenNebula 3.0|
As reported in the mailing list, the MySQL DB bootstrap fails for some installations.
The proposed solution is to change the size of some text columns:
Another way to solve this may be setting the charset to latin1, because the key length depends on the number of bytes per character.
Bug #848: Set name columns to 128 chars. The name length is checked for new objects
Bug #848: Add 3.1.0 migrator, it will truncate existing names with more than 128 chars.
#1 Updated by Robert Hennig about 8 years ago
I don't think that setting the charset to latin1 is a proper solution as Latin1 does not contain all required chracters for some languages (compared to UTF-8).
I don't know much about the code so I can't tell if there is a real reason for these fields to be 256 chars long instead of 255. But if there is no real reason it would be best to just reduce the field sizes by one char.