You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kim Haase (JIRA)" <ji...@apache.org> on 2012/11/20 20:18:58 UTC
[jira] [Updated] (DERBY-5999) Improve documentation on index key
lengths
[ https://issues.apache.org/jira/browse/DERBY-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-5999:
-----------------------------
Attachment: DERBY-5999.zip
DERBY-5999.stat
DERBY-5999.diff
Attaching DERBY-5999.diff, DERBY-5999.stat, and DERBY-5999.zip, with changes to two topics:
M src/ref/rrefsqlj41207.dita
M src/tuning/ctundepth1002853.dita
There is no need, I think, to add a warning to the documentation of the CHAR data type. Since a CHAR can be no larger than 254 bytes, there is no danger of bumping into the page size limit.
Please let me know if you have any suggestions for changes.
> Improve documentation on index key lengths
> ------------------------------------------
>
> Key: DERBY-5999
> URL: https://issues.apache.org/jira/browse/DERBY-5999
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Affects Versions: 10.9.1.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-5999.diff, DERBY-5999.stat, DERBY-5999.zip
>
>
> DERBY-5881 includes the following suggestion:
> 3. The documentation for sized datatypes like char and varchar should be updated to warn about indexing limitations (which would most likely be encounterd with such datatypes).
> It probably also makes sense to add this recommendation to the introductory topic on indexes in the Tuning Guide (http://db.apache.org/derby/docs/dev/tuning/ctunperf10679.html).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira