db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6643) ALTER TABLE columnAlteration syntax needs fixing
Date Thu, 03 Jul 2014 09:26:24 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051234#comment-14051234

Knut Anders Hatlen commented on DERBY-6643:

The work on DERBY-6644 is done, so the new syntax (\{SET | DROP \} NOT NULL) could be added
to columnAlteration as an alternative to the existing \[ NOT \] NULL syntax.

> ALTER TABLE columnAlteration syntax needs fixing
> ------------------------------------------------
>                 Key: DERBY-6643
>                 URL: https://issues.apache.org/jira/browse/DERBY-6643
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-6643.diff, rrefsqlj81859.html
> Knut Anders Hatlen points out in a comment on DERBY-6609 that the columnAlteration syntax
in the ALTER TABLE statement topic is not quite correct. It is possible to set the data type
to BLOB or CLOB, in addition to VARCHAR and VARCHAR FOR BIT DATA.
> Also, for VARCHAR FOR BIT DATA, he notes, "the length argument is on the wrong spot.
It should be columnName SET DATA TYPE VARCHAR ( integer ) FOR BIT DATA,  rather than columnName
> DERBY-6644 also requires a change to the columnAlteration syntax.

This message was sent by Atlassian JIRA

View raw message