db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-275) Add documentation support for BY DEFAULT option, once code changes are made.
Date Mon, 20 Jun 2005 23:31:21 GMT
    [ http://issues.apache.org/jira/browse/DERBY-275?page=comments#action_12314111 ] 

A B commented on DERBY-275:

With this latest patch, it looks like some text in the "CREATE TABLE" section was orphaned.
 More specifically, the following lines should be moved to the "Identity column attributes"
section with the rest of the related info:


The IDENTITY keyword can only be specified if the data type associated with the column is
one of the following exact integer types.

    * INT
    * BIGINT


Actually, there seems to be a lot of column-specific information under the "CREATE TABLE"
section that would be better if moved to the "Column-definition" section.  For example, we
talk about "Data types", "Column-level-constraints", and column defaults when none of those
are used in the syntax diagram for CREATE TABLE.  Wouldn't all of that make more sense under
the "Column-definition" section?  Of course, that's a problem that existed before this patch,
so perhaps that should be a different issue to be filed against the Reference Manual later...?

In any event, the above lines (at the very least) should be moved to the same section that
describes the GENERATED ALWAYS/BY DEFAULT keywords, since that's where IDENTITY columns are

> Add documentation support for BY DEFAULT option, once code changes are made.
> ----------------------------------------------------------------------------
>          Key: DERBY-275
>          URL: http://issues.apache.org/jira/browse/DERBY-275
>      Project: Derby
>         Type: Sub-task
>   Components: Documentation
>     Versions:
>     Reporter: Satheesh Bandaram
>      Fix For:
>  Attachments: derby275modified.zip
> Once a patch is accepted, new syntax needs to be documented.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message