[Groonga-mysql-commit] mroonga/mroonga at f6d2ed8 [master] storage: fix the max supported key and key part length

Back to archive index

Kouhei Sutou null+****@clear*****
Wed Oct 22 10:04:31 JST 2014


Kouhei Sutou	2014-10-22 10:04:31 +0900 (Wed, 22 Oct 2014)

  New Revision: f6d2ed81327b32b95727a196a306989cb755ae98
  https://github.com/mroonga/mroonga/commit/f6d2ed81327b32b95727a196a306989cb755ae98

  Message:
    storage: fix the max supported key and key part length
    
    It doesn't change any behavior because handler class has
    MAX_KEY_LENGTH (= 3072) check.
    
    Groonga can handle 4096 byte for a key but we can't use it on Mroonga
    because of MySQL limitation. :<

  Modified files:
    ha_mroonga.cpp

  Modified: ha_mroonga.cpp (+2 -2)
===================================================================
--- ha_mroonga.cpp    2014-10-21 12:14:09 +0900 (8b9a08b)
+++ ha_mroonga.cpp    2014-10-22 10:04:31 +0900 (6a9027f)
@@ -2126,7 +2126,7 @@ uint ha_mroonga::wrapper_max_supported_key_length() const
 uint ha_mroonga::storage_max_supported_key_length() const
 {
   MRN_DBUG_ENTER_METHOD();
-  DBUG_RETURN(HA_MAX_REC_LENGTH);
+  DBUG_RETURN(GRN_TABLE_MAX_KEY_SIZE);
 }
 
 uint ha_mroonga::max_supported_key_length() const
@@ -2173,7 +2173,7 @@ uint ha_mroonga::wrapper_max_supported_key_part_length() const
 uint ha_mroonga::storage_max_supported_key_part_length() const
 {
   MRN_DBUG_ENTER_METHOD();
-  DBUG_RETURN(HA_MAX_REC_LENGTH);
+  DBUG_RETURN(GRN_TABLE_MAX_KEY_SIZE);
 }
 
 uint ha_mroonga::max_supported_key_part_length() const
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-mysql-commit mailing list
Back to archive index