Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <17566398.1149770671523.JavaMail.jira@brutus>
Date: Thu, 8 Jun 2006 12:44:31 +0000 (GMT+00:00)
From: "Andreas Korneliussen (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1384) Increase default BLOB/CLOB length to
 maximum supported (2G?)
In-Reply-To: <32130647.1149681749953.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1384?page=comments#action_12415347 ] 

Andreas Korneliussen commented on DERBY-1384:
---------------------------------------------

Maybe the  Release Note Required checkbox should be checked for this change.

My understanding is that after an upgrade (from a version without this improvement), an application which continues to use the schemas/tables as they were initially created, will not be affected by the change. An application which recreates the schemas/tables after an upgrade, may be affected if it depends on Derby rejecting Blobs with sizes bigger than 1M.


> 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