Add Utf8View to TypeCategory::Unknown
#13350
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
findepi
approved these changes
Nov 11, 2024
| DataType::Utf8 | ||
| | DataType::LargeUtf8 | ||
| | DataType::Utf8View | ||
| | DataType::Null |
There was a problem hiding this comment.
Adding Utf8View LGTM
but the comment above "String literal is possible to cast to many other types like numeric or datetime," is worrisome. I don't think it's true.
Would it make sense to update that comment?
github-actions
bot
added
documentation
Signed-off-by: jayzhan211 <[email protected]>
Signed-off-by: jayzhan211 <[email protected]>
Signed-off-by: Jay Zhan <[email protected]>
jayzhan211
force-pushed
the
fix-string-union-resolution
branch
from
1d7f487 to
2ae09b3
Compare
github-actions
bot
removed
documentation
|
@Omega359 ptal |
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.
Which issue does this PR close?
Closes #13347 #13358 .
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?