db0a7fe91d
With MySQL 5.6 setup to use UTF-8 for everything, the 033 migration will fail. This is because a VARCHAR(256) cannot be indexed in UTF-8 databases. In versions of MySQL before 5.6, this produced a warning and a truncated, less-useful index. In 5.6 it was changed to an error. We will reduce these columns further to 64 bytes in the model in a subsequent fix. For now, we will just create the table with 64 character columns on new systems, which will allow this migration to work properly on mysql-5.6. There is no danger of overflow, as 64 chars is what Keystone uses for them anyway. Change-Id: I27b9c61828301ba8c392b3d316f656641af753bc Closes-Bug: #1316646 |
||
|---|---|---|
| .. | ||
| sqlalchemy | ||
| __init__.py | ||
| api.py | ||
| sync.py | ||
| utils.py | ||