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

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/plugin_register.txt

@@ -1,64 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: commands_plugin_register
-
-``plugin_register``
-===================
-
-.. versionadded:: 5.0.1
-
-Summary
--------
-
-``plugin_register`` command registers a plugin. You need to register a plugin
-before you use a plugin.
-
-You need just one ``plugin_register`` command for a plugin in the same
-database because registered plugin information is written into the
-database.  When you restart your ``groonga`` process, ``groonga``
-process loads all registered plugins without ``plugin_register`` command.
-
-You can unregister a registered plugin by :doc:`plugin_unregister`.
-
-Syntax
-------
-
-This command takes only one required parameter::
-
-  plugin_register name
-
-Usage
------
-
-Here is a sample that registers ``QueryExpanderTSV`` query expander
-that is included in
-``${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so``.
-
-.. groonga-command
-.. include:: ../../example/reference/commands/plugin_register/query_expanders_tsv.log
-.. plugin_register query_expanders/tsv
-
-You can omit ``${PREFIX}/lib/groonga/plugins/`` and suffix (``.so``).
-They are completed automatically.
-
-You can specify absolute path such as ``plugin_register
-/usr/lib/groonga/plugins/query_expanders/tsv.so``.
-
-Return value
-------------
-
-``plugin_register`` returns ``true`` as body on success such as::
-
-  [HEADER, true]
-
-If ``plugin_register`` fails, error details are in ``HEADER``.
-
-See :doc:`/reference/command/output_format` for ``HEADER``.
-
-See also
---------
-
-* :doc:`plugin_unregister`

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/plugin_unregister.txt

@@ -1,63 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: commands_plugin_unregister
-
-``plugin_unregister``
-=====================
-
-.. note::
-
-   This command is an experimental feature.
-
-.. versionadded:: 5.0.1
-
-Summary
--------
-
-``plugin_unregister`` command unregisters a plugin.
-
-Syntax
-------
-
-This command takes only one required parameter::
-
-  plugin_unregister name
-
-Usage
------
-
-Here is a sample that unregisters ``QueryExpanderTSV`` query expander
-that is included in
-``${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so``.
-
-.. groonga-command
-.. plugin_register query_expanders/tsv
-
-.. groonga-command
-.. include:: ../../example/reference/commands/plugin_unregister/query_expanders_tsv.log
-.. plugin_unregister query_expanders/tsv
-
-You can omit ``${PREFIX}/lib/groonga/plugins/`` and suffix (``.so``).
-They are completed automatically.
-
-You can specify absolute path such as ``plugin_unregister
-/usr/lib/groonga/plugins/query_expanders/tsv.so``.
-
-Return value
-------------
-
-``plugin_unregister`` returns ``true`` as body on success such as::
-
-  [HEADER, true]
-
-If ``plugin_unregister`` fails, error details are in ``HEADER``.
-
-See :doc:`/reference/command/output_format` for ``HEADER``.
-
-See also
---------
-
-* :doc:`plugin_register`

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/query_expand.txt

@@ -1,38 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: query_expand
-
-``query_expand``
-================
-
-Summary
--------
-
-.. versionadded:: 6.0.5
-
-Syntax
-------
-
-Usage
------
-
-Parameters
-----------
-
-This section describes all parameters.
-
-Required parameters
-^^^^^^^^^^^^^^^^^^^
-
-Optional parameters
-^^^^^^^^^^^^^^^^^^^
-
-Return value
-------------
-
-See also
---------
-

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/quit.txt

@@ -1,38 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-``quit``
-========
-
-Summary
--------
-
-quit - セッション終了
-
-Groonga組込コマンドの一つであるquitについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
-
-quitは、groongaプロセスとのセッションを終了します。クライアントプロセスならばgroongaプロセスとの接続を切ります。
-
-Syntax
-------
-::
-
- quit
-
-Usage
------
-::
-
- quit
-
-Parameters
-----------
-
-ありません。
-
-Return value
-------------
-
-ありません。
-

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/range_filter.txt

@@ -1,28 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: range_filter
-
-``range_filter``
-===================
-
-Summary
--------
-
-TODO: write me
-
-Syntax
-------
-
-Usage
------
-
-Return value
-------------
-
-See also
---------
-
-* :doc:`/reference/commands/select`

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/register.txt

@@ -1,69 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: commands_register
-
-``register``
-============
-
-.. deprecated:: 5.0.1
-   Use :doc:`plugin_register` instead.
-
-Summary
--------
-
-``register`` command registers a plugin. You need to register a plugin
-before you use a plugin.
-
-You need just one ``register`` command for a plugin in the same
-database because registered plugin information is written into the
-database.  When you restart your ``groonga`` process, ``groonga``
-process loads all registered plugins without ``register`` command.
-
-.. note::
-
-   Registered plugins can be removed since Groonga 5.0.1. Use
-   :doc:`plugin_unregister` in such a case.
-
-Syntax
-------
-
-This command takes only one required parameter::
-
-  register path
-
-Usage
------
-
-Here is a sample that registers ``QueryExpanderTSV`` query expander
-that is included in
-``${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so``.
-
-.. groonga-command
-.. include:: ../../example/reference/commands/register/query_expanders_tsv.log
-.. register query_expanders/tsv
-
-You can omit ``${PREFIX}/lib/groonga/plugins/`` and suffix (``.so``).
-They are completed automatically.
-
-You can specify absolute path such as ``register
-/usr/lib/groonga/plugins/query_expanders/tsv.so``.
-
-Return value
-------------
-
-``register`` returns ``true`` as body on success such as::
-
-  [HEADER, true]
-
-If ``register`` fails, error details are in ``HEADER``.
-
-See :doc:`/reference/command/output_format` for ``HEADER``.
-
-See also
---------
-
-* :doc:`plugin_register`
-* :doc:`plugin_unregister`

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/reindex.txt

@@ -1,142 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: reindex
-
-``reindex``
-===========
-
-Summary
--------
-
-.. versionadded:: 5.1.0
-
-``reindex`` command recreates one or more index columns.
-
-If you specify a database as target object, all index columns are
-recreated.
-
-If you specify a table as target object, all index columns in the
-table are recreated.
-
-If you specify a data column as target object, all index columns for
-the data column are recreated.
-
-If you specify an index column as target object, the index column is
-recreated.
-
-This command is useful when your index column is broken. The target
-object is one of database, table and column.
-
-.. note::
-
-   You can't use target index columns while ``reindex`` command is
-   running. If you use the same database from multiple processes, all
-   processes except running ``reindex`` should reopen the
-   database. You can use :doc:`database_unmap` for reopening database.
-
-Syntax
-------
-
-This command takes only one optional parameter::
-
-  reindex [target_name=null]
-
-If ``target_name`` parameters is omitted, database is used for the
-target object. It means that all index columns in the database are
-recreated.
-
-Usage
------
-
-Here is an example to recreate all index columns in the database:
-
-.. groonga-command
-.. include:: ../../example/reference/commands/reindex/database.log
-.. reindex
-
-Here is an example to recreate all index columns
-(``Lexicon.entry_key`` and ``Lexicon.entry_body``) in ``Lexicon``
-table:
-
-.. groonga-command
-.. include:: ../../example/reference/commands/reindex/table.log
-.. table_create Entry TABLE_HASH_KEY ShortText
-.. column_create Entry body COLUMN_SCALAR Text
-..
-.. table_create Lexicon TABLE_PAT_KEY ShortText \
-..   --default_tokenizer TokenBigram \
-..   --normalizer NormalizerAuto
-.. column_create Lexicon entry_key COLUMN_INDEX|WITH_POSITION \
-..   Entry _key
-.. column_create Lexicon entry_body COLUMN_INDEX|WITH_POSITION \
-..   Entry body
-..
-.. reindex Lexicon
-
-Here is an example to recreate all index columns
-(``BigramLexicon.site_title`` and ``RegexpLexicon.site_title``) of
-``Site.title`` data column:
-
-.. groonga-command
-.. include:: ../../example/reference/commands/reindex/data_column.log
-.. table_create Site TABLE_HASH_KEY ShortText
-.. column_create Site title COLUMN_SCALAR ShortText
-..
-.. table_create BigramLexicon TABLE_PAT_KEY ShortText \
-..   --default_tokenizer TokenBigram \
-..   --normalizer NormalizerAuto
-.. column_create BigramLexicon site_title COLUMN_INDEX|WITH_POSITION \
-..   Site title
-..
-.. table_create RegexpLexicon TABLE_PAT_KEY ShortText \
-..   --default_tokenizer TokenRegexp \
-..   --normalizer NormalizerAuto
-.. column_create RegexpLexicon site_title COLUMN_INDEX|WITH_POSITION \
-..   Site title
-..
-.. reindex Site.title
-
-Here is an example to recreate an index column (``Timestamp.index``):
-
-.. groonga-command
-.. include:: ../../example/reference/commands/reindex/index_column.log
-.. table_create Logs TABLE_NO_KEY
-.. column_create Logs timestamp COLUMN_SCALAR Time
-..
-.. table_create Timestamp TABLE_PAT_KEY Time
-.. column_create Timestamp logs_timestamp COLUMN_INDEX  Logs timestamp
-..
-.. reindex Timestamp.logs_timestamp
-
-Parameters
-----------
-
-This section describes all parameters.
-
-``target_name``
-"""""""""""""""
-
-Specifies the name of table or column.
-
-If you don't specify it, database is used for the target object.
-
-The default is none. It means that the target object is database.
-
-Return value
-------------
-
-``reindex`` command returns whether recreation is succeeded or not::
-
-  [HEADER, SUCCEEDED_OR_NOT]
-
-``HEADER``
-
-  See :doc:`/reference/command/output_format` about ``HEADER``.
-
-``SUCCEEDED_OR_NOT``
-
-  If command succeeded, it returns true, otherwise it returns false on
-  error.