[
https://issues.apache.org/jira/browse/FLINK-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093179#comment-17093179
]
Dawid Wysakowicz commented on FLINK-17356:
------------------------------------------
The PKs are used by the planner already. The only thing I wanted to bring to
your attention is maybe it makes more sense to first support it in the runtime
and only afterwards expose it to users. Otherwise it might be confusing.
> 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)
