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

Kim Haase commented on DERBY-6643:
----------------------------------

Thanks, Knut!

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

I am leaving the issue open for the expected fix to DERBY-6644, which will also 
require a fix to the columnAlteration syntax. Seems simpler than filing another 
issue.


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

Reply via email to