Fix enumMigration not working on long fieldNames #8708
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
Some users were facing issues while updating SELECT or MULTISELECT options:
Root cause
Internally, while migrating enum values, we are doing:
oldColumnName being:
${columnDefinition.columnName}_old_${v4()}
;However, TypeORM only supports 63 bits identifiers: typeorm/typeorm#3118, but silently truncate the identifer so if oldColumnName gets larger than 63 characters,
value[oldColumnName]
is undefined.Fix
We only need a temporary and unique temporary name, no need to take into account the previous columnName here