rroonga 7.0.2-x86-mingw32 → 7.1.1-x86-mingw32

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

@@ -1,195 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: functions_in_records
-
-``in_records``
-==============
-
-Summary
--------
-
-.. versionadded:: 7.0.2
-
-You can use ``in_records`` for using an existing table as condition patterns. Each record in the existing table is treated as a condition pattern.
-
-You may be able to reduce multiple queries to only one query by ``in_records``.
-
-``in_records`` is similar to :doc:`sub_filter`. Here are differences of them:
-
-  * ``sub_filter`` requires a reference column to condition table but ``in_records`` doesn't require.
-
-  * ``sub_filter`` requires an index column for the reference column but ``in_records`` doesn't require.
-
-  * ``sub_filter`` can use all logical operations but ``in_records`` can use only AND logical operation in one pattern.
-
-  * ``sub_filter`` can use only the value of one reference column for condition but ``in_records`` can use one or more values for condition. You can use multiple columns, functions and so on for multiple values.
-
-  * ``sub_filter`` uses index search but ``in_records`` uses sequential search.
-
-.. _in-records-syntax:
-
-Syntax
-------
-
-``in_records`` has four or more parameters::
-
-  in_records(condition_table,
-             value1, mode1, condition_column_name1,
-             ...,
-             valueN, modeN, condition_column_nameN)
-
-.. _in-records-usage:
-
-Usage
------
-
-Here is a schema definition and sample data.
-
-Sample schema:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/in_records/usage_setup_schema.log
-.. table_create Tags TABLE_PAT_KEY ShortText
-..
-.. table_create Conditions TABLE_PAT_KEY ShortText
-.. column_create Conditions user_pattern COLUMN_SCALAR ShortText
-.. column_create Conditions tag COLUMN_SCALAR Tags
-.. column_create Conditions max_length COLUMN_SCALAR UInt32
-..
-.. table_create Memos TABLE_HASH_KEY ShortText
-.. column_create Memos user COLUMN_SCALAR ShortText
-.. column_create Memos tag COLUMN_SCALAR Tags
-
-Sample data:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/in_records/usage_setup_data.log
-.. load --table Memos
-.. [
-.. {"_key": "Groonga is fast",          "user": "alice", "tag": "groonga"},
-.. {"_key": "Mroonga is fast",          "user": "alice", "tag": "mroonga"},
-.. {"_key": "Groonga is very good!",    "user": "alice", "tag": "groonga"},
-.. {"_key": "Droonga is fast",          "user": "david", "tag": "droonga"},
-.. {"_key": "Groonga is a HTTP server", "user": "david", "tag": "groonga"}
-.. ]
-
-Sample conditions:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/in_records/usage_setup_conditions.log
-.. load --table Conditions
-.. [
-.. {"_key": "lic + groonga", "user_pattern": "lic", "tag": "groonga", max_length: 20},
-.. {"_key": "dav + droonga", "user_pattern": "dav", "tag": "droonga", max_length: 50}
-.. ]
-
-Here is a simple usage of ``in_records`` that searches by records in ``Conditions`` table. Each record is used as a condition:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/in_records/usage_search.log
-.. plugin_register functions/string
-.. select \
-..   --table Memos \
-..   --filter 'in_records(Conditions, \
-..                        user,                 "@", "user_pattern", \
-..                        tag,                 "==", "tag", \
-..                        string_length(_key), "<=", "max_length")' \
-..   --sort_by _id \
-..   --output_columns _key,user,tag
-
-The ``filter`` tries the following three conditions for each record:
-
-  * ``Memos.user`` matches (``@``) ``Conditions.user_pattern``.
-
-  * ``Memos.tag`` equals (``==``) ``Conditions.tag``.
-
-  * The number of characters in ``Memos._key`` is less than or equals to ``Conditions.max_length``.
-
-If at least one record in ``Conditions`` table returns true for the all three conditions, the record in ``Memos`` is matched.
-
-The first record in ``Conditions`` table use the following conditions:
-
-  * ``Memos.user`` has ``"lic"`` substring.
-
-  * ``Memos.tag`` is ``"groonga"``.
-
-  * The number of characters in ``Memos._key`` is less than or equals to ``20``.
-
-This condition matches the following records:
-
-  * ``{"_key": "Groonga is fast", "user": "alice", "tag": "groonga"}``
-
-The second record in ``Conditions`` table use the following conditions:
-
-  * ``Memos.user`` has ``"dav"`` substring.
-
-  * ``Memos.tag`` is ``"droonga"``.
-
-  * The number of characters in ``Memos._key`` is less than or equals to ``50``.
-
-This condition matches the following records:
-
-  * ``{"_key": "Droonga is fast", "user": "david", "tag": "droonga"}``
-
-The result has the all above records.
-
-.. _in-records-parameters:
-
-Parameters
-----------
-
-``in_records`` requires four or more parameters.
-
-.. _in-records-required-parameters:
-
-Required parameters
-^^^^^^^^^^^^^^^^^^^
-
-``condition_table`` and tuples of ``value``, ``mode_name`` and ``condition_column_name`` are required. You can specify multiple tuples of ``value``, ``mode_name`` and ``condition_column_name``
-
-.. _in-records-condition-table:
-
-``condition_table``
-"""""""""""""""""""
-
-Specifies a table that has conditions as its records.
-
-.. _in-records-value:
-
-``value``
-^^^^^^^^^
-
-Specifies a value to be compared.
-
-.. _in-records-mode-name:
-
-``mode_name``
-^^^^^^^^^^^^^
-
-Specifies a mode name that specifies how to compare :ref:`in-records-value` with a value of :ref:`in-records-condition-column-name`.
-
-See :ref:`query-default-mode` for available mode names. All mode names except ``NEAR``, ``SIMILAR`` and ``SUFFIX`` are supported.
-
-.. _in-records-condition-column-name:
-
-``condition_column_name``
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Specifies a column name of :ref:`in-records-condition-table` to be used as condition.
-
-.. _in-records-optional-parameters:
-
-Optional parameter
-^^^^^^^^^^^^^^^^^^
-
-There are no optional parameter.
-
-Return value
-------------
-
-``in_records`` returns whether the record is matched one of records of the specified condition table or not.
-
-If the record is matched, it returns ``true``. Otherwise, it returns ``false``.

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

@@ -1,82 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: functions_in_values
-
-``in_values``
-=============
-
-Summary
--------
-
-.. 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
-------
-
-``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/now.txt

@@ -1,36 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-now
-===
-
-名前
-----
-
-now - 現在時刻を返す
-
-書式
-----
-::
-
- now()
-
-説明
-----
-
-Groonga組込関数の一つであるnowについて説明します。組込関数は、script形式のgrn_expr中で呼び出すことができます。
-
-now() 関数は現在時刻に対応するTime型の値を返します。
-
-返値
-----
-
-現在時刻に対応するTime型のオブジェクトを返します。
-
-例
---
-::
-
- now()
- 1256791194.55541

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

@@ -1,20 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-``number_classify``
-===================
-
-Summary
--------
-
-number_classify
-
-Syntax
-------
-
-Usage
------
-
-Return value
-------------

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

@@ -1,158 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: functions_prefix_rk_search
-
-``prefix_rk_search``
-====================
-
-Summary
--------
-
-``prefix_rk_search`` selects records by
-:doc:`/reference/operations/prefix_rk_search`.
-
-You need to create :ref:`table-pat-key` table for prefix RK search.
-
-You can't use ``prefix_rk_search`` for sequential scan. It's a
-selector only procedure.
-
-Syntax
-------
-
-``prefix_rk_search`` requires two arguments. They are ``column`` and
-``query``::
-
-  prefix_rk_search(column, query)
-
-``column`` must be ``_key`` for now.
-
-``query`` must be string.
-
-Usage
------
-
-Here are a schema definition and sample data to show usage:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/prefix_rk_search/usage_setup.log
-.. table_create Readings TABLE_PAT_KEY ShortText --normalizer NormalizerAuto
-.. load --table Readings
-.. [
-.. {"_key": "ニホン"},
-.. {"_key": "ニッポン"},
-.. {"_key": "ローマジ"}
-.. ]
-
-Here is the simple usage of ``prefix_rk_search()`` function which
-selects ``ニホン`` and ``ニッポン`` by ``ni``:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/prefix_rk_search/usage_simple.log
-.. select Readings --filter 'prefix_rk_search(_key, "ni")'
-
-You can implement :doc:`/reference/suggest/completion` like feature by
-combining :doc:`sub_filter`.
-
-Create a table that has candidates of completion as records. Each
-records have zero or more readings. They are stored into ``Readings``
-table. Don't forget define an index column for ``Items.readings`` in
-``Readings`` table. The index column is needed for :doc:`sub_filter`:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/prefix_rk_search/usage_setup_completion.log
-.. table_create Items TABLE_HASH_KEY ShortText
-.. column_create Items readings COLUMN_VECTOR Readings
-..
-.. column_create Readings items_index COLUMN_INDEX Items readings
-..
-.. load --table Items
-.. [
-.. {"_key": "日本",     "readings": ["ニホン", "ニッポン"]},
-.. {"_key": "ローマ字", "readings": ["ローマジ"]},
-.. {"_key": "漢字",     "readings": ["カンジ"]}
-.. ]
-
-You can find ``日本`` record in ``Items`` table by ``niho``. Because
-prefix RK search with ``niho`` selects ``ニホン`` reading and ``ニホン``
-reading is one of readings of ``日本`` record:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/prefix_rk_search/usage_prefix_rk_only_completion.log
-.. select Items \
-..  --filter 'sub_filter(readings, "prefix_rk_search(_key, \\"niho\\")")'
-
-You need to combine :ref:`script-syntax-prefix-search-operator` to
-support no reading completion targets.
-
-Add one no reading completion target:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/prefix_rk_search/usage_add_no_reading_completion_target.log
-.. load --table Items
-.. [
-.. {"_key": "nihon", "readings": []}
-.. ]
-
-Combine :ref:`script-syntax-prefix-search-operator` to
-support no reading completion targets:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/prefix_rk_search/usage_prefix_search_combined_completion.log
-.. select Items \
-..  --filter 'sub_filter(readings, "prefix_rk_search(_key, \\"niho\\")") || _key @^ "niho"'
-
-Normally, you want to use case insensitive search for completion. Use
-``--normalizer NormalizerAuto`` and ``label`` column for the case:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/prefix_rk_search/usage_setup_loose_completion.log
-.. table_create LooseItems TABLE_HASH_KEY ShortText --normalizer NormalizerAuto
-.. column_create LooseItems label COLUMN_SCALAR ShortText
-.. column_create LooseItems readings COLUMN_VECTOR Readings
-..
-.. column_create Readings loose_items_index COLUMN_INDEX LooseItems readings
-..
-.. load --table LooseItems
-.. [
-.. {"_key": "日本",     "label": "日本",     "readings": ["ニホン", "ニッポン"]},
-.. {"_key": "ローマ字", "label": "ローマ字", "readings": ["ローマジ"]},
-.. {"_key": "漢字",     "label": "漢字",     "readings": ["カンジ"]},
-.. {"_key": "Nihon",    "label": "日本",     "readings": []}
-.. ]
-
-Use ``LooseItems.label`` for display:
-
-.. groonga-command
-.. include:: ../../example/reference/functions/prefix_rk_search/usage_loose_completion.log
-.. select LooseItems \
-..  --filter 'sub_filter(readings, "prefix_rk_search(_key, \\"nIhO\\")") || _key @^ "nIhO"' \
-..  --output_columns '_key,label'
-
-Parameters
-----------
-
-There are two required parameter, ``column`` and ``query``.
-
-``column``
-^^^^^^^^^^
-
-Always specifies ``_key`` for now.
-
-``query``
-^^^^^^^^^
-
-Specifies a query in romaji, katakana or hiragana as string.
-
-Return value
-------------
-
-``prefix_rk_search`` function returns matched records.
-
-See also
---------
-
-* :doc:`/reference/operations/prefix_rk_search`
-* :doc:`/reference/functions/sub_filter`