Julian Hyde created CALCITE-5178:
Summary: Scalar subquery in scalar subquery generates plan that
will not compile
Key: CALCITE-5178
URL: https://issues.apache.org/jira/browse/CALCITE-5178
Project:
Hi Julian,
Thanks for asking those questions! I was providing this material as an
educational reference since the use case is very similar to the resources I
shared. I found those references to help enrich the Calcite community in
the past. For example, Gavin Ray has written an article [1] on
Hello, community!
I would like to ask for your help with the review of this PR [1].
It’s been a while since I worked on this for the last time, but now I’m
really looking forward to driving this till the end.
This change addresses the issue described in CALCITE-4913 [2]. Basically, I
want the
Yanjing,
Yes, I know. But I don't think this is a problem.
Yanjing Wang 于2022年6月2日周四 17:54写道：
> Benchao,
>
> I mean that "name" <> '3' will have '3' to be varchar(10) type, but "name"
> > '3' or "name" < '3' will have '3' to be char(1) type, I noticed that your
> change will make "name" > '3'
Benchao,
I mean that "name" <> '3' will have '3' to be varchar(10) type, but "name"
> '3' or "name" < '3' will have '3' to be char(1) type, I noticed that your
change will make "name" > '3' or "name" < '3' to be "name" <> '3', but the
'3' is still char(1) type. should the '3' type be consistent
Big thanks to you, Benchao,
I also noticed that SubstitutionVisitor#isEquivalent method evaluates
equivalence without types and RexCall#computeDigest(boolean withType) with
false argument .
Now we are aware that the type difference doesn't affect materialization
applications and expression
Ruben Q L created CALCITE-5177:
--
Summary: Query loses hint after decorrelation
Key: CALCITE-5177
URL: https://issues.apache.org/jira/browse/CALCITE-5177
Project: Calcite
Issue Type: Bug
