queryparam measures maxlength based on character length instead of byte length
Description
queryparam measures maxlength based on character length instead of byte length, problem with that is that a "varchar(255)" is based byte length what of course can differ.
For that we need also an attribute "charset" that allows to define the target charset used for the column.
Environment
None
Activity
Show:
Michael Offner
August 15, 2020, 12:36 AM
we also use the attribute charset to validate the string against that charset, so is the string compatible with that charset.
Michael Offner
August 15, 2020, 12:59 AM
Michael Offner
August 15, 2020, 2:18 AM
if charset is not set, it works the old way for backward compatibility.
Fixed
Assignee
Reporter
Priority
Labels
Fix versions
Sprint
5.3.8 Sprint 3