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

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

@@ -1,109 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-News in Senna period
-====================
-
-Senna -> groonga - 2009-01-14
------------------------------
-
-2006-04-05
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* SEN_INDEX_DELIMITED added
-* sen_sel_term_extract added
-
-2006-03-03
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* snippet function added
-
-2006-01-16
-----------
-
-Fixes
-^^^^^
-
-* io.c bug fix. index format changed
-
-2006-01-12
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* windows porting released
-
-2005-12-22
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* support unpatched version of mecab (0.81, 0.82pre, 0.90)
-  no longer depends on mecab mte patch.
-
-2005-10-27
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* mysql binding updated
-
-2005-09-17
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* mysql-5.0.12-beta binding from <tasuku at hottolink.co.jp>
-
-2005-09-08
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* utf-8 support enhanced. (SEN_INDEX_NORMALIZE become available)
-
-2005-08-16
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* Ruby binding has rewrited using SWIG and supports advanced API.
-* SJIS support enhanced.
-
-2005-07-05
-----------
-
-Changes
-^^^^^^^
-
-* the license has changed to LGPL from GPL.
-
-2005-06-23
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* advanced API functions implemented
-
-2005-04-12
-----------
-
-Improvements
-^^^^^^^^^^^^
-
-* applied ftb patch for mysql binding from <ko at yappo.ne.jp>
-  'IN BOOLEAN MODE' supported

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

@@ -1,35 +0,0 @@
-.. -*- rst -*-
-.. Groonga Project
-
-.. highlightlang:: none
-
-Reference manual
-================
-
-.. toctree::
-   :maxdepth: 2
-
-   reference/executables
-   reference/output
-   reference/command
-   reference/types
-   reference/tables
-   reference/column
-   reference/normalizers
-   reference/tokenizers
-   reference/token_filters
-   reference/query_expanders
-   reference/scorer
-   reference/grn_expr
-   reference/regular_expression
-   reference/function
-   reference/window_function
-   reference/operations
-   reference/configuration
-   reference/alias
-   reference/suggest
-   reference/indexing
-   reference/sharding
-   reference/log
-   reference/tuning
-   reference/api

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

@@ -1,164 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-.. groonga-command
-.. database: alias
-
-Alias
-=====
-
-.. versionadded:: 5.1.2
-
-You can refer a table and column by multiple names by using alias
-feature.
-
-Summary
--------
-
-The alias feature is useful for the following cases:
-
-  * You want to rename a table but you can't change some Groonga
-    clients that uses the current table name.
-
-  * You want to change column type without downtime.
-
-In the former case, some Groonga clients can use the current table
-name after you rename a table. Because the alias feature maps the
-current table name to the renamed new table name.
-
-In the latter case, all Groonga clients access the column by aliased
-name such as ``aliased_column``. ``aliased_column`` refers
-``current_column``. You create a new column ``new_column`` with new
-type and copy data from ``current_column`` by
-:doc:`/reference/commands/column_copy`. You change ``aliased_column``
-to refer ``new_column`` from ``current_column``. Now, all Groonga
-clients access ``new_column`` by ``aliased_column`` without stopping
-search requests.
-
-Usage
------
-
-You manage alias to real name mapping by a normal table and a normal
-column.
-
-You can use any table type except :ref:`table-no-key` for the
-table. :ref:`table-hash-key` is recommended because exact key match
-search is only used for the alias feature. :ref:`table-hash-key` is
-the fastest table type for exact key match search.
-
-The column must be :doc:`/reference/columns/scalar` and type is
-``ShortText``. You can also use ``Text`` and ``LongText`` types but
-they are meaningless. Because the max table/column name size is
-4KiB. ``ShortText`` can store 4KiB data.
-
-Here are example definitions of table and column for managing aliases:
-
-.. groonga-command
-.. include:: ../example/reference/alias/table_and_column.log
-.. table_create Aliases TABLE_HASH_KEY ShortText
-.. column_create Aliases real_name COLUMN_SCALAR ShortText
-
-You need to register the table and column by :doc:`configuration`.
-The alias feature uses ``alias.column`` configuration item. You can
-register the table and column by the following
-:doc:`/reference/commands/config_set`:
-
-.. groonga-command
-.. include:: ../example/reference/alias/register.log
-.. config_set alias.column Aliases.real_name
-
-Here are schema and data to show how to use alias:
-
-.. groonga-command
-.. include:: ../example/reference/alias/schema.log
-.. table_create Users TABLE_HASH_KEY ShortText
-.. column_create Users age COLUMN_SCALAR UInt8
-..
-.. load --table Users
-.. [
-.. {"_key": "alice", "age": 14},
-.. {"_key": "bob",   "age": 29}
-.. ]
-
-You can use ``Users.age`` in :doc:`/reference/commands/select`:
-
-.. groonga-command
-.. include:: ../example/reference/alias/select_age.log
-.. select Users --filter 'age < 20'
-
-You can't use ``Users.age`` when you rename ``Users.age`` to
-``Users.years`` by :doc:`/reference/commands/column_rename`:
-
-.. groonga-command
-.. include:: ../example/reference/alias/select_age_after_rename.log
-.. column_rename Users age years
-.. select Users --filter 'age < 20'
-
-But you can use ``Users.age`` by registering ``Users.age`` to
-``Users.years`` mapping to ``Aliases``.
-
-.. groonga-command
-.. include:: ../example/reference/alias/select_age_by_alias.log
-.. load --table Aliases
-.. [
-.. {"_key": "Users.age", "real_name": "Users.years"}
-.. ]
-..
-.. select Users --filter 'age < 20'
-
-Now, you can use ``Users.age`` as alias of ``Users.years``.
-
-How to resolve alias
---------------------
-
-This section describes how to resolve alias.
-
-Groonga uses the alias feature when nonexistent object name (table
-name, column name, command name, function name and so on) is
-referred. It means that you can't override existing object (table,
-column, command, function and so on) by the alias feature.
-
-For example, alias isn't resolved in the following example because
-``Users.years`` exists:
-
-.. groonga-command
-.. include:: ../example/reference/alias/existing_name.log
-.. load --table Aliases
-.. [
-.. {"_key": "Users.years", "real_name": "Users.years_old"}
-.. ]
-..
-.. select Users --filter 'years < 20'
-
-Alias is resolved recursively. If you rename ``Users.years`` to
-``Users.years_old`` and you refer ``Users.age``, Groonga replaces
-``Users.age`` with ``Users.years`` and then ``Users.years`` with
-``Users.years_old``. Because ``Aliases`` table has the following
-records:
-
-.. list-table::
-   :header-rows: 1
-
-   * - ``_key``
-     - ``real_name``
-   * - ``Users.age``
-     - ``Users.years``
-   * - ``Users.years``
-     - ``Users.years_old``
-
-Here is an example to ``Users.age`` is resolved recursively:
-
-.. groonga-command
-.. include:: ../example/reference/alias/existing_name.log
-.. column_rename Users years years_old
-.. select Users --filter 'age < 20'
-
-See also
---------
-
-  * :doc:`/reference/configuration`
-  * :doc:`/reference/commands/config_set`
-  * :doc:`/reference/commands/table_create`
-  * :doc:`/reference/commands/column_create`
-  * :doc:`/reference/commands/select`

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

@@ -1,18 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-API
-===
-
-Groonga can be used as a fulltext search library. This section
-describes APIs that are provided by groonga.
-
-.. toctree::
-   :maxdepth: 1
-   :glob:
-
-   api/overview
-   api/global_configurations
-   api/plugin
-   api/*

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/api/global_configurations.txt

@@ -1,49 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: none
-
-Global configurations
-=====================
-
-Summary
--------
-
-Groonga has the global configurations. You can access them by API.
-
-
-Reference
----------
-
-.. c:function:: int grn_get_lock_timeout(void)
-
-   Returns the lock timeout.
-
-   :c:type:`grn_ctx` acquires a lock for updating a shared value. If
-   other :c:type:`grn_ctx` is already updating the same value,
-   :c:type:`grn_ctx` that try to acquire a lock can't acquires a lock.
-   The :c:type:`grn_ctx` that can't acquires a lock waits 1
-   millisecond and try to acquire a lock again. The try is done
-   ``timeout`` times. If the :c:type:`grn_ctx` that can't acquires a
-   lock until ``timeout`` times, the tries are failed.
-
-   The default lock timeout is ``10000000``. It means that Groonga
-   doesn't report a lock failure until about 3 hours.  (1 * 10000000
-   [msec] = 10000 [sec] = 166.666... [min] = 2.777... [hour])
-
-   :return: The lock timeout.
-
-.. c:function:: grn_rc grn_set_lock_timeout(int timeout)
-
-   Sets the lock timeout.
-
-   See :c:func:`grn_get_lock_timeout` about lock timeout.
-
-   There are some special values for ``timeout``.
-
-     * ``0``: It means that Groonga doesn't retry acquiring a lock.
-       Groonga reports a failure after one lock acquirement failure.
-     * negative value: It means that Groonga retries acquiring a lock
-       until Groonga can acquire a lock.
-
-   :param timeuot: The new lock timeout.
-   :return: ``GRN_SUCCESS``. It doesn't fail.

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/api/grn_cache.txt

@@ -1,114 +0,0 @@
-.. -*- rst -*-
-
-.. highlightlang:: c
-
-``grn_cache``
-=============
-
-Summary
--------
-
-.. note::
-
-   This API is experimental.
-
-``grn_cache`` is a data store that keeps responses of
-:doc:`/reference/commands/select` command. It is not general use cache
-object. It is only for :doc:`/reference/commands/select` command.
-
-You can just change the current cache object by
-:c:func:`grn_cache_current_set()`. :doc:`/reference/commands/select`
-command response cache is done internally.
-
-:doc:`/reference/commands/select` command uses one global cache
-object. If you open multiple databases, the one cache is shared. It is
-an important problem.
-
-If you open multiple databases and use
-:doc:`/reference/commands/select` command, you need to use
-``grn_cache`` object. It is :doc:`/reference/executables/groonga-httpd`
-case. If you open only one database or don't use
-:doc:`/reference/commands/select` command, you don't need to use
-``grn_cache`` object. It is `rroonga
-<http://ranguba.org/#about-rroonga>`_ case.
-
-Example
--------
-
-Here is an example that change the current cache object.
-
-.. code-block:: c
-
-   grn_cache *cache;
-   grn_cache *cache_previous;
-   cache = grn_cache_open(ctx);
-   cache_previous = grn_cache_current_get(ctx);
-   grn_cache_current_set(ctx, cache);
-   /* grn_ctx_send(ctx, ...); */
-   grn_cache_current_set(ctx, cache_previous);
-
-
-Reference
----------
-
-.. c:type:: grn_cache
-
-   It is an opaque cache object. You can create a ``grn_cache`` by
-   :c:func:`grn_cache_open()` and free the created object by
-   :c:func:`grn_cache_close()`.
-
-.. c:function:: grn_cache *grn_cache_open(grn_ctx *ctx)
-
-   Creates a new cache object.
-
-   If memory allocation for the new cache object is failed, ``NULL``
-   is returned. Error information is stored into the ``ctx``.
-
-   :param ctx: The context.
-   :return: A newly allocated cache object on success, ``NULL``
-            otherwise. The returned cache object must be freed by
-            :c:func:`grn_cache_close()`.
-
-.. c:function:: grn_rc grn_cache_close(grn_ctx *ctx, grn_cache *cache)
-
-   Frees resourses of the ``cache``.
-
-   :param ctx: The context.
-   :param cache: The cache object to be freed.
-   :return: ``GRN_SUCCESS`` on success, not ``GRN_SUCCESS`` otherwise.
-
-.. c:function:: grn_rc grn_cache_current_set(grn_ctx *ctx, grn_cache *cache)
-
-   Sets the cache object that is used in
-   :doc:`/reference/commands/select` command.
-
-   :param ctx: The context.
-   :param cache: The cache object that is used in
-                 :doc:`/reference/commands/select` command.
-   :return: ``GRN_SUCCESS`` on success, not ``GRN_SUCCESS`` otherwise.
-
-.. c:function:: grn_cache *grn_cache_current_get(grn_ctx *ctx)
-
-   Gets the cache object that is used in
-   :doc:`/reference/commands/select` command.
-
-   :param ctx: The context.
-   :return: The cache object that is used in
-            :doc:`/reference/commands/select` command. It may be ``NULL``.
-
-.. c:function:: grn_rc grn_cache_set_max_n_entries(grn_ctx *ctx, grn_cache *cache, unsigned int n)
-
-   Sets the max number of entries of the cache object.
-
-   :param ctx: The context.
-   :param cache: The cache object to be changed.
-   :param n: The new max number of entries of the cache object.
-   :return: ``GRN_SUCCESS`` on success, not ``GRN_SUCCESS`` otherwise.
-
-.. c:function:: unsigned int grn_cache_get_max_n_entries(grn_ctx *ctx, grn_cache *cache)
-
-   Gets the max number of entries of the cache object.
-
-   :param ctx: The context.
-   :param cache: The target cache object.
-   :return: The max number of entries of the cache object.