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 "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2014/07/11 13:47:05 UTC

[jira] [Commented] (DERBY-6653) Data type limitations on indexes should be in Reference Manual

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

Knut Anders Hatlen commented on DERBY-6653:
-------------------------------------------

Thanks, Kim. The changes look good to me. +1 to commit.

> Data type limitations on indexes should be in Reference Manual
> --------------------------------------------------------------
>
>                 Key: DERBY-6653
>                 URL: https://issues.apache.org/jira/browse/DERBY-6653
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 10.11.0.0
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-6653.diff, DERBY-6653.stat, DERBY-6653.zip
>
>
> The Tuning Guide topic "Create useful indexes" (http://db.apache.org/derby/docs/10.10/tuning/ctundepth1002853.html) has the following excessively vague note at the end:
> "Note: Derby does not support indexing on columns with data types like BLOB, CLOB, and XML."
> The topic also has a cross-reference to the "CREATE INDEX statement" topic in the Derby Reference Manual, but that topic says nothing about data type limitations for index columns. 
> In an email exchange, Knut says that LONG VARCHAR and user-defined types should be added to make the list complete, but he also suggests moving this information from the tuning guide to the "CREATE INDEX statement" topic in the Reference Manual, since we already reference that topic and since the information needs to be there.



--
This message was sent by Atlassian JIRA
(v6.2#6252)