hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16604) Use [NOT] ENFORCED for column constraint characteristics
Date Mon, 08 May 2017 18:30:04 GMT

    [ https://issues.apache.org/jira/browse/HIVE-16604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16001268#comment-16001268
] 

Ashutosh Chauhan commented on HIVE-16604:
-----------------------------------------

Supporting both syntax will be good to have, since people migrating from Oracle will not need
to change their queries in those cases. However, we need to make sure this doesn't add complexity
in our parser which will make future changes in syntaxes harder to do.

> Use [NOT] ENFORCED for column constraint characteristics
> --------------------------------------------------------
>
>                 Key: HIVE-16604
>                 URL: https://issues.apache.org/jira/browse/HIVE-16604
>             Project: Hive
>          Issue Type: Improvement
>    Affects Versions: 3.0.0
>            Reporter: Carter Shanklin
>            Assignee: Jesus Camacho Rodriguez
>
> From HIVE-16575:
> {quote}
> SQL:2011 spec, 10.8, uses [ NOT ] ENFORCED for column constraint characteristics.
> I think Oracle invented DISABLE and NORELY and maybe others have copied it over time.
> A quick check I see DB2 uses the [ NOT ] ENFORCED. Teradata uses something else entirely.
> Personally I think there are advantages to adopting the standard approach.
> There is no standard approach for hinting the optimizer so we're on our own there.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message