[ http://issues.apache.org/jira/browse/DERBY-166?page=all ]
Jeff Levitt resolved DERBY-166:
-------------------------------
Resolution: Duplicate
I am adding this comment to the doc review for the reference manual for version
10.1. It will get patched there... Thus, resolving this issue as a duplicate
of Derby-382...
> NULL is not a valid constraint type
> -----------------------------------
>
> Key: DERBY-166
> URL: http://issues.apache.org/jira/browse/DERBY-166
> Project: Derby
> Type: Bug
> Components: Documentation
> Versions: 10.0.2.0
> Environment: Windows XP SP1 Professional
> Reporter: George Baklarz
> Priority: Trivial
>
> The following statement in the documentation is incorrect:
> NULL The opposite of NOT NULL (not really a constraint), it specifies that
> the column can hold NULL values. Specifying NULL is the same as saying
> nothing at all, except when the column is included in a PRIMARY KEY
> constraint.
> If you try to create a column with the NULL attribute, you get a failure:
> CREATE TABLE X ( A INT NULL );
> ERROR 42X01: Syntax error: Encountered "null" at line 1, column 23.
> While this isn't really a problem since we can just omit the NULL keyword,
> the documentation gives the impression that it is allowed in the CREATE
> statement.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
