db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6298) Documentation implies column NOT NULL constraint can not be named, but it can be.
Date Fri, 19 Jul 2013 11:38:48 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dag H. Wanvik updated DERBY-6298:
---------------------------------

    Summary: Documentation implies column NOT NULL constraint can not be named, but it can
be.  (was: Documentation implies column NOT NULL constrain can not be named, but it can be.)
    
> Documentation implies column NOT NULL constraint can not be named, but it can be.
> ---------------------------------------------------------------------------------
>
>                 Key: DERBY-6298
>                 URL: https://issues.apache.org/jira/browse/DERBY-6298
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>
> Cf syntax description in ref/rrefsqlj16095.html:
> Column-level-constraint
> {
>     NOT NULL |
>     [ [CONSTRAINT constraint-Name]
>     {
>         CHECK (searchCondition) |
>         {
>             PRIMARY KEY |
>             UNIQUE |
>             REFERENCES clause
>         } 
>     }
> }
> but actually this works:
> create table t(i int constraint foo not null);

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message