[jira] Updated: (DERBY-3855) The Tuning guide should mention that LIKE transformations/optimizations are disabled when using territory-based collations

["Kim Haase (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase updated DERBY-3855:
-----------------------------

    Attachment: rtuntransform208.html
                DERBY-3855.diff

This seems like a fairly simple fix, Rick, with all the information you provided. Attaching DERBY-3855.diff and rtuntransform208.html, which I hope are correct. I added a cross-reference to the main information about territory-based collation in the Dev Guide.

> The Tuning guide should mention that LIKE transformations/optimizations are disabled when using territory-based collations
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3855
>                 URL: https://issues.apache.org/jira/browse/DERBY-3855
>             Project: Derby
>          Issue Type: Improvement
>    Affects Versions: 10.3.3.0, 10.4.1.3, 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-3855.diff, rtuntransform208.html
>
>
> The Tuning Guide section titled "LIKE transformations" describes transformations and optimizations which Derby performs on LIKE expressions in order to avoid full table scans. These transformations/optimizations are disabled when using territory-based collations. See DERBY-3854. The Tuning Guide does not mention this fact but it is likely that this information would be very useful to customers and tech support engineers. The "LIKE transformations"  section in the Tuning Guide should be changed to mention that LIKE transformations/optimizations are disabled when using territory-based collations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.