[ http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415433 ]
Satheesh Bandaram commented on DERBY-1384: ------------------------------------------ This is the case I was thinking about. I have coded my application without specifying lengths for BLOB/CLOB. I would normally expect this to work: INSERT INTO tblob select * from tblob; OR INSERT INTO tblob select * from myblobTab; My concern was on soft-update, it would be possible to insert larger than 1MB and later on downgrade, same operations like above will not work as some instances of BLOB could now be larger than 1MB. (and hence above operations could fail on 10.1) May be this is extreme case and may not be worth protecting... but one could look at 10.1 BLOB (without size) datatype to be between 1-1MB and is being changed to 1-2GB. > Increase default BLOB/CLOB length to maximum supported (2G?) > ------------------------------------------------------------ > > Key: DERBY-1384 > URL: http://issues.apache.org/jira/browse/DERBY-1384 > Project: Derby > Type: Improvement > Components: SQL > Reporter: Bernt M. Johnsen > Assignee: Bernt M. Johnsen > Priority: Minor > Fix For: 10.2.0.0 > Attachments: derby-1384-code.diff, derby-1384-code.stat, > derby-1384-docs.diff, derby-1384-docs.stat > > Default BLOB/CLOB length should be the maximum length supported by Derby (2G?) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
