[
https://issues.apache.org/jira/browse/CALCITE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14543668#comment-14543668
]
Xavier FH Leong commented on CALCITE-708:
-----------------------------------------
I'd completed the first draft implementation, basically using what was defined
in the runtime Schema, a query was run to collect all the type info. This will
give a sub set of type info that was created by the schema factory, un-realized
type are not query-able.
I take this approach since currently DDL is not officially supported, so in a
sense, the schema are not changeable via JDBC or SQL, so exploration of type
info are mainly for what was already defined and used, which at the client side
use case is to dynamically build SQL based on data type reflection
However, I do believe in future, we need a way that the type can be reflected
back by the adapter, which what [~yeongwei] is mentioning on the support on the
Schema#getTypeInfos, where the adapter can overwrite the details info for all
the supported data types.
> Avatica and Calcite to support DatabaseMetaData getTypeInfo
> -----------------------------------------------------------
>
> Key: CALCITE-708
> URL: https://issues.apache.org/jira/browse/CALCITE-708
> Project: Calcite
> Issue Type: Improvement
> Reporter: Xavier FH Leong
> Assignee: Julian Hyde
> Priority: Minor
> Labels: avatica, metadata
>
> http://docs.oracle.com/javase/7/docs/api/java/sql/DatabaseMetaData.html#getTypeInfo()
>
> Avatica to call underlying connection database metadata for getTypeInfo to
> show the database supported type and meta info.
> Calcite to provide the info for the underlying adapter thru SqlTypeName and
> RelDataType
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
