db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-6643) ALTER TABLE columnAlteration syntax needs fixing
Date Thu, 03 Jul 2014 18:20:34 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kim Haase resolved DERBY-6643.

          Resolution: Fixed
       Fix Version/s:
    Issue & fix info:   (was: Patch Available)

Thanks, Knut!

Committed patch DERBY-6643-2.diff to documentation trunk at revision 1607706. 

> 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
>             Fix For:
>         Attachments: DERBY-6643-2.diff, DERBY-6643.diff, rrefsqlj81859.html, 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