From: Date: August 3 2007 12:50am
Subject: bk commit into 5.1 tree (svoj:1.2569) BUG#27040
List-Archive: http://lists.mysql.com/commits/32025
X-Bug: 27040
Message-Id: <20070802225026.70DA5BB1@april.pils.ru>

Below is the list of changes that have just been committed into a local
5.1 repository of svoj. When svoj does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet@stripped, 2007-08-03 03:50:19+05:00, svoj@stripped +1 -0
  BUG#27040 - Incorrect FTS parser name output
  
  When a table uses two (or more) fulltext keys with different fulltext parsers,
  all fulltext keys (excluding those that use built-in parser) were using first
  parser that was mentioned in .frm.
  
  With this fix fulltext keys use proper (assigned during create table) fulltext
  parser.
  
  This code was contributed by Yoshinori Matsunobu ymatsunobu@stripped
  on 2007-03-12 The copyright was assigned and transferred under the
  terms of the MySQL Contributor License Agreement.

  sql/table.cc@stripped, 2007-08-03 03:50:09+05:00, svoj@stripped +1 -0
    Shift extra data segment buffer pointer by parser name length to restore
    next key parser name correctly.

diff -Nrup a/sql/table.cc b/sql/table.cc
--- a/sql/table.cc	2007-07-26 05:23:30 +05:00
+++ b/sql/table.cc	2007-08-03 03:50:09 +05:00
@@ -918,6 +918,7 @@ static int open_binary_frm(THD *thd, TAB
         }
         parser_name.str= (char*) next_chunk;
         parser_name.length= strlen((char*) next_chunk);
+        next_chunk+= parser_name.length + 1;
         keyinfo->parser= my_plugin_lock_by_name(NULL, &parser_name,
                                                 MYSQL_FTPARSER_PLUGIN);
         if (! keyinfo->parser)