[CBRD-25018] In case of unsigned tinyint in mysql and mariadb, error … #4706
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
http://jira.cubrid.org/browse/CBRD-25018
Purpose
In the case of unsigned tinyint in mysql and mariadb, an error occurred when retrieving the value as smallint type.
When the Gateway requested a value from ODBC, it requested a smallint. At this time, if the value was 127 or higher, 0xFF was added in front of the value and an incorrect value was delivered.
For example, if you input 225 into unsigned tinyint and read the value, it should return 225 (0xE1), but in reality, it returns 65505 (0xFFE1).
For reference, values 1 to 127 are returned as 1(0x01) to 127(0xF7).
In the case of unsigned tinyint, when requesting a value from ODBC, it needs to be changed to request tinyint.
Implementation
N/A
Remarks
N/A