[
https://issues.apache.org/jira/browse/CALCITE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268704#comment-14268704
]
James Taylor commented on CALCITE-493:
--------------------------------------
This looks very good for SELECT, but how would you insert a dynamic column
value at DML time using INSERT/UPSERT VALUES, [~julianhyde]? For example, in
Phoenix you can do this:
{code}
UPSERT INTO T(a, b, c VARCHAR) VALUES ('foo','bar','bas');
UPSERT INTO T(a, b, c VARCHAR) SELECT d, e, f FROM OTHER_T;
{code}
> Add EXTEND clause, for defining columns and their types at query/DML time
> -------------------------------------------------------------------------
>
> Key: CALCITE-493
> URL: https://issues.apache.org/jira/browse/CALCITE-493
> Project: Calcite
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Julian Hyde
> Labels: phoenix
> Fix For: 1.0.0-incubating
>
>
> Often times only being able to define a static schema over which to query is
> not flexible enough. It would be useful to be able to define columns and
> their type at query/DML time. For an example syntax, see
> http://phoenix.apache.org/dynamic_columns.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
