rroonga 2.0.7-x86-mingw32 → 2.0.8-x86-mingw32

data/vendor/local/share/doc/groonga/en/html/_sources/install/windows.txt

@@ -17,12 +17,12 @@ size data.
 Installer
 ---------
 
-For 32-bit environment, download `groonga-2.0.7-x86.exe
-<http://packages.groonga.org/windows/groonga/groonga-2.0.7-x86.exe>`_
+For 32-bit environment, download `groonga-2.0.9-x86.exe
+<http://packages.groonga.org/windows/groonga/groonga-2.0.9-x86.exe>`_
 and run it.
 
-For 64-bit environment, download `groonga-2.0.7-x64.exe
-<http://packages.groonga.org/windows/groonga/groonga-2.0.7-x64.exe>`_
+For 64-bit environment, download `groonga-2.0.9-x64.exe
+<http://packages.groonga.org/windows/groonga/groonga-2.0.9-x64.exe>`_
 and run it.
 
 Use command prompt for :doc:`/reference/executables/groonga` installed in start menu.
@@ -30,12 +30,12 @@ Use command prompt for :doc:`/reference/executables/groonga` installed in start
 zip
 ---
 
-For 32-bit environment, download `groonga-2.0.7-x86.zip
-<http://packages.groonga.org/windows/groonga/groonga-2.0.7-x86.zip>`_
+For 32-bit environment, download `groonga-2.0.9-x86.zip
+<http://packages.groonga.org/windows/groonga/groonga-2.0.9-x86.zip>`_
 and extract it.
 
-For 64-bit environment, download `groonga-2.0.7-x64.zip
-<http://packages.groonga.org/windows/groonga/groonga-2.0.7-x64.zip>`_
+For 64-bit environment, download `groonga-2.0.9-x64.zip
+<http://packages.groonga.org/windows/groonga/groonga-2.0.9-x64.zip>`_
 and extract it.
 
 :doc:`/reference/executables/groonga` is in ``bin`` folder.
@@ -50,28 +50,38 @@ Windows. Here are required tools:
     <http://www.microsoft.com/japan/msdn/vstudio/express/>`_
   * `CMake <http://www.cmake.org/>`_
 
-Download zipped source `groonga-2.0.7.zip
-<http://packages.groonga.org/source/groonga/groonga-2.0.7.zip>`_
+Download zipped source `groonga-2.0.9.zip
+<http://packages.groonga.org/source/groonga/groonga-2.0.9.zip>`_
 and extract it.
 
 Start ``Visual Studio Command Prompt (2010)`` installed by Microsoft
 Visual Studio 2010 Express and move to the groonga's source folder::
 
-  > cd c:\Users\%USERNAME%\Downloads\groonga-2.0.7
+  > cd c:\Users\%USERNAME%\Downloads\groonga-2.0.9
 
 Configure by ``cmake``. The following commnad line is for 64-bit
 version. To build 32-bit version, use ``-G "Visual Studio 10"``
 parameter instead::
 
-  groonga-2.0.7> cmake . -G "Visual Studio 10 Win64" -DCMAKE_INSTALL_PREFIX=C:\groonga
+  groonga-2.0.9> cmake . -G "Visual Studio 10 Win64" -DCMAKE_INSTALL_PREFIX=C:\groonga
 
-Build by Visual Studio::
+Build by Visual C++ 2010 Express::
 
-  groonga-2.0.7> devenv groonga.sln /Build Release
+  groonga-2.0.9> msbuild groonga.sln /p:Configuration=Release
 
-Install::
+Install by Visual C++ 2010 Express::
 
-  groonga-2.0.7> devenv groonga.sln /Build Release /Project Install
+  groonga-2.0.9> msbuild groonga.sln /p:Configuration=Release /t:Install
+
+If you installed Visual Studio 2010, use can use devenv instead.
+
+Build by Visual Studio 2010::
+
+  groonga-2.0.9> devenv groonga.sln /Build Release
+
+Install by Visual Studio 2010::
+
+  groonga-2.0.9> devenv groonga.sln /Build Release /Project Install
 
 After the above steps, :doc:`/reference/executables/groonga` is found in
 ``c:\groonga\bin\groonga.exe``.

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

@@ -7,13 +7,23 @@ Limitations
 
 Groonga has some limitations.
 
+Limitations of table
+--------------------
+
+A table has the following limitations.
+
+* The maximum one key size: 4096Bytes
+* The maximum total size of keys: 4GBytes
+
+Keep in mind that these limitations may vary depending on conditions.
+
 Limitations of indexing
 -----------------------
 
 A full-text index has the following limitations.
 
-* The maximum number of records: 268,435,455 (more than 26 million)
-* The maximum number of distinct terms: 268,435,455 (more than 26 million)
+* The maximum number of records: 268,435,455 (more than 268 million)
+* The maximum number of distinct terms: 268,435,455 (more than 268 million)
 * The maximum index size: 256GBytes
 
 Keep in mind that these limitations may vary depending on conditions.

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

@@ -5,7 +5,102 @@
 News
 ====
 
-.. _release-2-0-７:
+.. _release-2-0-9:
+
+Release 2.0.9 - 2012/11/29
+--------------------------
+
+Improvements
+^^^^^^^^^^^^
+
+* Supported to calculate the value of distance accross border
+  in ``geo_distance`` with ``rectangle`` as approximate type. [#1534]
+* [doc] Added the :doc:`/spec/gqtp` specification.
+* Improved to ignore non critical ``getaddrinfo()`` error which groonga command emits on startup.
+  This change does not affects nomal use of groonga because it just checked whether default hostname
+  is resolved in previous version.
+* [experimental] Added ``snippet_html()`` function which extract keyword and surrounding text.
+  See :doc:`/reference/functions/snippet_html` about details.
+* Supported to report error reason when error occured during reading table record.
+* Supported to search with keyword by nested index notation ( concatinate multiple 
+  indexed column name with dot character ) if there is a relationship between
+  multiple table with index.
+* Supported to log "[tokenizer][mecab]" tag when using ``TokenMecab`` tokenizer.
+* Supported to log "[tokenizer][kytea]" tag when using ``TokenKyTea`` tokenizer.
+* Improved to use separated array for command error location as output results.
+  This change is incompatibility change, but does not affects existing program.
+* Added documentation for :doc:`/reference/command/output_format`.
+* Added documentation for :doc:`/reference/command/return_code` of output results.
+* Supported range search by using index.
+
+Fixes
+^^^^^
+
+* Fixed to use network byte order for status code of :ref:`gqtp-header-spec` to follow
+  the normal network protocol convention.
+  This change affects that groonga <= 2.0.8 client which connects to groonga server 2.0.9
+  or later can not show status code properly when command failed.
+* Fixed a bug that UTF-8 normalization computes wrong offset which affects to return value
+  of ``snippet_html()``. This change not to insert tag of snippet into invalid location.
+  [#1531] [Reported by Tomoatsu Shimada]
+* [windows] Fixed over allocated memory access which cause segmentation fault
+  on startup by groonga command. [#1532] [Patch by Akio Tajima]
+* [windows] Fixed a bug that data stored in column couldn't be read when total amount of data
+  stored in column exceeds 128MB. [groonga-dev,01088] [Reported by ongaeshi]
+* Fixed a bug that searching with indexed column for ``Int*`` and ``UInt*`` 
+  except ``Int32/Uint32`` returns invalid results.
+* Fixed a bug that deleting record can be found.
+* Fixed a bug that latin1 and koi8r normalizations could not process all string data
+  if given string contains NULL character on the way.
+* Fixed to return the correct default value of type when no data stored in column is
+  referenced by ``select`` command.
+* Fixed to exclude the value of vector column metadata in :ref:`offline-index-construction`.
+  This change not to contain such a metadata as search results.
+
+Thanks
+^^^^^^
+
+* Tomoatsu Shimada
+* Akio Tajima
+* ongaeshi
+
+
+.. _release-2-0-8:
+
+Release 2.0.8 - 2012/10/29
+--------------------------
+
+Improvements
+^^^^^^^^^^^^
+
+* [rpm] Improved the description of server-http and httpd packages.
+  [Suggested by Daiki Ueno]
+* Supported custom query expansion by plugin.
+* [experimental] Added query expander ``QueryExpanderTSV`` plugin.
+* Supported Ubuntu 12.10 Quantal Quetzal
+* [experimental] Supported function call in ``output_columns``.
+* [doc][rpm] Add missing description about installing MeCab dictionary.
+  [Reported by serihiro]
+
+Fixes
+^^^^^
+
+* [rpm] Fixed to remove needless "Requires" from spec file.
+  [Reported by Daiki Ueno]
+* [rpm] Fixed inaccurate description about license of groonga-server-gqtp.
+* [admin] Fixed record edit button shows wrong record. [GitHub#34]
+  [Reported by firewood]
+* [deb] Fixed to remove needless dependency to pcre.
+* [deb] Fixed to bundle missing table plugin.
+
+Thanks
+^^^^^^
+
+* Daiki Ueno
+* firewood
+* serihiro
+
+.. _release-2-0-7:
 
 Release 2.0.7 - 2012/09/29
 --------------------------

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

@@ -10,13 +10,13 @@
 
    reference/executables
    reference/output
-   reference/command_version
-   reference/commands
+   reference/command
    reference/type
    reference/tokenizers
+   reference/query_expanders
    reference/pseudo_column
    reference/grn_expr
-   reference/functions
+   reference/function
    reference/indexing
    reference/log
    reference/api

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

@@ -0,0 +1,20 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+Command
+=======
+
+Command is the most important processing unit in query API. You
+request a processing to groonga by a command.
+
+This section describes about command and built-in commands.
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   command/command_version
+   command/output_format
+   command/return_code
+   commands/*

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

@@ -0,0 +1,228 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+Output format
+=============
+
+Summary
+-------
+
+Commands output their result as JSON, MessagePack, XML or TSV format.
+
+JSON and MessagePack output have the same structure. XML and TSV are
+their original structure.
+
+JSON or MessagePack is recommend format. XML is useful for visual
+result check. TSV is just for special use. Normally you doesn't need
+to use TSV.
+
+JSON and MessagePack
+--------------------
+
+This secsion describes the structure of command result on JSON and
+MessagePack format. JSON is used to show structure because MessagePack
+is binary format. Binary format isn't proper for documenataion.
+
+JSON and MessagePack uses the following structure::
+
+  [HEADER, BODY]
+
+For example::
+
+  [
+    [
+      0,
+      1337566253.89858,
+      0.000355720520019531
+    ],
+    [
+      [
+        [
+          1
+        ],
+        [
+          [
+            "_id",
+            "UInt32"
+          ],
+          [
+            "_key",
+            "ShortText"
+          ],
+          [
+            "content",
+            "Text"
+          ],
+          [
+            "n_likes",
+            "UInt32"
+          ]
+        ],
+        [
+          2,
+          "Groonga",
+          "I started to use groonga. It's very fast!",
+          10
+        ]
+      ]
+    ]
+  ]
+
+In the example, the following part is ``HEADER``::
+
+  [
+    0,
+    1337566253.89858,
+    0.000355720520019531
+  ]
+
+The following part is ``BODY``::
+
+  [
+    [
+      [
+        1
+      ],
+      [
+        [
+          "_id",
+          "UInt32"
+        ],
+        [
+          "_key",
+          "ShortText"
+        ],
+        [
+          "content",
+          "Text"
+        ],
+        [
+          "n_likes",
+          "UInt32"
+        ]
+      ],
+      [
+        2,
+        "Groonga",
+        "I started to use groonga. It's very fast!",
+        10
+      ]
+    ]
+  ]
+
+``HEADER``
+^^^^^^^^^^
+
+``HEADER`` is an array. The content of ``HEADER`` has some patterns.
+
+Success case
+++++++++++++
+
+``HEADER`` has three elements on success::
+
+  [0, UNIX_TIME_WHEN_COMMAND_IS_STARTED, ELAPSED_TIME]
+
+The first element is always ``0``.
+
+``UNIX_TIME_WHEN_COMMAND_IS_STARTED`` is the number of seconds
+since 1970-01-01 00:00:00 UTC when the command is started
+processing. ``ELAPSED_TIME`` is the elapsed time for processing the
+command in seconds. Both ``UNIX_TIME_WHEN_COMMAND_IS_STARTED`` and
+``ELAPSED_TIME`` are float value. The precision of them are
+nanosecond.
+
+Error case
+++++++++++
+
+``HEADER`` has four or five elements on error::
+
+  [
+    RETURN_CODE,
+    UNIX_TIME_WHEN_COMMAND_IS_STARTED,
+    ELAPSED_TIME,
+    ERROR_MESSAGE,
+    ERROR_LOCATION
+  ]
+
+``ERROR_LOCATION`` may not be included in ``HEADER`` but other four
+elements are always included.
+
+``RETURN_CODE`` is non 0 value. See :doc:`return_code` about available
+return codes.
+
+``UNIX_TIME_WHEN_COMMAND_IS_STARTED`` and ``ELAPSED_TIME`` are the
+same as success case.
+
+``ERROR_MESSAGE`` is an error message in string.
+
+``ERROR_LOCATION`` is optional. If error location is collected,
+``ERROR_LOCATION`` is included. ``ERROR_LOCATION`` is an
+array. ``ERROR_LOCATION`` has one ore two elements::
+
+  [
+    LOCATION_IN_GROONGA,
+    LOCATION_IN_INPUT
+  ]
+
+``LOCATION_IN_GROONGA`` is the source location that error is occurred
+in groonga. It is useful for groonga developers but not useful for
+users. ``LOCATION_IN_GROONGA`` is an array. ``LOCATION_IN_GROONGA`` has
+three elements::
+
+  [
+    FUNCTION_NAME,
+    SOURCE_FILE_NAME,
+    LINE_NUMBER
+  ]
+
+``FUNCTION_NAME`` is the name of function that error is occurred.
+
+``SOURCE_FILE_NAME`` is the name of groonga's source file that error is
+occurred.
+
+``LINE_NUMBER`` is the line number of ``SOURCE_FILE_NAME`` that error
+is occurred.
+
+``LOCATION_IN_INPUT`` is optional. ``LOCATION_IN_INPUT`` is included
+when the location that error is occurred in input file is
+collected. Input file can be specified by ``--file`` command line
+option for ``groonga`` command. ``LOCATION_IN_GROONGA`` is an
+array. ``LOCATION_IN_GROONGA`` has three elements::
+
+  [
+    INPUT_FILE_NAME,
+    LINE_NUMBER,
+    LINE_CONTENT
+  ]
+
+``INPUT_FILE_NAME`` is the input file name that error is occurred.
+
+``LINE_NUMBER`` is the line number of ``INPUT_FILE_NAME`` that error
+is occurred.
+
+``LINE_CONTENT`` is the content at ``LINE_NUMBER`` in
+``INPUT_FILE_NAME``.
+
+``BODY``
+^^^^^^^^
+
+``BODY`` content depends on the executed command. It may be omitted.
+
+``BODY`` may be an error message on error case.
+
+XML
+---
+
+TODO
+
+TSV
+---
+
+TODO
+
+See also
+--------
+
+* :doc:`return_code` describes about return code.
+