[client-v2] fixed number conversion in reader #1856
Merged
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.
Summary
This PR implement conversion between different number types. Today client API (readers) allow to get column value only in the type it is defined in a DB. It is very inconvenient because requires to follow schema very strictly. So this PR relaxes this rule and lets to:
int
,int32
aslong
.int32
value like1000
can be read asshort
but not asbyte
.Closes: #1852
Checklist
Delete items not relevant to your PR: