[DERBY-6298] Documentation implies column NOT NULL constraint cannot be named, but it can be.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.10.1.1
• Fix Version/s: 10.8.3.3, 10.9.2.2, 10.10.2.0, 10.11.1.1
• Component/s: Documentation
• Assignee: Camilla Haase
• Reporter: Dag H. Wanvik
• Created: 19/Jul/13 11:37
• Updated: 16/Apr/14 02:41
• Resolved: 25/Jul/13 15:39

Description

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.