From ec15dda2bfa246d71a257da2d25c3d398b4d4cc4 Mon Sep 17 00:00:00 2001
From: "ingo@mysql.com" <>
Date: Tue, 19 Jul 2005 14:13:56 +0200
Subject: Bug#10932 - Building server with key limit of 128, makes test cases
 fail This patch allows to configure MyISAM for 128 indexes per table. The
 main problem is the key_map, wich is implemented as an ulonglong. To get rid
 of the limit and keep the efficient and flexible implementation, the highest
 bit is now used for all upper keys. This means that the lower keys can be
 disabled and enabled individually as usual and the high keys can only be
 disabled and enabled as a block. That way the existing test suite is still
 applicable, while more keys work, though slightly less efficient. To really
 get more than 64 keys, some defines need to be changed. Another patch will
 address this.

---
 myisam/mi_rsame.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'myisam/mi_rsame.c')

diff --git a/myisam/mi_rsame.c b/myisam/mi_rsame.c
index 56c8d1226ca..321097744b9 100644
--- a/myisam/mi_rsame.c
+++ b/myisam/mi_rsame.c
@@ -30,7 +30,7 @@ int mi_rsame(MI_INFO *info, byte *record, int inx)
 {
   DBUG_ENTER("mi_rsame");
 
-  if (inx != -1 && ! (((ulonglong) 1 << inx) & info->s->state.key_map))
+  if (inx != -1 && ! mi_is_key_active(info->s->state.key_map, inx))
   {
     DBUG_RETURN(my_errno=HA_ERR_WRONG_INDEX);
   }
-- 
cgit v1.2.1