feat: new concatenation operator for working with arrays #6615
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
github-actions
bot
added
core
alamb
approved these changes
Jun 11, 2023
| @@ -204,3 +204,21 @@ query II rowsort | |||
| select array_ndims(array_fill(1, [1, 2, 3])), array_ndims([[[[[[[[[[[[[[[[[[[[[1]]]]]]]]]]]]]]]]]]]]]); | |||
| ---- | |||
| 3 21 | |||
|
|
|||
| # array concatenate operator #1 (like array_concat scalar function) | |||
There was a problem hiding this comment.
I recommend adding a test for `null handling in these arrays
like
select make_array(1, 2, 3) || make_array(4, null, 6);and
select make_array(1, 2, 3) || null;There was a problem hiding this comment.
I think this feature will only be available after issue #6556 is resolved.
|
@alamb, what do you think about this PR? |
|
🤔 that is not good:
I restarted the test |
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 #6603
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Yes
Are there any user-facing changes?
Yes