[
https://issues.apache.org/jira/browse/DERBY-6298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik closed DERBY-6298.
--------------------------------
> Documentation implies column NOT NULL constraint cannot 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
> Affects Versions: 10.10.1.1
> Reporter: Dag H. Wanvik
> Assignee: Kim Haase
> Fix For: 10.8.3.1, 10.9.2.2, 10.10.1.3, 10.11.0.0
>
> Attachments: DERBY-6298-2.diff, DERBY-6298.diff, rrefsqlj16095.html,
> rrefsqlj16095.html
>
>
> 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); The curly braces around
> primary, unique and references are redundant as well.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
