db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Closed: (DERBY-166) NULL is not a valid constraint type
Date Tue, 10 Oct 2006 10:17:20 GMT
     [ http://issues.apache.org/jira/browse/DERBY-166?page=all ]

Kristian Waagan closed DERBY-166.
---------------------------------


> NULL is not a valid constraint type
> -----------------------------------
>
>                 Key: DERBY-166
>                 URL: http://issues.apache.org/jira/browse/DERBY-166
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects 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

        

Mime
View raw message