[
https://issues.apache.org/jira/browse/FLINK-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17092673#comment-17092673
]
Jark Wu edited comment on FLINK-17356 at 4/26/20, 11:22 AM:
------------------------------------------------------------
I agree with you [~f.pompermaier]. SQL standard and many database vendors all
use {{UNIQUE}} not {{UNIQUE KEY}} to declare a unique constraint. But we can
wait for the response from the author [~dwysakowicz].
was (Author: jark):
I agree with you [~f.pompermaier]. SQL standard and many database vendors all
use {{UNIQUE}} not {{UNIQUE KEY}} to declare a unique constraint.
> Properly set constraints (PK and UNIQUE)
> ----------------------------------------
>
> Key: FLINK-17356
> URL: https://issues.apache.org/jira/browse/FLINK-17356
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / JDBC, Table SQL / Ecosystem
> Reporter: Flavio Pompermaier
> Priority: Major
> Labels: pull-request-available
>
> At the moment the PostgresCatalog does not create field constraints (at the
> moment there's only UNIQUE and PRIMARY_KEY in the TableSchema..could it
> worth to add also NOT_NULL?)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
