Inconsistent query plans when Functional Indexes are used
General
Escalation
General
Escalation
Description
Environment
None
AFFECTED CS IDs
CS0047375
Activity
Show:
Julia Vural September 30, 2024 at 10:40 AM
This is a design flaw coming from upstream. Currently, the fix cannot be made on the downstream side as it would cause code to deviate from upstream tremendously and make it impossible to maintain.
Julia Vural September 26, 2024 at 1:07 PM
This is a design flaw coming from upstream.
Julia Vural July 1, 2024 at 10:44 AM
The upstream bug was marked as a duplicate of another upstream bug that was opened in 2021. It looks like upstream has no intention to fix it. There is a possibility that this might not be an easy fix due to the current design.
Won't Do
Details
Assignee
UnassignedUnassignedReporter
Iwo PanowiczIwo PanowiczUpstream Bug URL
Needs QA
YesTime tracking
1d loggedAffects versions
Priority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
Iwo Panowicz
Iwo PanowiczUpstream Bug URL
Needs QA
Yes
Time tracking
1d logged
Affects versions
Priority
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created June 25, 2024 at 9:22 AM
Updated October 1, 2024 at 9:40 AM
Resolved September 30, 2024 at 10:40 AM
Description:
MySQL does not utilise functional indexes for operators like `LIKE'.
How to repeat:
All of the below are executed under:
Table schema:
Implicit usage does not use the
test01
index:Explicit usage of the virtually generated columns makes use of that index:
Suggested fix:
The optimizer should use the functional indexes more consistently.