fix: 🐛 multibyte object name causes error #895
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.
Context
Multi byte character handling
Problem
Oracle database allows multi byte characters in object names such as sequences, so if I try to use multi byte characters in sequence names, an exception will be thrown due to the handling of multi byte characters.
I know it should not use multi byte character in any object name but sadly my recent work environment using multi byte object name.
How to reproduce
Set oracle server character set to
JA16SJISTILDE
Create migration file like below
Solution
mb_substr
instead ofsubstr
. Because it handles both unicode character and ascii character properly.