Jay Narale created CALCITE-4875:
---
Summary: NVL Function Incorrectly changes nullability field of its
operands
Key: CALCITE-4875
URL: https://issues.apache.org/jira/browse/CALCITE-4875
Project: Calcite
Will Noble created CALCITE-4874:
---
Summary: Add recursive digest helper method
Key: CALCITE-4874
URL: https://issues.apache.org/jira/browse/CALCITE-4874
Project: Calcite
Issue Type: Improvement
Hello,
I am working on a custom parser grammar that extends
"PostgresqlSqlDialect". I have a simple case where I want to allow my
grammar to accept the token "SUBSTR" and have it behave exactly like
"SUBSTRING" would. Is there a simple way to map this behavior without
having to create a new
Calcite already has something called macros. They work like Lisp macros
(substituting the AST) rather than C macros (your model of string replacement).
See JdbcTest.testTableMacro [1].
Does this approach solve your problem?
Julian
[1]
Hey,
I'm working on a product that executes arbitrary SQL on a "data source".
A data source implements a SQL language, for instance, it can be MySQL,
Pinot, BigQuery, etc...
I'd like to introduce a macro language on top of the SQL.
Very similar to what is done in grafana:
Hi guys,
Thanks for your time to read this help message. I'm new to Calcite and
reading some codes and examples from calcite Github repo. I'm wandering how
to get the column real name and type from view.
For example, I have some SQL as below. A kafka topic table left join
MySQL table,
Igor Seliverstov created CALCITE-4873:
-
Summary: Unconditional operand appending on
SqlPosixRegexOperator#createCall method call
Key: CALCITE-4873
URL: https://issues.apache.org/jira/browse/CALCITE-4873
