rroonga 1.2.5-x86-mingw32 → 1.2.7-x86-mingw32

data/vendor/local/share/doc/groonga/ja/html/_sources/suggest/correction.txt

@@ -0,0 +1,148 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. % groonga-suggest-create-dataset /tmp/groonga-databases/correction query
+.. database: correction
+
+Correction
+==========
+
+This section describes about the following correction
+features:
+
+* How it works
+* How to use
+* How to learn
+
+How it works
+------------
+
+The correction feature uses three searches to compute corrected
+words:
+
+  1. Cooccurrence search against learned data.
+  2. Similar search against registered words. (optional)
+
+Cooccurrence search
+^^^^^^^^^^^^^^^^^^^
+
+Cooccurrence search can find registered words from user's
+wrong input. It uses user submit sequences that will be
+learned from query logs, access logs and so on.
+
+For example, there are the following user submissions:
+
++-------------------+---------------------------+
+|  query            |    time                   |
++===================+===========================+
+| serach (typo!)    | 2011-08-10T22:20:50+09:00 |
++-------------------+---------------------------+
+| search (fixed!)   | 2011-08-10T22:20:52+09:00 |
++-------------------+---------------------------+
+
+Groonga creates the following correction pair from the above
+submissions:
+
++----------+--------------------+
+|  input   |   corrected word   |
++==========+====================+
+|serach    |search              |
++----------+--------------------+
+
+Groonga treats continuous submissions within a minute as
+input correction by user. Not submitted user input sequence
+between two submissions isn't used as learned data for
+correction.
+
+If an user inputs "serach" and cooccurrence search returns
+"search" because "serach" is in input column and
+corresponding corrected word column value is "search".
+
+Similar search
+^^^^^^^^^^^^^^
+
+Similar search can find registered words that has one or
+more the same tokens as user input. TokenBigram tokenizer is
+used for tokenization because suggest dataset schema
+created by :doc:`/executables/groonga-suggest-create-dataset`
+uses TokenBigram tokenizer as the default tokenizer.
+
+For example, there is a registered query "search engine". An
+user can find "search engine" by "web search service",
+"sound engine" and so on. Because "search engine" and "web
+search engine" have the same token "search" and "search
+engine" and "sound engine" have the same token "engine".
+
+"search engine" is tokenized to "search" and "engine"
+tokens. (Groonga's TokenBigram tokenizer doesn't tokenize
+two characters for continuous alphabets and continuous
+digits for reducing search
+noise. TokenBigramSplitSymbolAlphaDigit tokenizer should be
+used to ensure tokenizing to two characters.) "web search
+service" is tokenized to "web", "search" and
+"service". "sound engine" is tokenized to "sound" and
+"engine".
+
+How to use
+----------
+
+.. groonga-command
+.. load --table event_query --each 'suggest_preparer(_id, type, item, sequence, time, pair_query)'
+.. [
+.. {"sequence": "1", "time": 1312950803.86057, "item": "s"},
+.. {"sequence": "1", "time": 1312950803.96857, "item": "sa"},
+.. {"sequence": "1", "time": 1312950804.26057, "item": "sae"},
+.. {"sequence": "1", "time": 1312950804.56057, "item": "saer"},
+.. {"sequence": "1", "time": 1312950804.76057, "item": "saerc"},
+.. {"sequence": "1", "time": 1312950805.76057, "item": "saerch", "type": "submit"},
+.. {"sequence": "1", "time": 1312950809.76057, "item": "serch"},
+.. {"sequence": "1", "time": 1312950810.86057, "item": "search", "type": "submit"}
+.. ]
+
+Groonga provides :doc:`/commands/suggest` command to use
+correction. `--type correct` option requests corrections.
+
+For example, here is an command to get correction results by
+"saerch":
+
+.. groonga-command
+.. include:: ../example/correction-1.log
+.. suggest --table item_query --column kana --types correction --frequency_threshold 1 --query saerch
+
+How it learns
+-------------
+
+Cooccurrence search uses learned data. They are based on
+query logs, access logs and so on. To create learned data,
+groonga needs user submit inputs with time stamp.
+
+For example, an user wants to search by "search" but the
+user has typo "saerch" before inputs the correct query. The
+user inputs the query with the following sequence:
+
+  1. 2011-08-10T13:33:23+09:00: s
+  2. 2011-08-10T13:33:23+09:00: sa
+  3. 2011-08-10T13:33:24+09:00: sae
+  4. 2011-08-10T13:33:24+09:00: saer
+  5. 2011-08-10T13:33:24+09:00: saerc
+  6. 2011-08-10T13:33:25+09:00: saerch (submit!)
+  7. 2011-08-10T13:33:29+09:00: serch (correcting...)
+  8. 2011-08-10T13:33:30+09:00: search (submit!)
+
+Groonga can be learned from the input sequence by the
+following command::
+
+  load --table event_query --each 'suggest_preparer(_id, type, item, sequence, time, pair_query)'
+  [
+  {"sequence": "1", "time": 1312950803.86057, "item": "s"},
+  {"sequence": "1", "time": 1312950803.96857, "item": "sa"},
+  {"sequence": "1", "time": 1312950804.26057, "item": "sae"},
+  {"sequence": "1", "time": 1312950804.56057, "item": "saer"},
+  {"sequence": "1", "time": 1312950804.76057, "item": "saerc"},
+  {"sequence": "1", "time": 1312950805.76057, "item": "saerch", "type": "submit"},
+  {"sequence": "1", "time": 1312950809.76057, "item": "serch"},
+  {"sequence": "1", "time": 1312950810.86057, "item": "search", "type": "submit"}
+  ]
+

data/vendor/local/share/doc/groonga/ja/html/_sources/suggest/introduction.txt

@@ -0,0 +1,94 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+Introduction
+============
+
+The suggest feature in groonga provides the following features:
+
+* Completion
+* Correction
+* Suggestion
+
+Completion
+----------
+
+Completion helps user input. If user inputs a partial word,
+groonga can return complete words from registered
+words.
+
+For example, there are registered words:
+
+* "groonga"
+* "complete"
+* "correction"
+* "suggest"
+
+An user inputs "co" and groonga returns "complete" and
+"correction" because they starts with "co".
+
+An user inputs "sug" and groonga returns "suggest" because
+"suggest" starts with "sug".
+
+An user inputs "ab" and groonga returns nothing because no
+word starts with "ab".
+
+Correction
+----------
+
+Correction also helps user input. If user inputs a wrong
+word, groonga can return correct words from registered
+correction pairs.
+
+For example, there are registered correction pairs:
+
++------------+--------------+
+| wrong word | correct word |
++============+==============+
+| grroonga   | groonga      |
+| gronga     | groonga      |
+| gronnga    | groonga      |
++------------+--------------+
+
+An user inputs "gronga" and groonga returns "groonga" because
+"gronga" is in wrong word and corresponding correct word is
+"groonga".
+
+An user inputs "roonga" and groonga returns nothing because
+"roonga" isn't in wrong word.
+
+Suggestion
+----------
+
+Suggestion helps that user filters many found documents. If
+user inputs a query, groonga can return new queries that has
+more additional keywords from registered related query
+pairs.
+
+For example, there are registered related query pairs:
+
++----------------------------+--------------------------+
+|          keyword           |      related query       |
++============================+==========================+
+| groonga                    | groonga search engine    |
++----------------------------+--------------------------+
+| search                     | Google search            |
++----------------------------+--------------------------+
+| speed                      | groonga speed            |
++----------------------------+--------------------------+
+
+An user inputs "groonga" and groonga returns "groonga search
+engine" because "groonga" is in keyword column and related
+query column is "groonga search engine".
+
+An user inputs "MySQL" and groonga returns nothing because
+"MySQL" isn't in keyword column values.
+
+Learning
+--------
+
+The suggest feature requires registered data before using
+the feature. Those data can be registered from user inputs.
+Gronnga-suggest-httpd and groonga-suggest-learner commands
+are provided for the propose.

data/vendor/local/share/doc/groonga/ja/html/_sources/suggest/suggestion.txt

@@ -0,0 +1,115 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. % groonga-suggest-create-dataset /tmp/groonga-databases/suggestion query
+.. database: suggestion
+
+Suggestion
+==========
+
+This section describes about the following completion
+features:
+
+* How it works
+* How to use
+* How to learn
+
+How it works
+------------
+
+The suggestion feature uses a search to compute suggested
+words:
+
+  1. Cooccurrence search against learned data.
+
+Cooccurrence search
+^^^^^^^^^^^^^^^^^^^
+
+Cooccurrence search can find related words from user's
+input. It uses user submissions that will be learned
+from query logs, access logs and so on.
+
+For example, there are the following user submissions:
+
++----------------------+
+|  query               |
++======================+
+| search engine        |
++----------------------+
+| web search realtime  |
++----------------------+
+
+Groonga creates the following suggestion pairs:
+
++----------+------------------------------------+
+|  input   |          suggested words           |
++==========+====================================+
+|search    |search engine                       |
++----------+------------------------------------+
+|engine    |search engine                       |
++----------+------------------------------------+
+|web       |web search realtime                 |
++----------+------------------------------------+
+|search    |web search realtime                 |
++----------+------------------------------------+
+|realtime  |web search realtime                 |
++----------+------------------------------------+
+
+Those pairs are created by the following steps:
+
+  1. Tokenizes user input query by TokenDelimit tokenizer
+     that uses a space as token delimiter. (e.g. "search
+     engine" is tokenized to two tokens "search" and
+     "engine".)
+  2. Creates a pair that is consists of a token and original
+     query for each token.
+
+If an user inputs "search" and cooccurrence search returns
+"search engine" and "web search realtime" because "search" is
+in two input columns and corresponding suggested word
+columns have "search engine" and "web search realtime".
+
+How to use
+----------
+
+.. groonga-command
+.. load --table event_query --each 'suggest_preparer(_id, type, item, sequence, time, pair_query)'
+.. [
+.. {"sequence": "1", "time": 1312950803.86057, "item": "search engine", "type": "submit"},
+.. {"sequence": "1", "time": 1312950808.86057, "item": "web search realtime", "type": "submit"}
+.. ]
+
+Groonga provides :doc:`/commands/suggest` command to use
+suggestion. `--type suggest` option requests suggestion
+
+For example, here is an command to get suggestion results by
+"search":
+
+.. groonga-command
+.. include:: ../example/suggestion-1.log
+.. suggest --table item_query --column kana --types suggest --frequency_threshold 1 --query search
+
+How it learns
+-------------
+
+Cooccurrence search uses learned data. They are based on
+query logs, access logs and so on. To create learned data,
+groonga needs user input sequence with time stamp and user
+submit input with time stamp.
+
+For example, an user wants to search by "engine". The user
+inputs the query with the following sequence:
+
+  1. 2011-08-10T13:33:23+09:00: search engine (submit)
+  2. 2011-08-10T13:33:28+09:00: web search realtime (submit)
+
+Groonga can be learned from the submissions by the
+following command::
+
+  load --table event_query --each 'suggest_preparer(_id, type, item, sequence, time, pair_query)'
+  [
+  {"sequence": "1", "time": 1312950803.86057, "item": "search engine", "type": "submit"},
+  {"sequence": "1", "time": 1312950808.86057, "item": "web search realtime", "type": "submit"}
+  ]

data/vendor/local/share/doc/groonga/ja/html/_sources/suggest/tutorial.txt

@@ -0,0 +1,8 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+Tutorial
+========
+
+TODO...

data/vendor/local/share/doc/groonga/ja/html/_sources/suggest.txt

@@ -0,0 +1,22 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+Suggest
+=======
+
+.. note::
+
+   The suggest feature specification isn't stable. The
+   specification may be changed.
+
+Groonga has the suggest feature. This section describes how to use it and how it works.
+
+.. toctree::
+   :maxdepth: 2
+
+   suggest/introduction
+   suggest/tutorial
+   suggest/completion
+   suggest/correction
+   suggest/suggestion

data/vendor/local/share/doc/groonga/ja/html/_sources/tutorial/tutorial01.txt

@@ -3,6 +3,7 @@
 .. highlightlang:: none
 
 .. groonga-command
+.. database: tutorial
 .. table_remove Site
 .. table_remove Terms
 
@@ -73,7 +74,7 @@ groonga実行ファイルやgroongaサーバを介して様々なコマンドを
 
 書式2において、空白や、記号「"'()\」のうちいずれかを含む値を指定したい場合は、シングルクォート(')かダブルクォート(")で値を囲みます。
 
-詳しくは、 :doc:`/execfile` のコマンドの項を参考にしてください。
+詳しくは、 :doc:`/executables/groonga` のコマンドの項を参考にしてください。
 
 主なコマンド
 ------------

data/vendor/local/share/doc/groonga/ja/html/_static/groonga.css

@@ -103,6 +103,7 @@ div.header div.facebook-buttons
     padding-left: 10px;
     width: 320px;
     height: 90px;
+    overflow: hidden;
 }
 
 div.header div.other-language-links

data/vendor/local/share/doc/groonga/ja/html/characteristic.html

@@ -9,7 +9,7 @@
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
     
-    <title>1. groongaの特徴 &mdash; groonga v1.2.4ドキュメント</title>
+    <title>1. groongaの特徴 &mdash; groonga v1.2.5ドキュメント</title>
     
     <link rel="stylesheet" href="_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="_static/pygments.css" type="text/css" />
@@ -17,7 +17,7 @@
     <script type="text/javascript">
       var DOCUMENTATION_OPTIONS = {
         URL_ROOT:    '',
-        VERSION:     '1.2.4',
+        VERSION:     '1.2.5',
         COLLAPSE_INDEX: false,
         FILE_SUFFIX: '.html',
         HAS_SOURCE:  true
@@ -28,7 +28,7 @@
     <script type="text/javascript" src="_static/doctools.js"></script>
     <script type="text/javascript" src="_static/translations.js"></script>
     <link rel="shortcut icon" href="_static/favicon.ico"/>
-    <link rel="top" title="groonga v1.2.4ドキュメント" href="index.html" />
+    <link rel="top" title="groonga v1.2.5ドキュメント" href="index.html" />
     <link rel="next" title="2. インストール" href="install.html" />
     <link rel="prev" title="groonga ドキュメント" href="index.html" /> 
   </head>
@@ -62,7 +62,7 @@
         <li class="right" >
           <a href="index.html" title="groonga ドキュメント"
              accesskey="P">前へ</a> |</li>
-        <li><a href="index.html">groonga v1.2.4ドキュメント</a> &raquo;</li> 
+        <li><a href="index.html">groonga v1.2.5ドキュメント</a> &raquo;</li> 
       </ul>
     </div>  
 
@@ -174,7 +174,7 @@
         <li class="right" >
           <a href="index.html" title="groonga ドキュメント"
              >前へ</a> |</li>
-        <li><a href="index.html">groonga v1.2.4ドキュメント</a> &raquo;</li> 
+        <li><a href="index.html">groonga v1.2.5ドキュメント</a> &raquo;</li> 
       </ul>
     </div>
     <div class="footer">

data/vendor/local/share/doc/groonga/ja/html/command_version.html

@@ -9,7 +9,7 @@
   <head>
     <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
     
-    <title>5.2.1. コマンドバージョン &mdash; groonga v1.2.4ドキュメント</title>
+    <title>6.2.1. コマンドバージョン &mdash; groonga v1.2.5ドキュメント</title>
     
     <link rel="stylesheet" href="_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="_static/pygments.css" type="text/css" />
@@ -17,7 +17,7 @@
     <script type="text/javascript">
       var DOCUMENTATION_OPTIONS = {
         URL_ROOT:    '',
-        VERSION:     '1.2.4',
+        VERSION:     '1.2.5',
         COLLAPSE_INDEX: false,
         FILE_SUFFIX: '.html',
         HAS_SOURCE:  true
@@ -28,10 +28,10 @@
     <script type="text/javascript" src="_static/doctools.js"></script>
     <script type="text/javascript" src="_static/translations.js"></script>
     <link rel="shortcut icon" href="_static/favicon.ico"/>
-    <link rel="top" title="groonga v1.2.4ドキュメント" href="index.html" />
-    <link rel="up" title="5.2. コマンド" href="commands.html" />
-    <link rel="next" title="5.2.2. cache_limit" href="commands/cache_limit.html" />
-    <link rel="prev" title="5.2. コマンド" href="commands.html" /> 
+    <link rel="top" title="groonga v1.2.5ドキュメント" href="index.html" />
+    <link rel="up" title="6.2. コマンド" href="commands.html" />
+    <link rel="next" title="6.2.2. cache_limit" href="commands/cache_limit.html" />
+    <link rel="prev" title="6.2. コマンド" href="commands.html" /> 
   </head>
   <body>
 <div class="header">
@@ -58,14 +58,14 @@
           <a href="genindex.html" title="総合索引"
              accesskey="I">索引</a></li>
         <li class="right" >
-          <a href="commands/cache_limit.html" title="5.2.2. cache_limit"
+          <a href="commands/cache_limit.html" title="6.2.2. cache_limit"
              accesskey="N">次へ</a> |</li>
         <li class="right" >
-          <a href="commands.html" title="5.2. コマンド"
+          <a href="commands.html" title="6.2. コマンド"
              accesskey="P">前へ</a> |</li>
-        <li><a href="index.html">groonga v1.2.4ドキュメント</a> &raquo;</li>
-          <li><a href="reference.html" >5. リファレンスマニュアル</a> &raquo;</li>
-          <li><a href="commands.html" accesskey="U">5.2. コマンド</a> &raquo;</li> 
+        <li><a href="index.html">groonga v1.2.5ドキュメント</a> &raquo;</li>
+          <li><a href="reference.html" >6. リファレンスマニュアル</a> &raquo;</li>
+          <li><a href="commands.html" accesskey="U">6.2. コマンド</a> &raquo;</li> 
       </ul>
     </div>  
 
@@ -75,16 +75,16 @@
           <div class="body">
             
   <div class="section" id="id1">
-<h1>5.2.1. コマンドバージョン<a class="headerlink" href="#id1" title="このヘッドラインへのパーマリンク">¶</a></h1>
+<h1>6.2.1. コマンドバージョン<a class="headerlink" href="#id1" title="このヘッドラインへのパーマリンク">¶</a></h1>
 <div class="section" id="id2">
-<h2>5.2.1.1. 概要<a class="headerlink" href="#id2" title="このヘッドラインへのパーマリンク">¶</a></h2>
+<h2>6.2.1.1. 概要<a class="headerlink" href="#id2" title="このヘッドラインへのパーマリンク">¶</a></h2>
 <p>groonga1.1からコマンドバージョンという概念が導入されます。コマンドバージョンは、selectやloadなどのgroongaのコマンドの仕様の互換性を表します。groongaパッケージのバージョンが新しくなったとしても、同一のコマンドバージョンが使用可能であるなら、すべてのコマンドについて互換性が保証されます。コマンドバージョンが異なれば、同じ名前のコマンドであっても、動作に互換性がない可能性があります。</p>
 <p>あるバージョンのgroongaは、二つのコマンドバージョンを同時にサポートするようになります。
 使用するコマンドバージョンは、groongaを起動する際のコマンドラインオプションないしコンフィグファイルにdefault-commnad-versionパラメータを与えることによって指定できます。また、個々のコマンドを実行する際に、command_versionパラメータを与えることによっても指定することができます。</p>
 <p>コマンドバージョンは1からはじまり、更新されるたびに1ずつ大きくなります。現状のgroongaのコマンドの仕様はcommand-version 1という扱いになります。次回提供するgroongaは、command-version 1とcommand-version 2の二つをサポートすることになります。</p>
 </div>
 <div class="section" id="id3">
-<h2>5.2.1.2. バージョンの位置づけ<a class="headerlink" href="#id3" title="このヘッドラインへのパーマリンク">¶</a></h2>
+<h2>6.2.1.2. バージョンの位置づけ<a class="headerlink" href="#id3" title="このヘッドラインへのパーマリンク">¶</a></h2>
 <p>あるバージョンのgroongaにおいてサポートされるコマンドバージョンは、develop, stable,deprecatedのいずれかの位置づけとなります。</p>
 <dl class="docutils">
 <dt>develop</dt>
@@ -109,10 +109,10 @@ groonga1.5: command-version3=stable     command-version4=develop
 <p>groongaプロセス起動時に、default-command-versionパラメータにstable扱いでないコマンドバージョンを指定した場合には、警告メッセージがログファイルに出力されます。また、サポート範囲外のコマンドバージョンを指定した場合にはエラーとなり、プロセスは速やかに停止します。</p>
 </div>
 <div class="section" id="id4">
-<h2>5.2.1.3. コマンドバージョンの指定方法<a class="headerlink" href="#id4" title="このヘッドラインへのパーマリンク">¶</a></h2>
+<h2>6.2.1.3. コマンドバージョンの指定方法<a class="headerlink" href="#id4" title="このヘッドラインへのパーマリンク">¶</a></h2>
 <p>コマンドバージョンの指定方法はgroonga実行モジュールの引数として指定する方法と各コマンドの引数として指定する方法があります。</p>
 <div class="section" id="default-command-version">
-<h3>5.2.1.3.1. default-command-versionパラメータ<a class="headerlink" href="#default-command-version" title="このヘッドラインへのパーマリンク">¶</a></h3>
+<h3>6.2.1.3.1. default-command-versionパラメータ<a class="headerlink" href="#default-command-version" title="このヘッドラインへのパーマリンク">¶</a></h3>
 <p>groonga実行モジュールの引数としてdefault-command-versionパラメータを指定できます。
 (configファイルの中に指定することも可能です)</p>
 <p>実行例:</p>
@@ -122,7 +122,7 @@ groonga1.5: command-version3=stable     command-version4=develop
 <p>そのプロセスで実行するすべてのコマンドについて、デフォルトのコマンドバージョンとして指定されたバージョンを使用します。指定されたコマンドバージョンがstableであった場合にはなんのメッセージも表示されずそのまま起動します。指定されたコマンドバージョンがdevelopあるいはdeprecatedであった場合には、groonga.logファイルに警告メッセージを出力します。指定されたコマンドバージョンがサポート対象外であった場合には標準エラー出力にエラーメッセージを出力し、プロセスは速やかに終了します。</p>
 </div>
 <div class="section" id="command-version">
-<h3>5.2.1.3.2. command_versionパラメータ<a class="headerlink" href="#command-version" title="このヘッドラインへのパーマリンク">¶</a></h3>
+<h3>6.2.1.3.2. command_versionパラメータ<a class="headerlink" href="#command-version" title="このヘッドラインへのパーマリンク">¶</a></h3>
 <p>select,loadなどのすべてのgroongaコマンドにcommand_versionが指定できます。</p>
 <p>実行例:</p>
 <div class="highlight-none"><div class="highlight"><pre>select --command_version 1 --table tablename
@@ -141,12 +141,12 @@ groonga1.5: command-version3=stable     command-version4=develop
         <div class="sphinxsidebarwrapper">
   <h3><a href="index.html">目次</a></h3>
   <ul>
-<li><a class="reference internal" href="#">5.2.1. コマンドバージョン</a><ul>
-<li><a class="reference internal" href="#id2">5.2.1.1. 概要</a></li>
-<li><a class="reference internal" href="#id3">5.2.1.2. バージョンの位置づけ</a></li>
-<li><a class="reference internal" href="#id4">5.2.1.3. コマンドバージョンの指定方法</a><ul>
-<li><a class="reference internal" href="#default-command-version">5.2.1.3.1. default-command-versionパラメータ</a></li>
-<li><a class="reference internal" href="#command-version">5.2.1.3.2. command_versionパラメータ</a></li>
+<li><a class="reference internal" href="#">6.2.1. コマンドバージョン</a><ul>
+<li><a class="reference internal" href="#id2">6.2.1.1. 概要</a></li>
+<li><a class="reference internal" href="#id3">6.2.1.2. バージョンの位置づけ</a></li>
+<li><a class="reference internal" href="#id4">6.2.1.3. コマンドバージョンの指定方法</a><ul>
+<li><a class="reference internal" href="#default-command-version">6.2.1.3.1. default-command-versionパラメータ</a></li>
+<li><a class="reference internal" href="#command-version">6.2.1.3.2. command_versionパラメータ</a></li>
 </ul>
 </li>
 </ul>
@@ -155,10 +155,10 @@ groonga1.5: command-version3=stable     command-version4=develop
 
   <h4>前のトピックへ</h4>
   <p class="topless"><a href="commands.html"
-                        title="前の章へ">5.2. コマンド</a></p>
+                        title="前の章へ">6.2. コマンド</a></p>
   <h4>次のトピックへ</h4>
   <p class="topless"><a href="commands/cache_limit.html"
-                        title="次の章へ">5.2.2. cache_limit</a></p>
+                        title="次の章へ">6.2.2. cache_limit</a></p>
   <h3>このページ</h3>
   <ul class="this-page-menu">
     <li><a href="_sources/command_version.txt"
@@ -188,14 +188,14 @@ groonga1.5: command-version3=stable     command-version4=develop
           <a href="genindex.html" title="総合索引"
              >索引</a></li>
         <li class="right" >
-          <a href="commands/cache_limit.html" title="5.2.2. cache_limit"
+          <a href="commands/cache_limit.html" title="6.2.2. cache_limit"
              >次へ</a> |</li>
         <li class="right" >
-          <a href="commands.html" title="5.2. コマンド"
+          <a href="commands.html" title="6.2. コマンド"
              >前へ</a> |</li>
-        <li><a href="index.html">groonga v1.2.4ドキュメント</a> &raquo;</li>
-          <li><a href="reference.html" >5. リファレンスマニュアル</a> &raquo;</li>
-          <li><a href="commands.html" >5.2. コマンド</a> &raquo;</li> 
+        <li><a href="index.html">groonga v1.2.5ドキュメント</a> &raquo;</li>
+          <li><a href="reference.html" >6. リファレンスマニュアル</a> &raquo;</li>
+          <li><a href="commands.html" >6.2. コマンド</a> &raquo;</li> 
       </ul>
     </div>
     <div class="footer">