From 7ace3f136264fbc7de3e50e047ad5f88653c6c3c Mon Sep 17 00:00:00 2001
From: "sergefp@mysql.com" <>
Date: Fri, 1 Apr 2005 11:05:17 +0400
Subject: [PATCH] Better comment

---
 sql/sql_select.cc | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/sql/sql_select.cc b/sql/sql_select.cc
index 57b09fa40b4..3c66574231d 100644
--- a/sql/sql_select.cc
+++ b/sql/sql_select.cc
@@ -7179,8 +7179,9 @@ test_if_skip_sort_order(JOIN_TAB *tab,ORDER *order,ha_rows select_limit,
           /*
             We'll use ref access method on key new_ref_key. In general case 
             the index search tuple for new_ref_key will be different (e.g.
-            when one of the indexes only covers prefix of the field, see
-            BUG#9213 in group_by.test).
+            when one index is defined as (part1, part2, ...) and another as
+            (part1, part2(N), ...) and the WHERE clause contains 
+            "part1 = const1 AND part2=const2". 
             So we build tab->ref from scratch here.
           */
           KEYUSE *keyuse= tab->keyuse;