-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
fix: dont try to coerce list for regex match #11646
Conversation
@@ -325,6 +325,11 @@ SELECT 'foo\nbar\nbaz' ~ 'bar'; | |||
---- | |||
true | |||
|
|||
statement error | |||
Error during planning: Cannot infer common argument type for regex operation List(Field { name: "item", data_type: Int64, nullable: true, dict_id: 0, dict_is_ordered: false, metadata |
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.
A bit verbose, but tries to prove the error happens during planning.
I guess we don't need list coercion for |
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, I'll wait a day or so to hear if it's there for a reason for it, otherwise I'll pull it out too. |
Thanks again @tshauck and @jayzhan211 |
Which issue does this PR close?
Closes #11622
Rationale for this change
Regex match's args will try to be coerced from Lists, but that shouldn't be possible.
List coercion was added in #10445, but it's not clear to me why.
What changes are included in this PR?
Remove list coercion, add tests
Are these changes tested?
yes
Are there any user-facing changes?
No