rroonga 2.1.0-x86-mingw32 → 2.1.1-x86-mingw32

data/vendor/local/share/doc/groonga/en/html/_sources/reference/executables/grntest.txt

@@ -134,7 +134,7 @@ grntest命令
 コマンドファイル
 ^^^^^^^^^^^^^^^^
 
-コマンドファイルは、groonga組み込みコマンドを1行に1つずつ記述したテキストファイルです。拡張子に制限はありません。groonga組み込みコマンドに関しては :doc:`/reference/commands` を参照してください。
+コマンドファイルは、groonga組み込みコマンドを1行に1つずつ記述したテキストファイルです。拡張子に制限はありません。groonga組み込みコマンドに関しては :doc:`/reference/command` を参照してください。
 
 サンプル
 ^^^^^^^^

data/vendor/local/share/doc/groonga/en/html/_sources/reference/executables/groonga-server-http.txt

@@ -48,7 +48,7 @@ GETメソッドのみが使用可能です。
 
 output_typeにはjson, tsv, xmlが指定可能です。
 
-command_versionはコマンドの仕様の互換性を指定します。詳細は :doc:`/reference/command_version` を参照してください。
+command_versionはコマンドの仕様の互換性を指定します。詳細は :doc:`/reference/command/command_version` を参照してください。
 
 返値
 ----

data/vendor/local/share/doc/groonga/en/html/_sources/reference/executables/groonga.txt

@@ -138,6 +138,8 @@ groongaのデータベースは、groongaコマンドかCライブラリイン
 
    スタンドアロンおよびクライアントモードの場合は、実行するコマンドとその引数をコマンドライン引数に指定できます。コマンドライン引数にcommandを与えなかった場合は、標準入力から一行ずつEOFに達するまでコマンド文字列を読み取り、順次実行します。
 
+.. _command-list-with-continuous-line:
+
 コマンド
 --------
 
@@ -154,6 +156,13 @@ groongaコマンドを通してデータベースを操作する命令をコマ
 
 標準入力からコマンド文字列を与える場合は、コマンド名と引数名と値は、空白( )で区切ります。空白や、記号「"'()\」のうちいずれかを含む値を指定したい場合は、シングルクォート(')かダブルクォート(")で値を囲みます。値として指定する文字列の中では、改行文字は'\n'に置き換えて指定します。また、引用符に使用した文字を値の中で指定する場合には、その文字の前にバックスラッシュ('\') を指定します。バックスラッシュ文字自身を値として指定する場合には、その前にバックスラッシュを指定します。
 
+You can write command list with continuous line which is represented by '\\' character.::
+
+  table_create --name Terms \
+               --flags TABLE_PAT_KEY \
+               --key_type ShortText \
+               --default_tokenizer TokenBigram
+
 組み込みコマンド
 ----------------
 

data/vendor/local/share/doc/groonga/en/html/_sources/reference/functions/geo_distance.txt

@@ -158,7 +158,7 @@ you want to calculate the value of distance between two points.
 
 You can specify the value of GeoPoint type. [#]_
 
-See :doc:`/reference/type` about GeoPoint.
+See :doc:`/reference/types` about GeoPoint.
 
 ``point2``
 """"""""""
@@ -169,7 +169,7 @@ you want to calculate the value of distance between two points.
 You can specify the value of GeoPoint type or 
 the string indicating the coordinate.
 
-See :doc:`/reference/type` about GeoPoint and the coordinate.
+See :doc:`/reference/types` about GeoPoint and the coordinate.
 
 Optional parameter
 ^^^^^^^^^^^^^^^^^^

data/vendor/local/share/doc/groonga/en/html/_sources/reference/grn_expr/script_syntax.txt

@@ -221,7 +221,7 @@ Its syntax is ``name(arugment1, argument2, ...)``.
 ``name(argument1, argument2, ...)`` calls a function that is named
 ``name`` with arguments ``argument1``, ``argument2`` and ``...``.
 
-See :doc:`/reference/functions/` for available functin list.
+See :doc:`/reference/function` for available functin list.
 
 Here is a simple exmaple.
 

data/vendor/local/share/doc/groonga/en/html/_sources/reference/normalizers.txt

@@ -0,0 +1,122 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: normalisers
+
+Normalizers
+===========
+
+Summary
+-------
+
+Groonga has normalizer module. It is used when tokenizing text and
+storing table key. For example, ``A`` and ``a`` are processed as the
+same character after normalization.
+
+Normalizer module can be added as a plugin. You can customize text
+normalization by registering your normalizer plugins to groonga.
+
+A normalizer module is attached to a table. A table can have zero or
+one normalizer module. You can attach a normalizer module to a table
+by :ref:`table-create-normalizer` option in
+:doc:`/reference/commands/table_create`.
+
+Here is an example ``table_create`` that uses ``NormalizerAuto``
+normalizer module:
+
+.. groonga-command
+.. include:: ../example/reference/normalizers/example-table-create.log
+.. table_create Dictionary TABLE_HASH_KEY ShortText --normalizer NormalizerAuto
+
+.. note::
+
+   Groonga 2.0.9 or earlier doesn't have ``--normalizer`` option in
+   ``table_create``. ``KEY_NORMALIZE`` flag was used instead.
+
+   You can open an old database by groonga 2.1.0 or later. An old
+   database means that the database is created by groonga 2.0.9 or
+   earlier. But you cannot open the opened old database by groonga
+   2.0.9 or earlier. Once you open the old database by groonga 2.1.0
+   or later, ``KEY_NORMALIZE`` flag information in the old database is
+   converted to normalizer information. So groogna 2.0.9 or earlier
+   cannot find ``KEY_NORMALIZE`` flag information in the opened old
+   database.
+
+Keys of a table that has a normalizer module are normalized:
+
+.. groonga-command
+.. include:: ../example/reference/normalizers/example-load.log
+.. load --table Dictionary
+.. [
+.. {"_key": "Apple"},
+.. {"_key": "black"},
+.. {"_key": "COLOR"}
+.. ]
+.. select Dictionary
+
+``NormalizerAuto`` normalizer normalizes a text as a downcased text.
+For example, ``"Apple"`` is normalized to ``"apple"``, ``"black"`` is
+normalized to ``"blank"`` and ``"COLOR"`` is normalized to
+``"color"``.
+
+If a table is a lexicon for fulltext search, tokenized tokens are
+normalized. Because tokens are stored as table keys. Table keys are
+normalized as described above.
+
+Built-in normalizers
+--------------------
+
+Here is a list of built-in-normalizers:
+
+  * ``NormalizerAuto``
+  * ``NormalizerNFKC51``
+
+``NormalizerAuto``
+^^^^^^^^^^^^^^^^^^
+
+Normally you should use ``NormalizerAuto``
+normalizer. ``NormalizerAuto`` was the normalizer for groonga 2.0.9 or
+earlier. ``KEY_NORMALIZE`` flag in ``table_create`` on groonga 2.0.9
+or earlier equals to ``--normalizer NormalizerAuto`` option in
+``table`` on groonga 2.1.0 or later.
+
+``NormalizerAuto`` supports all encoding. It uses Unicode NFKC
+(Normalization Form Compatibility Composition) for UTF-8 encoding
+text. It uses encoding specific original normalization for other
+encodings. The results of those original normalization are similar to
+NFKC.
+
+For example, half-width katakana (such as U+FF76 HALFWIDTH KATAKANA
+LETTER KA) + half-width katakana voiced sound mark (U+FF9E HALFWIDTH
+KATAKANA VOICED SOUND MARK) is normalized to full-width katakana with
+voiced sound mark (U+30AC KATAKANA LETTER GA). The former is two
+chracters but the latter is one character.
+
+Here is an example that uses ``NormalizerAuto`` normalizer:
+
+.. groonga-command
+.. include:: ../example/reference/normalizers/normalizer-auto.log
+.. table_create NormalLexicon TABLE_HASH_KEY ShortText --normalizer NormalizerAuto
+
+``NormalizerNFKC51``
+^^^^^^^^^^^^^^^^^^^^
+
+``NormalizerNFKC51`` normalizes texts by Unicode NFKC (Normalization
+Form Compatibility Composition) for Unicode version 5.1. It supports
+only UTF-8 encoding.
+
+Normally you don't need to use ``NormalizerNFKC51`` explicitly. You can
+use ``NormalizerAuto`` instead.
+
+Here is an example that uses ``NormalizerNFKC51`` normalizer:
+
+.. groonga-command
+.. include:: ../example/reference/normalizers/normalizer-nfkc51.log
+.. table_create NFKC51Lexicon TABLE_HASH_KEY ShortText --normalizer NormalizerNFKC51
+
+See also
+--------
+
+* :doc:`/reference/commands/table_create`

data/vendor/local/share/doc/groonga/en/html/_sources/reference/tables.txt

@@ -0,0 +1,163 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+Tables
+======
+
+Summary
+-------
+
+Table in groonga manages relation between ID and key. Groonga provides
+four table types. They are ``TABLE_NO_KEY``, ``TABLE_HASH_KEY``,
+``TABLE_PAT_KEY`` and ``TABLE_DAT_KEY``.
+
+All table except ``TABLE_NO_KEY`` provides both fast ID search by key
+and fast key search by ID. ``TABLE_NO_KEY`` doesn't support
+key. ``TABLE_NO_KEY`` only manages ID. So ``TABLE_NO_KEY`` doesn't
+provides ID search and key search.
+
+Characteristics
+---------------
+
+Here is a chracteristic table of all tables in groonga. (``TABLE_``
+prefix is omitted in the table.)
+
++--------------+------------+--------------+-------------+-------------+
+|              | ``NO_KEY`` | ``HASH_KEY`` | ``PAT_KEY`` | ``DAT_KEY`` |
++--------------+------------+--------------+-------------+-------------+
+| Data         | Array      | Hash table   | Patricia    | Double      |
+| structure    |            |              | trie        | array       |
+|              |            |              |             | trie        |
++--------------+------------+--------------+-------------+-------------+
+| ID           | o          | o            | o           | o           |
+| support      |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+| Key          | x          | o            | o           | o           |
+| support      |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+| Value        | o          | o            | o           | x           |
+| support      |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+| Key -> ID    | -          | oo           | x           | o           |
+| speed        |            |              |             |             |
+| (o -> fast)  |            |              |             |             |
+| (x -> slow)  |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+| Update       | ooo        | o            | o           | x           |
+| speed        |            |              |             |             |
+| (o -> fast)  |            |              |             |             |
+| (x -> slow)  |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+| Size         | ooo        | o            | oo          | x           |
+| (o -> small) |            |              |             |             |
+| (x -> large) |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+| Key          | -          | x            | x           | o           |
+| update       |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+| Common       | -          | x            | o           | o           |
+| prefix       |            |              |             |             |
+| search       |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+| Predictive   | -          | x            | o           | o           |
+| search       |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+| Range        | -          | x            | o           | o           |
+| search       |            |              |             |             |
++--------------+------------+--------------+-------------+-------------+
+
+``TABLE_NO_KEY``
+^^^^^^^^^^^^^^^^
+
+``TABLE_NO_KEY`` is very fast and very small but it doesn't support
+key. ``TABLE_NO_KEY`` is a only table that doesn't support key.
+
+You cannot use ``TABLE_NO_KEY`` for lexicon for fulltext search
+because lexicon stores tokens as key. ``TABLE_NO_KEY`` is useful for
+no key records such as log.
+
+``TABLE_HASH_KEY``
+^^^^^^^^^^^^^^^^^^
+
+``TABLE_HASH_KEY`` is fast but it doesn't support advanced search
+functions such as common prefix search and predictive search.
+
+``TABLE_HASH_KEY`` is useful for index for exact search such as tag
+search.
+
+``TABLE_PAT_KEY``
+^^^^^^^^^^^^^^^^^
+
+``TABLE_PAT_KEY`` is small and supports advanced search functions.
+
+``TABLE_PAT_KEY`` is useful for lexicon for fulltext search and
+index for range search.
+
+``TABLE_DAT_KEY``
+^^^^^^^^^^^^^^^^^
+
+``TABLE_DAT_KEY`` is fast and supports key update but it is large. It
+is not suitable for storing many records. ``TABLE_DAT_KEY`` is a only
+table that supports key update.
+
+``TABLE_DAT_KEY`` is used in groonga database. Groonga database needs
+to convert object name such as ``ShortText``, ``TokenBigram`` and
+table names to object ID. And groonga database needs to rename object
+name. Those features are implemented by ``TABLE_DAT_KEY``. The number
+of objects is small. So large data size demerit of ``TABLE_DAT_KEY``
+can be ignored.
+
+Record ID
+---------
+
+Record ID is assigned automatically. You cannot assign record ID.
+
+Record ID of deleted record may be reused.
+
+Valid record ID range is between 1 and 268435455. (1 and 268435455 are
+valid IDs.)
+
+Persistent table and temporary table
+------------------------------------
+
+Table is persistent table or temporary table.
+
+Persistent table
+^^^^^^^^^^^^^^^^
+
+Persistent table is named and registered to database. Records in
+persistent table aren't deleted after closing table or
+database.
+
+Persistent table can be created by
+:doc:`/reference/commands/table_create` command.
+
+Temporary table
+^^^^^^^^^^^^^^^
+
+Temporary table is anonymous. Records in temporary table are deleted
+after closing table. Temporary table is used to store search result,
+sort result, group (drilldown) result and so on. ``TABLE_HASH_KEY`` is
+used for search result and group result. ``TABLE_NO_KEY`` is used for
+sort result.
+
+Limitations
+-----------
+
+The max number of records is 268435455. You cannot add 268435456 or
+more records in a table.
+
+The max number of a key size is 4096byte. You cannot use 4097byte or
+larger key. You can use column instead of key for 4097byte or larger
+size data. ``Text`` and ``LargeText`` types supports 4097byte or
+larger size data.
+
+The max number of total key size is 4GiB. You need to split a table,
+split a database (sharding) or reduce each key size to handle 4GiB or
+more larger total key size.
+
+See also
+--------
+
+* :doc:`/reference/commands/table_create`

data/vendor/local/share/doc/groonga/en/html/_sources/server/http/comparison.txt

@@ -123,7 +123,7 @@ configuration to use ``/api/`` as prefix path::
 Custom command version
 ----------------------
 
-Groonga has :doc:`/reference/command_version` mechanism. It is for
+Groonga has :doc:`/reference/command/command_version` mechanism. It is for
 upgrading groonga commands with backward compatibility.
 
 :doc:`groonga` can change the default command veresion by

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

@@ -15,7 +15,7 @@ Groonga is a full text search engine but also serves as a column-oriented data s
 Overview
 --------
 
-The basic data types of groonga are roughly divided into 5 groups --- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see :doc:`/reference/type`.
+The basic data types of groonga are roughly divided into 5 groups --- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see :doc:`/reference/types`.
 
 In addition, groonga supports reference types and vector types. Reference types are designed for accessing other tables. Vector types are designed for storing a variable number of values in one element.
 
@@ -46,7 +46,7 @@ The following example creates a boolean type column and adds three records. Note
 Numeric types
 -------------
 
-The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see :doc:`/reference/type`. The default value of the numeric types is 0.
+The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see :doc:`/reference/types`. The default value of the numeric types is 0.
 
 The following example creates an Int8 column and a Float column, and then updates existing records. The :doc:`/reference/commands/load` command updates the weight column as expected. On the other hand, the price column values are different from the specified values because 15.9 is not an integer and 200 is too large. 15.9 is converted to 15 by removing the fractional part. 200 causes an overflow and the result becomes -56. Note that the result of an overflow/underflow is undefined.
 
@@ -65,7 +65,7 @@ The following example creates an Int8 column and a Float column, and then update
 String types
 ------------
 
-The string types are divided according to the maximum length. For more details, see :doc:`/reference/type`. The default value is the zero-length string.
+The string types are divided according to the maximum length. For more details, see :doc:`/reference/types`. The default value is the zero-length string.
 
 The following example creates a ShortText column and updates existing records. The third record has the default value because not updated.
 
@@ -99,7 +99,7 @@ The following example creates a Time column and updates existing records. The fi
 Longitude and latitude types
 ----------------------------
 
-The longitude and latitude types are divided according to the geographic coordinate system. For more details, see :doc:`/reference/type`. To represent a longitude and latitude, groonga uses a string formatted as follows:
+The longitude and latitude types are divided according to the geographic coordinate system. For more details, see :doc:`/reference/types`. To represent a longitude and latitude, groonga uses a string formatted as follows:
 
 * "longitude x latitude" in milliseconds (e.g.: "128452975x503157902")
 * "longitude x latitude" in degrees (e.g.: "35.6813819x139.7660839")

data/vendor/local/share/doc/groonga/en/html/_sources/tutorial/introduction.txt

@@ -93,7 +93,7 @@ A :doc:`/reference/commands/table_create` command creates a new table.
 
 In most cases, a table has a primary key which must be specified with its data type and index type. 
 
-There are various data types such as integers, strings, etc. See also :doc:`/reference/type` for more details. The index type determines the search performance and the availability of prefix searches. The details will be described later.
+There are various data types such as integers, strings, etc. See also :doc:`/reference/types` for more details. The index type determines the search performance and the availability of prefix searches. The details will be described later.
 
 Let's create a table. The following example creates a table with a primary key. The `name` parameter specifies the name of the table. The `flags` parameter specifies the index type for the primary key. The `key_type` parameter specifies the data type of the primary key.
 

data/vendor/local/share/doc/groonga/en/html/_static/doctools.js

@@ -61,6 +61,18 @@ jQuery.getQueryParameters = function(s) {
   return result;
 };
 
+/**
+ * small function to check if an array contains
+ * a given item.
+ */
+jQuery.contains = function(arr, item) {
+  for (var i = 0; i < arr.length; i++) {
+    if (arr[i] == item)
+      return true;
+  }
+  return false;
+};
+
 /**
  * highlight a given string on a jquery object by wrapping it in
  * span elements with the given class name.

data/vendor/local/share/doc/groonga/en/html/_static/searchtools.js

@@ -301,7 +301,7 @@ var Search = {
   },
 
   query : function(query) {
-    var stopwords = ["a","and","are","as","at","be","but","by","for","if","in","into","is","it","near","no","not","of","on","or","such","that","the","their","then","there","these","they","this","to","was","will","with"];
+    var stopwords = ["and","then","into","it","as","are","in","if","for","no","there","their","was","is","be","to","that","but","they","not","such","with","by","a","on","these","of","will","this","near","the","or","at"];
 
     // Stem the searchterms and add them to the correct list
     var stemmer = new Stemmer();
@@ -332,7 +332,7 @@ var Search = {
         hlterms.push(tmp[i].toLowerCase());
       }
       // only add if not already in the list
-      if (!$u.contains(toAppend, word))
+      if (!$.contains(toAppend, word))
         toAppend.push(word);
     };
     var highlightstring = '?highlight=' + $.urlencode(hlterms.join(" "));
@@ -399,7 +399,7 @@ var Search = {
       // search result.
       for (var i = 0; i < excluded.length; i++) {
         if (terms[excluded[i]] == file ||
-            $u.contains(terms[excluded[i]] || [], file)) {
+            $.contains(terms[excluded[i]] || [], file)) {
           valid = false;
           break;
         }