Not all JDBC datasources support window functions. But JdbcProject is generated
regardless of this fact. In the result we get SQL with window function which
gives an error when the execution is pushed to the JDBC datasource. What is the
best way to avoid such errors based on SQL dialect? Avoid
Not all JDBC datasources support window functions. But JdbcProject is generated
regardless of this fact. In the result we get SQL with window function which
gives an error when the execution is pushed to the JDBC datasource. What is the
best way to avoid such errors based on SQL dialect? Avoid
Jesus Camacho Rodriguez created CALCITE-2189:
Summary: RelMdAllPredicates fast bail out creates mismatch with
RelMdTableReferences
Key: CALCITE-2189
URL:
The Apache Jenkins build system has built Calcite-Master (build #213)
Status: Still Failing
Check console output at https://builds.apache.org/job/Calcite-Master/213/ to
view the results.
The Apache Jenkins build system has built Calcite-Master (build #212)
Status: Still Failing
Check console output at https://builds.apache.org/job/Calcite-Master/212/ to
view the results.
The Apache Jenkins build system has built Calcite-Master (build #214)
Status: Still Failing
Check console output at https://builds.apache.org/job/Calcite-Master/214/ to
view the results.
I will try to find out more about this during the next few dayswhat do
Oracle, SQL Server, DB2 support.
On Wed, Feb 21, 2018 at 2:12 PM, Julian Hyde wrote:
> Can you do some research, and see if any other databases do anything
> similar? Since Postgres isn’t standard,
Jesus Camacho Rodriguez created CALCITE-2190:
Summary: Extend SubstitutionVisitor.splitFilter to cover different
order of operands
Key: CALCITE-2190
URL: