xtern commented on PR #4409:
URL: https://github.com/apache/ignite-3/pull/4409#issuecomment-2374397878
Frankly, I expected that after forbidding implicit type casts between
different families, we would not have type casts for function operands.
I mean
```
select length(1234)
```
for example, works fine with the following plan
```
Project(EXPR$0=[LENGTH(_UTF-8'1234':VARCHAR CHARACTER SET "UTF-8")]):
rowcount = 1.0, cumulative cost = IgniteCost [rowCount=2.0, cpu=2.0,
memory=0.0, io=0.0, network=0.0], id = 102
Values(tuples=[[{ 0 }]]): rowcount = 1.0, cumulative cost = IgniteCost
[rowCount=1.0, cpu=1.0, memory=0.0, io=0.0, network=0.0], id = 101
``
But the same example with dynamic parameter produces exception (as expected)
```
Values passed to LENGTH operator must have compatible types
```
Are we gong to fix this in follow-up issue?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@ignite.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
