-
Notifications
You must be signed in to change notification settings - Fork 1.4k
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[finagle-mysql] finagle-mysql 6.25.0: Can not read UNSIGNED INT columns correctly #438
Comments
@fab-soundcloud good catch! Unfortunately, we don't have a ton of bandwidth right now, but we'd love to shepherd your PR through 👍 |
Hi @mosesn, I am willing to solve this issue, now working on it. |
@mehmetgunturkun it looks like I can only assign it to committers, but feel free to start working on it! I'll just mark it as "in progress". Thanks, and welcome to the project! |
Hi @mosesn, I guess I solved the issue but before creating a pull request there are several things that I want to ask:
P.S. Sorry if I shouldn't have written these into issueç |
This got fixed a little while back. See this unit test for an example. |
Given this table:
with this data:
Trying to load that row with finagle mysql via pseudo code:
results in this value being available in the pattern matching:
It looks like mysql-finagle does not understand UNSIGNED int's which should result in a LongValue() or at least a Long java/scala representation. It always parses an Int which MaxValue is:
The problematic code I guess is this:
https://github.com/twitter/finagle/blob/develop/finagle-mysql/src/main/scala/com/twitter/finagle/mysql/Row.scala#L74
Expected behaviuor would be the that I can successfully read the value 4294967295 back somehow.
The text was updated successfully, but these errors were encountered: