BIGINT fields no longer returned as strings#255
Closed
chesles wants to merge 1 commit intomysqljs:masterfrom
chesles:master
Closed
BIGINT fields no longer returned as strings#255chesles wants to merge 1 commit intomysqljs:masterfrom chesles:master
chesles wants to merge 1 commit intomysqljs:masterfrom
chesles:master
Conversation
Contributor
|
-1 BIGINT is an 8-byte field. Once you reach a certain value, JavaScript's Number will start losing precision for integers. The only way to guarantee exact representation is by using a string. |
Author
|
Hmm. That's something I should have realized... hangs head in shame. |
dveeden
pushed a commit
to dveeden/mysql
that referenced
this pull request
Jan 31, 2023
Fix handling of queries without columns and rows
This file contains hidden or 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
2 participants
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.
No description provided.