Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.0.2, 1.1.2
-
None
Description
Depending on value Byte parameter could cause use of array index out of the range.
getByte also has problem of returning correct value in case of binary field.
This problem was reported in this PR
The fix and testcases have been pushed. There was an error with setByte method causing crash during query execution because of wrong >> operation resulting in wrong array index.
Also, the counterpart method - getByte had error, along with all other integer getters. In case of binary data they tried to read it as a string and convert to string as integer, and thus returning wrong values