[
https://issues.apache.org/jira/browse/CALCITE-5346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628572#comment-17628572
]
Julian Hyde commented on CALCITE-5346:
--------------------------------------
If user-defined types belong to a schema (I'll take your word for it) then the
most straightforward design is that they always belong to a schema. The
"global" types could belong to a particular schema (called say "$global") that
is on the "path" used to resolve types (I've forgotten whether there is such a
path, but there is a single-element "path" for resolving tables, namely the
current schema, and there is also a path for resolving user-defined functions,
so it's reasonable that there is one for types).
In other words, if the only problem is the need to qualify user-defined types
with a schema, then I think we can solve that fairly elegantly. And we wouldn't
need a new "types" tag in the JSON model file, because every JSON schema
already includes types.
> Support for type aliases
> ------------------------
>
> Key: CALCITE-5346
> URL: https://issues.apache.org/jira/browse/CALCITE-5346
> Project: Calcite
> Issue Type: New Feature
> Reporter: Will Noble
> Assignee: Will Noble
> Priority: Major
>
> We would like to support some sort of type alias functionality in order to
> map certain [BigQuery
> types|https://cloud.google.com/bigquery/docs/reference/standard-sql/data-types]
> to ISO types, e.g. {{STRING}} -> {{VARCHAR}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
