RenameIndexOperation bug
Posted: Tue 13 Jan 2015 12:27
Hello.
We have found bug in processing of RenameIndexOperation migration operation. Index names (old and new) are always modified to contain table name regardless of their values and source (default index name or manually specified). So index 'IX_BLABLABLA' becomes 'IX_TABLENAME_BLABLABLA'.
In our migrations we manually provide index names to conform Oracle name length limit and to control resulting names format.
Migration02:
CreateIndex(@"CityInventory.NonResidentals", @"LegalMode_Id", name: @"IX_NonResidentals_LegalMode_Id");
Migration03:
RenameIndex(table: @"CityInventory.NonResidentals", name: @"IX_NonResidentals_LegalMode_Id", newName: @"IX_NonResidentals_LegalModeId");
And third migration cannot be applied due to transformed name 'IX_NonResidentals_NonResidentals_LegalMode_Id' exceeded name length limit.
Can you fix this bug or add workarounds flag for this issue?
Regards,
Alexey.
We have found bug in processing of RenameIndexOperation migration operation. Index names (old and new) are always modified to contain table name regardless of their values and source (default index name or manually specified). So index 'IX_BLABLABLA' becomes 'IX_TABLENAME_BLABLABLA'.
In our migrations we manually provide index names to conform Oracle name length limit and to control resulting names format.
Migration02:
CreateIndex(@"CityInventory.NonResidentals", @"LegalMode_Id", name: @"IX_NonResidentals_LegalMode_Id");
Migration03:
RenameIndex(table: @"CityInventory.NonResidentals", name: @"IX_NonResidentals_LegalMode_Id", newName: @"IX_NonResidentals_LegalModeId");
And third migration cannot be applied due to transformed name 'IX_NonResidentals_NonResidentals_LegalMode_Id' exceeded name length limit.
Can you fix this bug or add workarounds flag for this issue?
Regards,
Alexey.