Specify number column types (Fixes #316) #317
Merged
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
WaterlineJS defaults to using floating point field types for number fields. The causes precision issues for file sizes since the reported file sizes do not match the assets. This would also prevent the download count tracking to work once the count is high enough such that one download is beyond the supported precision. Note: users must update their existing database schemas to avoid these issues.
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.
WaterlineJS defaults to using floating point field types for number fields. The causes precision issues for file sizes since the reported file sizes do not match the assets. This would also prevent the download count tracking to work once the count is high enough such that one download is beyond the supported precision.
Note: users must update their existing database schemas to avoid these issues.