[
https://issues.apache.org/jira/browse/DERBY-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034770#comment-13034770
]
Knut Anders Hatlen commented on DERBY-5235:
-------------------------------------------
I'm +1 to lifting arbitrary limits.
Will this have any effect on the ability to index VARCHAR columns? I would
think not. Of course, if the value stored in the column is so large that it
doesn't fit on an index page, we cannot index it, but that would also be a
problem today, given that the maximum page size is 32KB, and a 32672 character
long VARCHAR could easily exceed 32KB on disk if it's not pure ASCII.
By the way, if we lift the limit on VARCHAR, we should also lift the even more
artificial 32700-character limit on LONG VARCHAR...
> 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
