[
https://issues.apache.org/jira/browse/FLINK-17356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17092358#comment-17092358
]
Flavio Pompermaier commented on FLINK-17356:
--------------------------------------------
Yes, you're right. My laziness told me to try to push the 2 together..is it a
problem? Do I really need to split it in 2 parts? If we want to be meticulous
we should do another PR to change the enum of unique from UNIQUE_PK to UNIQUE
:). If you think that this PR should be splitted just open the relative tickets
please and I'll try yo push the new PRs
> 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)
