You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The newly added CHAR datatype is a little bit poorly mapped.
For now it seem to be an alias for UINT16, since it is represented as an integer in all formats, including
e.g. JSON and XML, where it should have been a char, e.g. 'A' instead of 65.
If the reason for adding it is to simply map the Java types char/Character, then those could have been added to UINT32 as valid Java datatypes, just as e.g. ENUM allows for both int and enum to be bound.
If the reason for adding it is to truly have a new data type, then CHAR should be encoded as a character in the text formats, i.e. JSON and XML.
The newly added CHAR datatype is a little bit poorly mapped.
For now it seem to be an alias for UINT16, since it is represented as an integer in all formats, including
e.g. JSON and XML, where it should have been a char, e.g. 'A' instead of 65.
If the reason for adding it is to simply map the Java types char/Character, then those could have been added to UINT32 as valid Java datatypes, just as e.g. ENUM allows for both int and enum to be bound.
If the reason for adding it is to truly have a new data type, then CHAR should be encoded as a character in the text formats, i.e. JSON and XML.