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
Second argument to tupleElement must be a constant UInt or String #15411
Labels
bug
Confirmed user-visible misbehaviour in official release
st-accepted
The issue is in our backlog, ready to take
st-hold
We've paused the work on issue for some reason
Comments
victor-sushko
added
the
bug
Confirmed user-visible misbehaviour in official release
label
Sep 28, 2020
Here is the stack from another server (Ubuntu 18.04) with the same query as in the issue.
|
It looks kile literal |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Confirmed user-visible misbehaviour in official release
st-accepted
The issue is in our backlog, ready to take
st-hold
We've paused the work on issue for some reason
An error occurs when a column of type
Array(Tuple(...))
is present in the query. There are only two possible calls of the functiontupleElement
in the query, none of them have non-constant second argument.How to reproduce
Expected behavior
The query should return the table with 3 columns and 1 row.
If replace the last line with
WHERE if('123456789' IS NOT NULL, rq.inn = '123456789', 3)
the query returns expected result.Error message and/or stacktrace
The text was updated successfully, but these errors were encountered: