Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 2 Jul 2014 07:56:24 +0000 (UTC)
From: "Knut Anders Hatlen (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12724715.1404219102578.86536.1404287784594@arcas>
In-Reply-To: <JIRA.12724715.1404219102578@arcas>
References: <JIRA.12724715.1404219102578@arcas>
Subject: [jira] [Commented] (DERBY-6643) ALTER TABLE columnAlteration syntax
 needs fixing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Knut Anders Hatlen commented on DERBY-6643:
-------------------------------------------

Thank you, Kim. The patch looks good to me. +1 to commit.

> 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: 10.11.0.0
>            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 SET DATA TYPE VARCHAR FOR BIT DATA( integer )."


--
This message was sent by Atlassian JIRA
(v6.2#6252)