[
https://issues.apache.org/jira/browse/DERBY-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eranda Sooriyabandara updated DERBY-4256:
-----------------------------------------
Attachment: derby4256.diff
Hi Bryan,
I made some changes to the code as,
if (!(typeName.equals(TypeId.VARCHAR_NAME)) &&
!(typeName.equals(TypeId.VARBIT_NAME))&&!(typeName.equals(TypeId.BLOB_NAME)))
{
throw StandardException.newException(
SQLState.LANG_MODIFY_COLUMN_INVALID_TYPE);
}
and this succeed the test
ij version 10.6
ij> connect 'jdbc:derby:testdb;create=true';
ij> create table binarydata(c1 int,data blob(64));
0 rows inserted/updated/deleted
ij> ALTER TABLE binarydata ALTER COLUMN data SET DATA TYPE blob(256M);
0 rows inserted/updated/deleted
Here I am attaching the patch file with this.
> allow alter table to increase the maximum size of a blob and a clob.
> --------------------------------------------------------------------
>
> Key: DERBY-4256
> URL: https://issues.apache.org/jira/browse/DERBY-4256
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.5.1.1
> Reporter: Mike Matrigali
> Assignee: Eranda Sooriyabandara
> Priority: Minor
> Attachments: derby4256.diff
>
>
> Allow new syntax that allows user to alter the maximum length of a blob
> and/or clob column:
> ALTER TABLE binarydata ALTER COLUMN data SET DATA TYPE blob(128M)
> The syntax should match up with the existing functionality to increase the
> size of varchar fields.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
