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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2008/08/26 20:22:44 UTC
[jira] Created: (DERBY-3855) The Tuning guide should mention that
LIKE transformations/optimizations are disabled when using territory-based
collations
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.4.1.3, 10.3.3.0, 10.5.0.0
Reporter: Rick Hillegas
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.
[jira] Updated: (DERBY-3855) The Tuning guide should mention that
LIKE transformations/optimizations are disabled when using territory-based
collations
Posted by "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:
-----------------------------
Derby Info: [Patch Available]
> 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.
[jira] Updated: (DERBY-3855) The Tuning guide should mention that
LIKE transformations/optimizations are disabled when using territory-based
collations
Posted by "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.
[jira] Commented: (DERBY-3855) The Tuning guide should mention that
LIKE transformations/optimizations are disabled when using territory-based
collations
Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626334#action_12626334 ]
Rick Hillegas commented on DERBY-3855:
--------------------------------------
Hi Kim,
It looks like it took me more words to describe the problem than it took you to fix it. This looks good to me. +1
> 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.
[jira] Closed: (DERBY-3855) The Tuning guide should mention that
LIKE transformations/optimizations are disabled when using territory-based
collations
Posted by "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 closed DERBY-3855.
----------------------------
The fix now appears in the Latest Alpha Manuals, so this issue can be closed.
> 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
> Fix For: 10.5.0.0
>
> 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.
[jira] Assigned: (DERBY-3855) The Tuning guide should mention that
LIKE transformations/optimizations are disabled when using territory-based
collations
Posted by "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 reassigned DERBY-3855:
--------------------------------
Assignee: Kim Haase
> 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
>
> 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.
[jira] Resolved: (DERBY-3855) The Tuning guide should mention that
LIKE transformations/optimizations are disabled when using territory-based
collations
Posted by "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 resolved DERBY-3855.
------------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
Derby Info: (was: [Patch Available])
Thank you very much, Rick!
Committed patch DERBY-3855.diff to documentation trunk at revision 691356.
> 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
> Fix For: 10.5.0.0
>
> 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.