Skip to content
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

bigint unsigned column display loss of precision #334

guerbai opened this issue Aug 19, 2019 · 2 comments


Copy link

commented Aug 19, 2019

Describe the bug
value 6684121293811353602 display in results is 6684121293811354000

To Reproduce
Steps to reproduce the behavior:

  1. create a table with bigint unsigned column id
  2. insert a row with id 6684121293811353602
  3. run select id from table where id=6684121293811353602

Expected behavior
value 6684121293811353602 display in result is 6684121293811353602


Desktop (please complete the following information):

  • SQLTools Version: 0.20.2
  • VSCode Version: 1.34.0
  • Dialect Used/Version: Mysql5.7.23
  • OS: Mac

@guerbai guerbai added the triage label Aug 19, 2019

@guerbai guerbai changed the title int64 display loss of precision bigint unsigned column display loss of precision Aug 19, 2019

@mtxr mtxr added bug mysql and removed triage labels Aug 24, 2019

@mtxr mtxr self-assigned this Aug 24, 2019

@mtxr mtxr added this to To do in Kanban via automation Aug 24, 2019


This comment has been minimized.

Copy link

commented Aug 24, 2019

Confirmed. Will be fixed and release in the next version. (~1 day)

@mtxr mtxr closed this in a9edf43 Aug 24, 2019

Kanban automation moved this from To do to To be released Aug 24, 2019


This comment has been minimized.

Copy link

commented Aug 28, 2019

Thank you, waiting next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.