Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

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 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 MaxLenghtValidator with something that measures the byte length 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 MaxLenghtValidator MaxLengthValidator with something that measures the byte length of the string.

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

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

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.

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