[
https://issues.apache.org/jira/browse/FLINK-33490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17802146#comment-17802146
]
Martijn Visser commented on FLINK-33490:
----------------------------------------
[~fsk119] I'm not suggesting to have a FLIP for a bugfix, I'm only trying to
understand the process. If the feature and scope of the fix is clear, and it
doesn't require breaking anything, then it's fine to go ahead and fix it. But
in that case, FLINK-33740 is not needed and not a helpful ticket, since a FLIP
isn't meant to list the supported capabilities. If we need to list the
supported capabilities, we should just improve the documentation and that
should be sufficient.
> Validate the name conflicts when creating view
> ----------------------------------------------
>
> Key: FLINK-33490
> URL: https://issues.apache.org/jira/browse/FLINK-33490
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.19.0
> Reporter: Shengkai Fang
> Assignee: xuyang
> Priority: Major
> Labels: pull-request-available
>
> We should forbid
> ```
> CREATE VIEW id_view AS
> SELECT id, uid AS id FROM id_table
> ```
> As the SQL standards states,
> If <regular view specification> is specified, then:
> i) If any two columns in the table specified by the <query expression> have
> equivalent <column name>s, or if any column of that table has an
> implementation-dependent name, then a <view column list> shall be specified.
> ii) Equivalent <column name>s shall not be specified more than once in the
> <view column list>.
> Many databases also throw exception when view name conflicts, e.g. mysql,
> postgres.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
