Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 18 May 2011 17:30:47 +0000 (UTC)
From: "Mike Matrigali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <837284722.22880.1305739847945.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1609503226.19075.1305639407502.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (DERBY-5235) Remove the artificial limit on the
 length of VARCHAR values, allowing them to be java.lang.Integer.MAX_VALUE
 long
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035505#comment-13035505 ] 

Mike Matrigali commented on DERBY-5235:
---------------------------------------

Given that varchar's will read into memory I am pretty sure almost nothing in the system will work with an actual varchar that is 
java.lang.Integer.MAX_VALUE.  Something is going to run out of memory and crash.  Especially given Knut's note that in worst case
we are likely to be trying to allocate an array that is 3 * java.lang.Integer.MAX_VALUE . 


> Remove the artificial limit on the length of VARCHAR values, allowing them to be java.lang.Integer.MAX_VALUE long
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5235
>                 URL: https://issues.apache.org/jira/browse/DERBY-5235
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.9.0.0
>            Reporter: Rick Hillegas
>
> The original Cloudscape limit for the length of VARCHAR values was java.lang.Integer.MAX_VALUE. That is the limit in Cloudscape 5.1. Nothing in Derby should break if we restore the original limit. The current limit is an artificial bound introduced to make Derby agree with DB2. 32672 is the upper bound on the length of a DB2 VARCHAR: http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/admin/r0001029.htm

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira