[
https://issues.apache.org/jira/browse/DERBY-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-4256:
----------------------------------
go ahead and ignore my comments about parser, it was not based on reading the
code. I am sure about the
store part of my comments that it is safe to just go ahead and change the
catalogs and not have to do anything
to the data.
. Bryan has the
experience in this area. I was just thinking that it was going to add syntax
and did not realize that datatype
part of the syntax would not need parser changes, but it looks like the part
that
handles different datatypes does not really need parser changes. The called
routines can handle many
different datatypes.
> 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: New Feature
> Affects Versions: 10.5.1.1
> Reporter: Mike Matrigali
> Assignee: Eranda Sooriyabandara
> Priority: Minor
>
> 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.
