fix(sql): allow using more data types in PARTITION BY of LATEST ON queries #3137
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
This was an omission. It's allowed with LONGs so I see no good reason why it should not be allowed with TIMESTAMPs.
ideoma
previously approved these changes
Mar 30, 2023
puzpuzpuz
added
New feature
puzpuzpuz
reviewed
Mar 30, 2023
bziobrowski
changed the title
[PR Coverage check]😍 pass : 1 / 1 (100.00%) file detail
|
bziobrowski
approved these changes
Mar 30, 2023
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.
PR allows using columns of following data types in PARTITON BY clause of LATEST ON :
This was an omission. It's allowed with LONGs so I see no good reason why it should not be allowed with TIMESTAMPs.