Revision history  [back]

edit: fixed There is a check like that, but in the repository, will be in version 0.7.40.

In encoded unicode characters byte length and the character count string length are not the same.same, we need to solve this problem.

In your case the unicode string is below the character count limit and the byte length is above, so the first check passes, but on the level of database it fails and you get an internal server error.

Now adjusted We need to replace the input MaxLengthValidator with something that measures the byte length validator.of the string.

There is a check like that, but in unicode characters byte length and the string length are not the same, we need to solve this problem.

In your case the unicode string length is below the character count limit and the byte length is above, so the first check passes, but on the level of database it fails and you get an internal server error.

We need to replace the MaxLengthValidator MaxLenghtValidator with something that measures the byte length of the string.