[
https://issues.apache.org/jira/browse/CALCITE-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17089321#comment-17089321
]
Jin Xing commented on CALCITE-3946:
-----------------------------------
Shall we go by PostgreSQL grammar [1] ?
For MULTISET/SET, we can use "table constraint";
For VOLATILE, we can use "temporary";
If we bring these modifiers in, besides the change in parser layer, we should
also add additional functionalities. (e.g. drop the temporary table when end of
user session and check duplication when insert values into a table marked as
UNIQUE) .
[1] [https://www.postgresql.org/docs/current/sql-createtable.html]
> Add parser support for MULTISET/SET and VOLATILE modifiers in CREATE TABLE
> statements
> -------------------------------------------------------------------------------------
>
> Key: CALCITE-3946
> URL: https://issues.apache.org/jira/browse/CALCITE-3946
> Project: Calcite
> Issue Type: Improvement
> Components: babel
> Affects Versions: 1.22.0
> Reporter: dasch
> Priority: Major
>
> Add support to Calcite's Babel parser for MULTISET/SET and VOLATILE modifiers
> in CREATE TABLE statements.
> The syntax for these statements is:
> CREATE TABLE [SET|MULTISET] [VOLATILE] <table_name> [IF NOT EXISTS]
> (<column_name> <data_type>, ...);
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
