[DERBY-3854] Implement LIKE transformations and optimizations for databases using territory-based collations

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.3.3.0, 10.4.1.3, 10.5.1.1
• Component/s: SQL
• Labels: derby_triage10_10
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Richard N. Hillegas
• Created: 26/Aug/08 18:11
• Updated: 30/Sep/12 02:40

Description

The LIKE transformations and optimizations are disabled when using a database with a territory-based collation. See the following email thread: http://www.nabble.com/territory-based-collations-and-optimizations-for-the-LIKE-operator-td19111725.html#a19111725 That thread, in turn, refers to DERBY-1478. It would be nice if we did not have to perform full table scans for LIKE queries in databases with territory-based collations.

Issue Links

• is related to: DERBY-1748 Global case insensitive setting
• is related to: DERBY-3855 The Tuning guide should mention that LIKE transformations/optimizations are disabled when using territory-based collations
• relates to: DERBY-1478 Add built in language based ordering and like processing to Derby