[
https://issues.apache.org/jira/browse/DERBY-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-4256:
----------------------------------
Derby Categories: [Newcomer]
I believe that this project would be a good one for a new comer. I don't think
it would be too hard.
I would suggest finding the code path that allows alter table to increase the
size of a varchar field and
mimic the code to apply to blob and clob fields. It will require some parser
changes and some execution
time changes. The files can be pointed out if necessary.
What makes this easy is to only allow INCREASE of size. For blob and clob the
size field is really only used
for error checking at the higher levels of the code, there is no storage
difference between a small one and
a large one. No format difference. Also no space difference as we only use
space to store whatever the
actual size is. By only allowing increase then there is no need to go and
check the length of every value, and
figure out what to do if there exists a value that exceeds the new proposed
maximum.
> 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
> 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.
