-
Notifications
You must be signed in to change notification settings - Fork 141
SNOW-2866776: add private var in numeric type #4022
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
d2649c3
add private var in numeric type and test
sfc-gh-yuwang 6065ebf
add private var in numeric type and test
sfc-gh-yuwang 7b8960e
add test
sfc-gh-yuwang eacb904
add feature flag to control
sfc-gh-yuwang 0defc75
modify __eq__ instead of feature flag
sfc-gh-yuwang 5d61d3d
remove reduntant code
sfc-gh-yuwang ac2e712
remove reduntant
sfc-gh-yuwang 1be3e95
fix tests
sfc-gh-yuwang 3ee94c5
move to _integraltype
sfc-gh-yuwang 20735a1
address comments
sfc-gh-yuwang 13ebe54
add test
sfc-gh-yuwang 8ad136a
add test
sfc-gh-yuwang e508e83
add eq function to timedelta
sfc-gh-yuwang 692ad3b
fix test
sfc-gh-yuwang e877f84
Merge branch 'main' into SNOW-2866776
sfc-gh-yuwang File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we do this style instead to make it more explicit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is a internal only feature, I think we don't want to expose this information to customer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, we can just keep it as kwargs then.
What do you think about moving the arguments onto
_IntegralTypeinstead of_NumericType? It looks like Snowflake only has a single precision forFLOATandDECIMAL(docs), so we should never have to expose precision information for those types.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on using _IntegralType, I don't think we need _scale as it would always be 0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i see, will fix this