[DERBY-5235] Remove the artificial limit on the length of VARCHAR values, allowing them to be java.lang.Integer.MAX_VALUE long

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.9.1.0
• Component/s: SQL
• Labels: derby_triage10_10
• Urgency: Normal
• Issue & fix info: Newcomer
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 17/May/11 13:34
• Updated: 28/Sep/12 04:39

Description

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

Issue Links

• is related to: DERBY-5241 The = and <> operators should be supported on CLOBs.
• is related to: DERBY-5236 Client driver silently truncates strings that exceed 32KB
• relates to: DERBY-4793 Assert failure when concatenating strings with total size greater than 32K