Another error on using unbounded dynamic parameters

I found another query sent to my DBMS which causes troubles to Calcite SELECT ? as foo, k1, n1 FROM mytable The result is the usual: "Illegal use of dynamic parameter" This time it is impossible to infer the type of the parameter. I wonder if it would be possible to implement a configuration

Re: BindableTableScan is losing aliased named

I solved my problem just by capturing the original rowtype after sql parser. Thanks Enrico Il ven 17 nov 2017, 22:44 Enrico Olivelli ha scritto: > > > Il ven 17 nov 2017, 22:36 Julian Hyde ha scritto: > >> Translating to RelNode loses some metadata. When

Setting connection's auto-commit property from the configuration files?

Is there a way to set the ConnectionProperties#setAutoCommit(boolean val) from the model.json or perhaps via the jdbc URL attributes? E.g. i'm looking for any configuration option that wouldn't require writing code such as Connection.setAutoCommit(...) -- Christian Tzolov

[GitHub] calcite-avatica-go pull request #6: Bump gokrb5 client to v2

GitHub user F21 opened a pull request: https://github.com/apache/calcite-avatica-go/pull/6 Bump gokrb5 client to v2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Boostport/calcite-avatica-go update-from-upstream

[GitHub] calcite-avatica-go pull request #6: Bump gokrb5 client to v2

Github user asfgit closed the pull request at: https://github.com/apache/calcite-avatica-go/pull/6 ---

Re: Setting connection's auto-commit property from the configuration files?

We should make autoCommit a connection property (see https://calcite.apache.org/docs/adapter.html#jdbc-connect-string-parameters ). Also any other properties set via methods in java.sql.Connection; and also things in