db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Levitt (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-382) Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual
Date Thu, 30 Jun 2005 00:00:00 GMT
    [ http://issues.apache.org/jira/browse/DERBY-382?page=comments#action_12314722 ] 

Jeff Levitt commented on DERBY-382:
-----------------------------------

>From Derby-166 (which is resolved as a duplicate of this issue now):

 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.

> Doc Review (CLOSED TO FURTHER COMMENTS): Derby Reference Manual
> ---------------------------------------------------------------
>
>          Key: DERBY-382
>          URL: http://issues.apache.org/jira/browse/DERBY-382
>      Project: Derby
>         Type: Improvement
>   Components: Documentation
>  Environment: all
>     Reporter: Jeff Levitt
>     Priority: Minor
>      Fix For: 10.1.1.0

>
> This issue tracks comments for the Derby Reference Manual. The deadline for posting comments
was Tuesday, June 28, noon Pacific time.
> PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE.  If you have additional comments,
please open a JIRA issue for a fixin in a future release, as there is not enough time to incorporate
additional comments.
> Some guidelines to follow when posting comments to this issue are:
> - Try to make clear and concise comments about what you want changed whenever possible.
 Provide concrete comments that say "Please change <original> to <modified>" instead
of generic comments like "This section needs to be rewritten."
> - If you're reviewing the HTML Files copy, include the URL for the page in the review
comment. Obtain the URL like this:
>     * highlight the topic in the left frame
>     * right click
>     * choose "Properties"
>     * copy and paste the address in the pop up box.
> - If you're reviewing the PDF copy, in the review comment:
>     * Include the page number for the PDF, and indicate whether the number is the PDF
sheet number or the printed page number.
>     * Include the title of the section that the problem occurs in. If it's in a subsection,
try to include the hierarchy of titles.
> - Please don't review the HTML Book copy -- it'll be time consuming to match up that
copy with the underlying DITA source.

-- 
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