[
https://issues.apache.org/jira/browse/CALCITE-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16284038#comment-16284038
]
Julian Hyde commented on CALCITE-2072:
--------------------------------------
Fix would be a couple of lines
[here|https://github.com/apache/calcite/blob/master/core/src/main/java/org/apache/calcite/config/CalciteConnectionConfigImpl.java#L102],
a test similar to JdbcTest.testFunOracle(), and the aforementioned doc changes.
> Allow specification of geospatial functions in connection string
> ----------------------------------------------------------------
>
> Key: CALCITE-2072
> URL: https://issues.apache.org/jira/browse/CALCITE-2072
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Michael Mior
> Assignee: Julian Hyde
>
> Per Julian's suggestion, it would be good if in addition to {{fun=oracle}},
> we could allow fun={{spatial}} and also a comma-separated list of possible
> operator tables.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
