[ http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415410 ]
Satheesh Bandaram commented on DERBY-1384: ------------------------------------------ Here is one situation where changing default max length would cause problem. In soft upgrade, if some one creates a default length BLOB/CLOB, if the default is changed, they could successfully create larger than 1MB blob/clob. On downgrade, statements like this would fail: INSERT INTO TAB SELECT * FROM BLOBTAB; where all blob/clob instances are created using default size, just some are created on soft-upgrade to 10.2. Soft upgrade checks are cheap and are designed to maintain same behavior across versions. > 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
