+1, thanks Julian for pushing this towards the final vision.
Ruben Q L 于2023年2月11日周六 17:05写道:
> Agree. The change makes sense, and it must be clearly documented on the
> next release notes.
>
>
> On Sat, Feb 11, 2023 at 12:18 AM Julian Hyde wrote:
>
> > Agreed. This is a breaking change.
> >
>
Agree. The change makes sense, and it must be clearly documented on the
next release notes.
On Sat, Feb 11, 2023 at 12:18 AM Julian Hyde wrote:
> Agreed. This is a breaking change.
>
> I've started work in a branch:
> https://github.com/julianhyde/calcite/tree/3870-sql2rel-expand-false
>
> On
Agreed. This is a breaking change.
I've started work in a branch:
https://github.com/julianhyde/calcite/tree/3870-sql2rel-expand-false
On Fri, Feb 10, 2023 at 1:47 PM Stamatis Zampetakis wrote:
>
> It totally makes sense to have expand=false since this is what we recommend.
>
> It can be a
It totally makes sense to have expand=false since this is what we recommend.
It can be a notable change though for those using SqlToRelConverter as it
is so we have to at least put it in a prominent place in the release notes.
Best,
Stamatis
On Fri, Feb 10, 2023 at 10:32 PM Julian Hyde wrote:
You should definitely log a bug for this. Please do so.
We would prefer that new features in SqlToRelConverter are developed
with expand=false. (Rationale: Keeping subqueries as RexSubQuery
expressions allows us to handle them later, via a planner rule, which
makes the logic more composable and
Hi,
I'm using Calcite for a project and am attempting to implement the behavior
for ANY/ALL such as:
SELECT ... FROM ... WHERE a = ANY(SELECT ...)
When I attempt to have Calcite create a plan for this query, I get the
runtime exception from here: