rroonga 5.0.0-x64-mingw32 → 5.0.1-x64-mingw32

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

@@ -57,7 +57,7 @@ There are required parameters, ``tokenizer`` and ``string``.
 ``tokenizer``
 """""""""""""
 
-It specifies the tokenizer name. ``tokenize`` command uses the
+Specifies the tokenizer name. ``tokenize`` command uses the
 tokenizer that is named ``tokenizer``.
 
 See :doc:`/reference/tokenizers` about built-in tokenizers.
@@ -78,7 +78,7 @@ registering ``tokenizers/kytea``.
 ``string``
 """"""""""
 
-It specifies any string which you want to tokenize.
+Specifies any string which you want to tokenize.
 
 If you want to include spaces in ``string``, you need to quote
 ``string`` by single quotation (``'``) or double quotation (``"``).
@@ -99,7 +99,7 @@ There are optional parameters.
 ``normalizer``
 """"""""""""""
 
-It specifies the normalizer name. ``tokenize`` command uses the
+Specifies the normalizer name. ``tokenize`` command uses the
 normalizer that is named ``normalizer``. Normalizer is important for
 N-gram family tokenizers such as ``TokenBigram``.
 
@@ -140,7 +140,7 @@ to lower case characters. For example, ``fu`` is a token.
 ``flags``
 """""""""
 
-It specifies a tokenization customize options. You can specify
+Specifies a tokenization customize options. You can specify
 multiple options separated by "``|``". For example,
 ``NONE|ENABLE_TOKENIZED_DELIMITER``.
 
@@ -178,7 +178,7 @@ tokenized delimiter.
 ``mode``
 """"""""
 
-It specifies a tokenize mode. If the mode is specified ``ADD``, the text
+Specifies a tokenize mode. If the mode is specified ``ADD``, the text
 is tokenized by the rule that adding a document. If the mode is specified
 ``GET``, the text is tokenized by the rule that searching a document. If
 the mode is omitted, the text is tokenized by the ``ADD`` mode.
@@ -206,7 +206,7 @@ The last alphabet is tokenized by two characters.
 ``token_filters``
 """""""""""""""""
 
-It specifies the token filter names. ``tokenize`` command uses the
+Specifies the token filter names. ``tokenize`` command uses the
 tokenizer that is named ``token_filters``.
 
 See :doc:`/reference/token_filters` about token filters.

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

@@ -78,7 +78,7 @@ There is required parameter, ``target_name``.
 ``target_name``
 """""""""""""""
 
-It specifies the name of table or column.
+Specifies the name of table or column.
 
 Return value
 ------------

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

@@ -5,50 +5,71 @@
 groonga command
 ===============
 
-名前
-----
+Summary
+-------
 
 groonga - 列指向データベース機能を持つ全文検索エンジンソフトウェア
 
-書式
-----
+Groongaは列指向のデータベース機能を持つ高速でスケーラブルな全文検索エンジンです。
+Groongaのデータベースは、groongaコマンドかCライブラリインタフェースを通して操作することができます。このマニュアルページでは、groongaコマンドの使い方について説明します。
+
+Syntax
+------
 
 ::
 
  groonga [options] [dest] [command [args]]
 
-説明
-----
-
-Groongaは列指向のデータベース機能を持つ高速でスケーラブルな全文検索エンジンです。
-Groongaのデータベースは、groongaコマンドかCライブラリインタフェースを通して操作することができます。このマニュアルページでは、groongaコマンドの使い方について説明します。
-
-オプション
-----------
+Options
+-------
 
 .. cmdoption:: -n
 
-   新たなデータベースを作成します。
+   Creates new database.
 
 .. cmdoption:: -c
 
-   クライアントモードで実行します。
+   Executes ``groonga`` command in client mode.
 
 .. cmdoption:: -s
 
-   サーバモードで実行します。
+   Executes ``groonga`` command in server mode. Use "Ctrl+C" to stop the ``groonga`` process.
 
 .. cmdoption:: -d
 
-   デーモンモードで実行します。(forkする点がサーバモードと異なる)
+   Executes ``groonga`` command in daemon mode. In contrast to server mode, ``groonga`` command forks in daemon mode. For example, to stop local daemon process, use "curl http://127.0.0.1:10041/d/shutdown".
 
 .. cmdoption:: -e, --encoding <encoding>
 
-   データベースで使用する文字エンコーディング方式を指定します。新たなデータベースを作成する時のみ有効です。none, euc, utf8, sjis, latin, koi8rのいずれかが指定できます。
+   Specifies encoding which is used for Groonga database. This option is effective when you create new Groonga database.  This parameter specifies one of the following values: ``none``, ``euc``, ``utf8``, ``sjis``, ``latin`` or ``koi8r``.
 
 .. cmdoption:: -l, --log-level <log level>
 
-   ログレベルを指定します。0〜8までの数値が指定可能で、数が大きいほど多くのログが出力されます。
+   Specifies log level. A integer value between 0 and 8. The meaning of value is:
+
+.. list-table::
+   :header-rows: 1
+
+   * - log level
+     - description
+   * - 0
+     - Nothing
+   * - 1
+     - Emergency
+   * - 2
+     - Alert
+   * - 3
+     - Critical
+   * - 4
+     - Error
+   * - 5
+     - Warning
+   * - 6
+     - Notice
+   * - 7
+     - Info
+   * - 8
+     - Debug
 
 .. cmdoption:: -a, --address <ip/hostname>
 
@@ -125,8 +146,8 @@ Groongaのデータベースは、groongaコマンドかCライブラリイン
 
    検索の挙動をエスカレーションする閾値を指定します。(デフォルトは0です)
 
-引数
-----
+Command line parameters
+-----------------------
 
 .. cmdoption:: dest
 
@@ -140,8 +161,8 @@ Groongaのデータベースは、groongaコマンドかCライブラリイン
 
 .. _command-list-with-continuous-line:
 
-コマンド
---------
+Command
+-------
 
 groongaコマンドを通してデータベースを操作する命令をコマンドと呼びます。コマンドは主にC言語で記述され、groongaプロセスにロードすることによって使用できるようになります。
 それぞれのコマンドは一意な名前と、0個以上の引数を持ちます。
@@ -163,8 +184,8 @@ You can write command list with continuous line which is represented by '\\' cha
                --key_type ShortText \
                --default_tokenizer TokenBigram
 
-組み込みコマンド
-----------------
+Builtin command
+---------------
 
 以下のコマンドは組み込みコマンドとして予め定義されています。
 
@@ -214,8 +235,8 @@ You can write command list with continuous line which is represented by '\\' cha
    ロックを解除します。
 
 
-例
---
+Usage
+-----
 
 新しいデータベースを作成します。::
 

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

@@ -85,30 +85,30 @@ There are five required parameters, ``column_or_value``, and ``min``, ``min_bord
 ``column_or_value``
 ^^^^^^^^^^^^^^^^^^^
 
-It specifies a column of the table or the value.
+Specifies a column of the table or the value.
 
 ``min``
 ^^^^^^^^^^^^^^^^^^^
 
-It specifies the minimal border value of the range.
+Specifies the minimal border value of the range.
 You can control the behavior that the value of ``max`` is included or excluded by ``max_border`` parameter.
 
 ``min_border``
 ^^^^^^^^^^^^^^^^^^^
 
-It specifies whether the specified range contains the value of ``min`` or not.
+Specifies whether the specified range contains the value of ``min`` or not.
 The value of ``min_border`` are either "include" or "exclude". If it is "include", ``min`` value is included. If it is "exclude", ``min`` value is not included.
 
 ``max``
 ^^^^^^^^^^^^^^^^^^^
 
-It specifies the maximum border value of the range.
+Specifies the maximum border value of the range.
 You can control the behavior that the value of ``max`` is included or excluded by ``max_border`` parameter.
 
 ``max_border``
 ^^^^^^^^^^^^^^^^^^^
 
-It specifies whether the specified range contains the value of ``max`` or not.
+Specifies whether the specified range contains the value of ``max`` or not.
 The value of ``max_border`` are either "include" or "exclude". If it is "include", ``max`` value is included. If it is "exclude", ``max`` value is not included.
 
 Return value

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

@@ -153,7 +153,7 @@ There are two required parameter, ``point1`` and ``point2``.
 ``point1``
 """"""""""
 
-It specifies the start point that
+Specifies the start point that
 you want to calculate the value of distance between two points.
 
 You can specify the value of GeoPoint type. [#]_
@@ -163,7 +163,7 @@ See :doc:`/reference/types` about GeoPoint.
 ``point2``
 """"""""""
 
-It specifies the end point that
+Specifies the end point that
 you want to calculate the value of distance between two points.
 
 You can specify the value of GeoPoint type or
@@ -179,7 +179,7 @@ There is a optional parameter, ``approximate_type``.
 ``approximate_type``
 """"""""""""""""""""
 
-It specifies how to approximate the geographical features for calculating
+Specifies how to approximate the geographical features for calculating
 the value of distance.
 
 You can specify the value of ``approximate_type`` by one of the followings.

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

@@ -88,35 +88,35 @@ There are three or over optional parameters, ``keywordN``, ``open_tagN`` and ``e
 ``column``
 ^^^^^^^^^^
 
-It specifies a column of the table.
+Specifies a column of the table.
 
 ``normalizer_name``
 ^^^^^^^^^^^^^^^^^^^
 
-It specifies a normalizer name.
+Specifies a normalizer name.
 
 ``use_html_escape``
 ^^^^^^^^^^^^^^^^^^^
 
-It specifies use or not use HTML escape. If it is ``true`` , use HTML escape.
+Specifies use or not use HTML escape. If it is ``true`` , use HTML escape.
 If it is ``false`` , not use HTML escape.
 
 ``keywordN``
 ^^^^^^^^^^^^
 
-It specifies a keyword for tagging.
+Specifies a keyword for tagging.
 You can specify multiple keywords for each three arguments.
 
 ``open_tagN``
 ^^^^^^^^^^^^^
 
-It specifies a open tag.
+Specifies a open tag.
 You can specify multiple open tags for each three arguments.
 
 ``close_tagN``
 ^^^^^^^^^^^^^^
 
-It specifies a close tag.
+Specifies a close tag.
 You can specify multiple close tags for each three arguments.
 
 Return value

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

@@ -85,7 +85,7 @@ There is only one parameter ``column`` .
 ``column``
 ^^^^^^^^^^
 
-It specifies a column of the table.
+Specifies a column of the table.
 
 Return value
 ------------

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

@@ -72,7 +72,7 @@ There is one required parameter, ``html``.
 ``html``
 ^^^^^^^^
 
-It specifies HTML text to be untagged.
+Specifies HTML text to be untagged.
 
 Return value
 ------------

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

@@ -11,20 +11,72 @@ in_values
 Summary
 -------
 
-TODO
+.. versionadded:: 4.0.7
+
+``in_values`` enables you to simplify the query which uses multiple ``OR`` or ``==``. It is recommended to use this function in point of view about performance improvements in such a case.
 
 Syntax
 ------
 
-TODO
+``in_values`` requires two or more arguments - ``target_value`` and multiple ``value``.
+
+::
+
+  in_values(target_value, value1, ..., valueN)
 
 Usage
 -----
 
+Here is a schema definition and sample data.
+
+Sample schema:
+
+.. groonga-command
+.. include:: ../../example/reference/functions/in_values/usage_setup_schema.log
+.. table_create Tags TABLE_PAT_KEY ShortText
+.. table_create Memos TABLE_HASH_KEY ShortText
+.. column_create Memos tag COLUMN_SCALAR ShortText
+.. column_create Tags memos_tag COLUMN_INDEX Memos tag
+
+Sample data:
+
+.. groonga-command
+.. include:: ../../example/reference/functions/in_values/usage_setup_data.log
+.. load --table Memos
+.. [
+.. {"_key": "Groonga is fast",          "tag": "groonga"},
+.. {"_key": "Mroonga is fast",          "tag": "mroonga"},
+.. {"_key": "Rroonga is fast",          "tag": "rroonga"},
+.. {"_key": "Droonga is fast",          "tag": "droonga"},
+.. {"_key": "Groonga is a HTTP server", "tag": "groonga"}
+.. ]
+
+Here is the simple usage of ``in_values`` function which selects the records - the value of ``tag`` column is "groonga" or "mroonga" or "droonga".
+
+.. groonga-command
+.. include:: ../../example/reference/functions/in_values/usage_only.log
+.. select Memos --output_columns _key,tag --filter 'in_values(tag, "groonga", "mroonga", "droonga")' --sortby _id
+
+When executing the above query, you can get the records except "rroonga" because "rroonga" is not specified as value in ``in_values``.
+
 Parameters
 ----------
 
+There are two or more required parameter, ``target_value`` and multiple ``value``.
+
+``target_value``
+^^^^^^^^^^^^^^^^
+
+Specifies a column of the table that is specified by ``table`` parameter in ``select``.
+
+``value``
+^^^^^^^^^
+
+Specifies a value of the column which you want to select.
+
 Return value
 ------------
 
+``in_values`` returns whether the value of column exists in specified the value of parameters or not.
 
+If record is matched to specified the value of parameters, it returns true. Otherwise, it returns false.

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

@@ -114,14 +114,14 @@ There are two required parameter, ``match_columns`` and ``query_string``.
 ``match_columns``
 """""""""""""""""
 
-It specifies the default target column for fulltext search by
+Specifies the default target column for fulltext search by
 ``query_string`` parameter value. It is the same role as
 :ref:`select-match-columns` parameter in ``select``.
 
 ``query_string``
 """"""""""""""""
 
-It specifies the search condition in
+Specifies the search condition in
 :doc:`/reference/grn_expr/query_syntax`. It is the same role as
 ``query`` parameter in ``select``.
 
@@ -136,7 +136,7 @@ There are some optional parameters.
 ``query_expander``
 """"""""""""""""""
 
-It specifies the plugin name for query expansion.
+Specifies the plugin name for query expansion.
 
 There is one plugin bundled in official release - :doc:`/reference/query_expanders/tsv`.
 
@@ -146,7 +146,7 @@ See :doc:`/reference/query_expanders/tsv` about details.
 ``substitution_table``
 """"""""""""""""""""""
 
-It specifies the substitution table and substitution column name
+Specifies the substitution table and substitution column name
 by following format such as ``${TABLE}.${COLUMN}`` for query expansion.
 
 See :ref:`query-expander` about details.

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

@@ -67,8 +67,8 @@ Sample data:
 .. {"_key": "rroonga's blog", "content": "content of rroonga's blog", comments: [3]},
 .. ]
 
-Here is the simple usage of ``sub_filter`` function which extracts the blog entry
- user 'A' commented out.
+Here is the simple usage of ``sub_filter`` function which extracts the
+blog entry commented by user 'A'.
 
 .. groonga-command
 .. include:: ../../example/reference/functions/sub_filter/usage_without_sub_filter.log
@@ -102,7 +102,7 @@ There are two required parameter, ``scope`` and ``filter_string``.
 ``scope``
 ^^^^^^^^^
 
-It specifies a column of the table that is specified by ``table``
+Specifies a column of the table that is specified by ``table``
 parameter in ``select``. The column has a limitation. The limitation
 is described later. ``filter_string`` is evaluated in the column
 context. It means that ``filter_string`` is evaluated like
@@ -119,7 +119,7 @@ See :ref:`select-table` about ``table`` parameter in ``select``.
 ``filter_string``
 ^^^^^^^^^^^^^^^^^
 
-It specifies a search condition in
+Specifies a search condition in
 :doc:`/reference/grn_expr/script_syntax`. It is evaluated in ``scope``
 context.
 

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

@@ -45,10 +45,10 @@ Here are a schema definition and sample data to show usage.
 ..  "content": "Welcome! This is my first post!",
 ..  "n_likes": 5},
 .. {"_key":    "Groonga",
-..  "content": "I started to use groonga. It's very fast!",
+..  "content": "I started to use Groonga. It's very fast!",
 ..  "n_likes": 10},
 .. {"_key":    "Mroonga",
-..  "content": "I also started to use mroonga. It's also very fast! Really fast!",
+..  "content": "I also started to use Mroonga. It's also very fast! Really fast!",
 ..  "n_likes": 15},
 .. {"_key":    "Good-bye Senna",
 ..  "content": "I migrated all Senna system!",
@@ -137,7 +137,7 @@ search conditions; ``search`` and ``keyword``. If you want to
 specifies a keyword that contains one or more spaces, you can use
 ``phrase search condition`` that is described below.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_full_text_search.log
@@ -170,7 +170,7 @@ adjacent. Thus, ``Put a search keyword in the form`` is matched but
 ``Search by the keyword`` and ``There is a keyword. Search by it!``
 aren't matched.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_phrase_search.log
@@ -212,7 +212,7 @@ the following features:
 See description of ``--match_columns`` option of
 :doc:`/reference/commands/select` about them.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_full_text_search_with_explicit_match_column.log
@@ -239,7 +239,7 @@ advanced match columns but ``phrase search condition (with explicit
 match column)`` isn't supported. See description of ``full text search
 condition (with explicit match column)`` about advanced match columns.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_phrase_search_with_explicit_match_column.log
@@ -273,7 +273,7 @@ time for large records.
 It doesn't require the default match columns such as ``full text
 search condition`` and ``phrase search condition``.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_prefix_search.log
@@ -318,7 +318,7 @@ large records.
 It doesn't require the default match columns such as ``full text
 search condition`` and ``phrase search condition``.
 
-Here is a simple exmaple. It uses fast suffix search for hiragana in
+Here is a simple example. It uses fast suffix search for hiragana in
 Japanese that is one of non-ASCII characters.
 
 .. groonga-command
@@ -350,7 +350,7 @@ It matches records that ``column`` value is equal to ``value``.
 It doesn't require the default match columns such as ``full text
 search condition`` and ``phrase search condition``.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_equal.log
@@ -369,7 +369,7 @@ It matches records that ``column`` value isn't equal to ``value``.
 It doesn't require the default match columns such as ``full text
 search condition`` and ``phrase search condition``.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_not_equal.log
@@ -393,7 +393,7 @@ compared as bit sequence.
 It doesn't require the default match columns such as ``full text
 search condition`` and ``phrase search condition``.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_less_than.log
@@ -417,7 +417,7 @@ compared as bit sequence.
 It doesn't require the default match columns such as ``full text
 search condition`` and ``phrase search condition``.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_greater_than.log
@@ -442,7 +442,7 @@ compared as bit sequence.
 It doesn't require the default match columns such as ``full text
 search condition`` and ``phrase search condition``.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_less_than_or_equal_to.log
@@ -467,7 +467,7 @@ compared as bit sequence.
 It doesn't require the default match columns such as ``full text
 search condition`` and ``phrase search condition``.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_greater_than_or_equal_to.log
@@ -476,6 +476,32 @@ Here is a simple exmaple.
 The expression matches records that ``n_likes`` column value is
 greater than or equal to ``10``.
 
+.. _query-regular-expression-condition:
+
+Regular expression condition
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+.. versionadded:: 5.0.1
+
+Its syntax is ``column:~pattern``.
+
+It matches records that ``column`` value is matched to
+``pattern``. ``pattern`` must be valid
+:doc:`/reference/regular_expression`.
+
+The following example uses ``.roonga`` as pattern. It matches
+``Groonga``, ``Mroonga`` and so on.
+
+.. groonga-command
+.. include:: ../../example/reference/grn_expr/query_syntax/simple_regular_expression.log
+.. select Entries --query content:~.roonga
+
+In most cases, regular expression is evaluated sequentially. So it may
+be slow against many records.
+
+In some cases, Groonga evaluates regular expression by index. It's
+very fast. See :doc:`/reference/regular_expression` for details.
+
 .. _combined-expression:
 
 Combined expression
@@ -493,7 +519,7 @@ assignment expressions.
 
 If at least one of ``a`` and ``b`` are matched, ``a OR b`` is matched.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_logical_or.log
@@ -516,7 +542,7 @@ If both ``a`` and ``b`` are matched, ``a + b`` is matched.
 You can specify ``+`` the first expression such as ``+a``. The ``+``
 is just ignored.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_logical_and.log
@@ -539,7 +565,7 @@ If ``a`` is matched and ``b`` is not matched, ``a - b`` is matched.
 You can not specify ``-`` the first expression such as ``-a``. It's
 syntax error.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_logical_not.log
@@ -559,7 +585,7 @@ processed as an expression. ``a b OR c`` means that ``a`` and ``b``
 are matched or ``c`` is matched. ``a (b OR c)`` means that ``a`` and
 one of ``b`` and ``c`` are matched.
 
-Here is a simple exmaple.
+Here is a simple example.
 
 .. groonga-command
 .. include:: ../../example/reference/grn_expr/query_syntax/simple_grouping.log