Naturalization of names resulting in >100 characters causes shcema migration to fail #4166
Labels
status: accepted
This issue has been accepted for implementation
type: bug
A confirmed report of unexpected behavior in the application
Environment
Steps to Reproduce
Expected Behavior
All migrations should complete successfully.
Observed Behavior
The migration
0095_primary_model_ordering
fails with the following error:This happens because the name "1a1a1a1a1a1a1a1a1a1a1a1a1a1a1a" expands to a string greater than 100 characters in length, which is the maximum length for the database field. The naturalization function accepts an argument to cut the naturalized string to a specific length, however the parameter is not being passed by the migration function.
It should be noted that this can be reproduced with any model using naturalized ordering if the source name is constructed in such a way that its naturalized version exceeds 100 characters.
The text was updated successfully, but these errors were encountered: