Changes between Initial Version and Version 1 of Ticket #24410, comment 5


Ignore:
Timestamp:
Feb 27, 2015, 8:02:58 AM (9 years ago)
Author:
László Károlyi

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #24410, comment 5

    initial v1  
    22
    33To clarify the workflow to reproduce this bug:
    4 - MySQL will emit the error mentioned above. In order to have that warning with the traceback and the failing migration avoided, I need to create the index manually with a `migrations.RunSQL` statement (stated above too).
     4- MySQL will emit the warning mentioned above. In order to have that warning with the traceback and the failing migration avoided, I need to create the index manually with a `migrations.RunSQL` statement (stated above too).
    55- When I try to use the same index name Django created so it'll be recognized by migrations, the `hash()` related bug comes into picture, causing the hash names to be unpredictable each time.
    66
Back to Top