[
https://issues.apache.org/jira/browse/DERBY-6653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-6653:
-----------------------------
Attachment: DERBY-6653.zip
DERBY-6653.stat
DERBY-6653.diff
Attaching DERBY-6653.diff, DERBY-6653.stat, and DERBY-6653.zip, with
modifications to the following topics:
M src/tuning/ctundepth1002853.dita
M src/ref/rrefsqlj20937.dita
Please let me know if changes are needed. Thanks!
> 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)
