db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5999) Improve documentation on index key lengths
Date Wed, 21 Nov 2012 13:11:58 GMT

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

Knut Anders Hatlen commented on DERBY-5999:

The patch looks like a good improvement. +1

It is possible to bump into the page size limit with CHAR columns too, but then you'd need
to have a multi-column index. I think it's OK not to mention that possibility in the documentation
of the CHAR data type, though. What we already have documented in the CREATE INDEX topic is
probably sufficient for CHAR and the other data types.
> 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:
>            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

View raw message