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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.3.0, 10.4.1.3, 10.5.1.1
• Fix Version/s: 10.5.1.1
• Component/s: Documentation
• Assignee: Camilla Haase
• Reporter: Richard N. Hillegas
• Created: 26/Aug/08 18:22
• Updated: 13/Jan/11 21:18
• Resolved: 02/Sep/08 19:58

Description

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.

Issue Links

• relates to: DERBY-3854 Implement LIKE transformations and optimizations for databases using territory-based collations