rroonga 4.0.5-x86-mingw32 → 4.0.6-x86-mingw32

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

@@ -7,6 +7,74 @@
 News
 ====
 
+.. _release-4-0-7:
+
+Release 4.0.7 - 2014/10/29
+--------------------------
+
+Improvements
+^^^^^^^^^^^^
+
+* [windows] Supported Groonga with mruby on Windows.
+* Added token filter plugin API.
+* Added :ref:`token-filter-stop-word` token filter plugin.
+  It treats records of ``is_stop_word`` column as actual stop words.
+* [doc] Added :doc:`/client` section which introduces link to client libraries.
+  [GitHub#210] [Patch by Naoya Murakami]
+* [doc] Reconstructed documentation. :doc:`/reference/suggest` and
+  :doc:`/reference/operations/geolocation_search` are grouped under :doc:`/reference`.
+  [GitHub#206] [Patch by Naoya Murakami]
+* [dump] Supports to dump TABLE_NO_KEY for token_flters.
+  [GitHub#215] [Patch by Naoya Murakami]
+* [deb] Added stop word token filter plugin.
+  [GitHub#216] [Patch by Hiroshi Hatake]
+* [deb] Clarified licenses about used/bundled files in debian/copyright.
+* Dropped LZO compression support.
+* Added LZ4 compression support. [GitHub#223] [Patch by Naoya Murakami]
+* Added :doc:`/reference/function/in_values`. We recommends to use it
+  instead of ``==`` and ``OR`` combinations ( ``((COLUMN == "a") OR
+  (COLUMN == "b") OR (COLUMN == "c"))`` ) because of better
+  performance.
+* [load] Supported to update existing record in ``TABLE_NO_KEY`` by
+  specifying a record by ``_id``.
+* Added :ref:`token-filter-stem` token filter plugin. It provides
+  stemming feature.  To use this token filter, you need to install
+  `libstemmer <http://http://snowball.tartarus.org/>`_ library.
+* [doc] Added :doc:`/reference/token_filters` documentation.
+  [GitHub#227] [Patch by Naoya Murakami]
+
+Fixes
+^^^^^
+
+* [doc] Fixed link of the Ranguba project. [GitHub#212] [Patch by Naoya Murakami]
+* [httpd] Updated bundled nginx version to 1.7.6.
+  [GitHub#208] [Patch by Hiroshi Hatake]
+* [power8] Fixed build failure. See
+  http://lists.askmonty.org/pipermail/commits/2014-October/006752.html
+  [Patch by Sergey Vojtovich]
+* Fixed a bug that URL encoding fails if ``char`` type is build as
+  ``unsigned char`` type. [GitHub#217]
+* Fixed a bug that a ``TABLE_DAT_KEY`` table returns empty results for
+  :doc:`/reference/commands/select`. [GitHub#220]
+* Fixed a memory leak about inspecting vector column. It occurs when
+  something error reports about vector column.
+* Fixed memory leaks in zlib/LZO compressed column [GitHub#221] [Patch
+  by Naoya Murakami]
+* Fixed a bug that the value of ``Int8`` column which is less than 100 may
+  return true in ``--filter``. By this issue, not intended records may
+  be included as search results.
+* Fixed to handle binary operation for vector column as an error.
+* Fixed a bug that ``!XXX`` may return inverted result on big endian
+  environment.
+* Fixed a memory leak on converting weight vector to text.
+
+Thanks
+^^^^^^
+
+* Naoya Murakami
+* Hiroshi Hatake
+* Sergey Vojtovich
+
 .. _release-4-0-6:
 
 Release 4.0.6 - 2014/09/29
@@ -23,8 +91,6 @@ Improvements
   [GitHub#196] [Patch by Masafumi Yokoyama]
 * [OS X] Added missing sphinx error message for Homebrew users.
   [GitHub#198] [Patch by cosmo0920]
-* Exported :c:func:`grn_expr_alloc_const` which allocates constant object.
-  It is exported for mruby.
 * [mruby] Query optimizer by mruby became a practical for some range select query.
   For example, mruby optimizer overhead is negligible enough for query such as
   "between(X, 0, 'exclude', 100, 'include')" - "X > 0 && X <= 100".
@@ -37,14 +103,11 @@ Improvements
   :doc:`/reference/commands/column_create`.  If source column doesn't
   exist, :doc:`/reference/commands/column_create` returns ``false`` and
   column isn't created.
-* [windows] Enabled mruby.
 * [debian] Dropped Debian jessie and sid support.
 
 Fixes
 ^^^^^
 
-* [windows] Disabled KyTea by default because of redistribution license issue.
-* [windows] Disabled libedit support by default.
 * Fixed a bug that similar search doesn't use IDF (Inverse Document Frequency)
   for choosing target tokens.
   In the previous versions, it used token ID instead of IDF.

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

@@ -194,7 +194,7 @@ Improvements
 * Accepted "#" and "-" as a valid name characters. #1043
 * Accepted all valid characters except "_" as the first character. #1043
 * Supported `--each` for `[...]` form :doc:`/reference/commands/load`. #1044
-* Added documentation for :doc:`/suggest`.
+* Added documentation for :doc:`/reference/suggest`.
 * Supported threshold as `--frequency_threshold` and
   `--conditional_probability_threshold` options in all
   :doc:`/reference/commands/suggest` types. #1042

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

@@ -142,7 +142,7 @@ Improvements
 * [gqtp] Supported error message. The body is changed to return
   raw text insted of double quoted text. This is incompatible changes.
 * [http] Supported "400 Bad request" for invalid argument error.
-* [doc] Added examples for :doc:`/suggest/completion`
+* [doc] Added examples for :doc:`/reference/suggest/completion`
 * Supported Ubuntu 13.10 (Saucy Salamander).
 
 Fixes

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

@@ -17,10 +17,13 @@ Reference manual
    reference/column
    reference/normalizers
    reference/tokenizers
+   reference/token_filters
    reference/query_expanders
    reference/pseudo_column
    reference/grn_expr
    reference/function
+   reference/operations
+   reference/suggest
    reference/indexing
    reference/log
    reference/tuning

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

@@ -117,3 +117,26 @@ Reference
    ctx、またはctxが使用するdbからidに対応するオブジェクトを検索して返す。idに一致するオブジェクトが存在しなければNULLを返す。
 
    :param id: 検索しようとするオブジェクトのidを指定します。
+
+.. c:function:: grn_content_type grn_ctx_get_output_type(grn_ctx *ctx)
+
+   Gets the current output type of the context.
+
+   Normally, this function isn't needed.
+
+   :param ctx: The context object.
+   :return: The output type of the context.
+
+.. c:function:: grn_rc grn_ctx_set_output_type(grn_ctx *ctx, grn_content_type type)
+
+   Sets the new output type to the context. It is used by executing a
+   command by :c:func:`grn_expr_exec()`. If you use
+   :c:func:`grn_ctx_send()`, the new output type isn't
+   used. :c:func:`grn_ctx_send()` sets output type from command line
+   internally.
+
+   Normally, this function isn't needed.
+
+   :param ctx: The context object.
+   :param type: The new output type.
+   :return: ``GRN_SUCCESS`` on success, not ``GRN_SUCCESS`` on error.

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

@@ -1,6 +1,6 @@
 .. -*- rst -*-
 
-.. highlightlang:: none
+.. highlightlang:: c
 
 grn_expr
 ========
@@ -48,6 +48,51 @@ Reference
 
 .. c:function:: GRN_API grn_rc grn_expr_append_op(grn_ctx *ctx, grn_obj *expr, grn_operator op, int nargs)
 
+.. c:function:: grn_rc grn_expr_get_keywords(grn_ctx *ctx, grn_obj *expr, grn_obj *keywords)
+
+   Extracts keywords from ``expr`` and stores to
+   ``keywords``. Keywords in ``keywords`` are owned by ``expr``. Don't
+   unlink them. Each keyword is ``GRN_BULK`` and its domain is
+   ``GRN_DB_TEXT``.
+
+   ``keywords`` must be ``GRN_PVECTOR``.
+
+   Here is an example code::
+
+      grn_obj keywords;
+      GRN_PTR_INIT(&keywords, GRN_OBJ_VECTOR, GRN_ID_NIL);
+      grn_expr_get_keywords(ctx, expr, &keywords);
+      {
+        int i, n_keywords;
+        n_keywords = GRN_BULK_VSIZE(&keywords) / sizeof(grn_obj *);
+        for (i = 0; i < n_keywords; i++) {
+          grn_obj *keyword = GRN_PTR_VALUE_AT(&keywords, i);
+          const char *keyword_content;
+          int keyword_size;
+          keyword_content = GRN_TEXT_VALUE(keyword);
+          keyword_size = GRN_TEXT_LEN(keyword);
+          /*
+            Use keyword_content and keyword_size.
+            You don't need to unlink keyword.
+            keyword is owned by expr.
+          */
+        }
+      }
+      GRN_OBJ_FIN(ctx, &keywords);
+
+
+   :param ctx: The context that creates the ``expr``.
+   :param expr: The expression to be extracted.
+   :param keywords: The container to store extracted keywords.
+                    It must be ``GRN_PVECTOR``.
+
+                    Each extracted keyword is ``GRN_BULK`` and its
+                    domain is ``GRN_DB_TEXT``.
+
+                    Extracted keywords are owned by ``expr``. Don't
+                    unlink them.
+   :return: ``GRN_SUCCESS`` on success, not ``GRN_SUCCESS`` on error.
+
 .. c:function:: grn_rc grn_expr_syntax_escape(grn_ctx *ctx, const char *string, int string_size, const char *target_characters, char escape_character, grn_obj *escaped_string)
 
    Escapes ``target_characters`` in ``string`` by ``escape_character``.

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

@@ -22,7 +22,7 @@ suggest - returns completion, correction and/or suggestion for a query.
 The suggest command returns completion, correction and/or
 suggestion for a specified query.
 
-See :doc:`/suggest/introduction` about completion,
+See :doc:`/reference/suggest/introduction` about completion,
 correction and suggestion.
 
 Syntax
@@ -257,5 +257,5 @@ Here is a returned JSON format::
 See also
 --------
 
-* :doc:`/suggest`
+* :doc:`/reference/suggest`
 * :doc:`/reference/executables/groonga-suggest-create-dataset`

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

@@ -26,6 +26,7 @@ Syntax
                [value_type=null]
                [default_tokenizer=null]
                [normalizer=null]
+               [token_filters=null]
 
 Usage
 -----
@@ -267,6 +268,20 @@ See :doc:`/reference/normalizers` for all normalizsers.
 
 The default value is none.
 
+.. _table-create-token-filters:
+
+``token_filters``
+^^^^^^^^^^^^^^^^^^
+
+It specifies token filters that is used to some processes tokenized token.
+
+You cannot use ``token_filters`` with ``TABLE_NO_KEY`` because
+``TABLE_NO_KEY`` doesn't support key.
+
+See :doc:`/reference/token_filters` for all token filters.
+
+The default value is none.
+
 Return value
 ------------
 

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

@@ -26,6 +26,7 @@ optional::
            [normalizer=null]
            [flags=NONE]
            [mode=ADD]
+           [token_filters=NONE]
 
 Usage
 -----
@@ -51,6 +52,8 @@ Required parameters
 
 There are required parameters, ``tokenizer`` and ``string``.
 
+.. _tokenize-tokenizer:
+
 ``tokenizer``
 """""""""""""
 
@@ -70,6 +73,8 @@ tokenizer plugin by :doc:`register` command. For example, you can use
 `KyTea <http://www.phontron.com/kytea/>`_ based tokenizer by
 registering ``tokenizers/kytea``.
 
+.. _tokenize-string:
+
 ``string``
 """"""""""
 
@@ -89,6 +94,8 @@ Optional parameters
 
 There are optional parameters.
 
+.. _tokenize-normalizer:
+
 ``normalizer``
 """"""""""""""
 
@@ -128,6 +135,8 @@ If you want to tokenize by two characters with noramlizer, use
 All alphabets are tokenized by two characters. And they are normalized
 to lower case characters. For example, ``fu`` is a token.
 
+.. _tokenize-flags:
+
 ``flags``
 """""""""
 
@@ -164,6 +173,8 @@ string. So the character is good character for this puropose. If
 treated as already tokenized string. Tokenizer just tokenizes by
 tokenized delimiter.
 
+.. _tokenize-mode:
+
 ``mode``
 """"""""
 
@@ -190,6 +201,18 @@ Here is an example to the ``GET`` mode.
 
 The last alphabet is tokenized by two characters.
 
+.. _tokenize-token-filters:
+
+``token_filters``
+"""""""""""""""""
+
+It specifies the token filter names. ``tokenize`` command uses the
+tokenizer that is named ``token_filters``.
+
+See :doc:`/reference/token_filters` about token filters.
+
+.. _tokenize-return-value:
+
 Return value
 ------------
 

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/executables/groonga-suggest-create-dataset.txt

@@ -20,9 +20,9 @@ SYNOPSTIS
 DESCTIPION
 ----------
 
-groonga-suggest-create-dataset creates a dataset for :doc:`/suggest`. A database has many datasets. This command just defines schema for a suggestion dataset.
+groonga-suggest-create-dataset creates a dataset for :doc:`/reference/suggest`. A database has many datasets. This command just defines schema for a suggestion dataset.
 
-This command generates some tables and columns for :doc:`/suggest`.
+This command generates some tables and columns for :doc:`/reference/suggest`.
 
 Here is the list of such tables. If you specify 'query' as dataset name, following '_DATASET' suffix are replaced. Thus, 'item_query', 'pair_query', 'sequence_query', 'event_query' tables are generated.
 
@@ -58,6 +58,6 @@ TODO
 SEE ALSO
 --------
 
-:doc:`/suggest`
+:doc:`/reference/suggest`
 :doc:`groonga-suggest-httpd`
 :doc:`groonga-suggest-learner`

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

@@ -42,7 +42,7 @@ You can use groonga as a library and create a grn_expr by calling
 grn_expr related APIs. You can use full features with calling APIs
 like :doc:`/reference/grn_expr/script_syntax`. Calling APIs is useful
 creating a custom syntax to create grn_expr. They are used in `rroonga
-<http://groonga.rubyforge.org/#about-rroonga>`_ that is Ruby bindings
+<http://ranguba.org/#about-rroonga>`_ that is Ruby bindings
 of Groonga. Rroonga can create a grn_expr by Ruby's syntax instead of
 parsing string.
 

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

@@ -0,0 +1,14 @@
+.. -*- rst -*-
+.. Groonga Project
+
+.. highlightlang:: none
+
+Operations
+==========
+
+Groonga has the search feature of multiple. This section describes how to search operations.
+
+.. toctree::
+   :maxdepth: 2
+
+   operations/geolocation_search

data/vendor/local/share/doc/groonga/{en/html/_sources → ja/html/_sources/reference}/suggest.txt

@@ -12,7 +12,6 @@ Groonga has the suggest feature. This section describes how to use it and how it
    :maxdepth: 2
 
    suggest/introduction
-   suggest/tutorial
    suggest/completion
    suggest/correction
    suggest/suggestion

data/vendor/local/share/doc/groonga/{en/html/_sources → ja/html/_sources/reference}/suggest/completion.txt

@@ -166,7 +166,7 @@ For example, here is an command to get completion results by
 "en":
 
 .. groonga-command
-.. include:: ../example/completion-1.log
+.. include:: ../../example/reference/suggest/complete/select.log
 .. suggest --table item_query --column kana --types complete --frequency_threshold 1 --query en
 
 How it learns
@@ -209,7 +209,7 @@ Groonga requires registered word and its reading for RK search, so load such dat
 Here is the example to register "日本" which means Japanese in english.
 
 .. groonga-command
-.. include:: ../example/suggest/complete/registered-word-japan.log
+.. include:: ../../example/reference/suggest/complete/registered-word-japan.log
 .. load --table event_query --each 'suggest_preparer(_id, type, item, sequence, time, pair_query)'
 .. [
 .. {"sequence": "1", "time": 1312950805.86058, "item": "日本", "type": "submit"}
@@ -219,7 +219,7 @@ Here is the example to register "日本" which means Japanese in english.
 Here is the example to update RK data to complete "日本".
 
 .. groonga-command
-.. include:: ../example/suggest/complete/update-rk-data.log
+.. include:: ../../example/reference/suggest/complete/update-rk-data.log
 .. load --table item_query
 .. [
 .. {"_key":"日本", "kana":["ニホン", "ニッポン"]}
@@ -228,7 +228,7 @@ Here is the example to update RK data to complete "日本".
 Then you can complete registered word "日本" by RK input - "nihon".
 
 .. groonga-command
-.. include:: ../example/suggest/complete/rk-search-nihon.log
+.. include:: ../../example/reference/suggest/complete/rk-search-nihon.log
 .. suggest --table item_query --column kana --types complete --frequency_threshold 1 --query nihon
 
 Without loading above RK data, you can't complete registered word "日本"
@@ -241,7 +241,7 @@ This is the reason that you can also complete the registered word "日本"
 by query - "nippon".
 
 .. groonga-command
-.. include:: ../example/suggest/complete/rk-search-nippon.log
+.. include:: ../../example/reference/suggest/complete/rk-search-nippon.log
 .. suggest --table item_query --column kana --types complete --frequency_threshold 1 --query nippon
 
 This feature is very convenient because you can search registered word
@@ -254,7 +254,7 @@ table.
 Here is the example to customize priority for RK search.
 
 .. groonga-command
-.. include:: ../example/suggest/complete/registered-word-japanese.log
+.. include:: ../../example/reference/suggest/complete/registered-word-japanese.log
 .. load --table event_query --each 'suggest_preparer(_id, type, item, sequence, time, pair_query)'
 .. [
 .. {"sequence": "1", "time": 1312950805.86059, "item": "日本語", "type": "submit"}