[
https://issues.apache.org/jira/browse/CALCITE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270040#comment-14270040
]
Julian Hyde commented on CALCITE-493:
-------------------------------------
I haven't tried it, but any table reference can have EXTEND, not just those in
the FROM clause of a SELECT. Thus
{code}
UPSERT INTO T EXTEND (c VARCHAR) (a, b, c) VALUES ('foo','bar','bas');
UPSERT INTO T EXTEND (c VARCHAR) (a, b, c) SELECT d, e, f FROM OTHER_T;
{code}
Yeah, it ain't pretty.
> 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)
