Fixed User.externalUsername column and creation on db #3583
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.
This PR fixes the definition of the
external_username
column onusr_user
table, which is incompatible with MySQL/MariaDB instances which have propertyinnodb_large_prefix
set toOFF
, which limits the max length of an index to 767 bytes. See MariaDB/MySQL documentationRelated Issue
This PR fixes #3523
Description of the solution adopted
Changed the Liquibase definition for the column.
Screenshots
None
Any side note on the changes made
Added also code argument validation to the length of
User.name
andUser.externalUsername
fields.