That makes sense.
Calcite calls the parse function twice, first time for model parsing during
startup, second time for ad-hoc query parsing. Calcite should use a
normalized version of the schema/table/column names to match up the query
to the schema.
My example is case in-sensitive for both model
I took a look at the functions in SqlLibraryOperators.
Number of Functions (in either PostgreSQL and/or Redshift): 44
Only in PostgreSQL: 5
Only in Redshift: 5
In both with different implementations: 2
This page describes the PostgreSQL functions that are unsupported in Redshift.
https://docs.aws.
Does the redshift official website fully explain compatibility with the
postgres dialect?
If so, I think this is acceptable. Because we must consider that some negative
tests of redshift functions are consistent with postgres, otherwise it may
cause some trouble to users.
> 2024年6月22日 07:13，Ju
I don’t want to encourage people to subclass RelBuilder. It is not designed to
be extended by subclassing.
Having said that, it seems reasonable to provide a way to find the table
aliases.
In https://issues.apache.org/jira/browse/CALCITE-4946 I added the method
RelBuilder.size(); I was surpris
