RubyGems - rroonga - Versions diffs - 7.1.1-x86-mingw32 → 9.0.2-x86-mingw32 - Mend

rroonga 7.1.1-x86-mingw32 → 9.0.2-x86-mingw32

Files changed (980) hide show

data/vendor/local/share/doc/groonga/en/html/troubleshooting/how_to_analyze_error_message.html CHANGED Viewed

@@ -1,34 +1,26 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
-    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-    <title>10.2. How to analyze error messages &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>10.2. How to analyze error messages &#8212; Groonga v9.0.2 documentation</title>
     <link rel="stylesheet" href="../_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
-    <script type="text/javascript">
-      var DOCUMENTATION_OPTIONS = {
-        URL_ROOT:    '../',
-        VERSION:     '7.1.0-73-g6d02cfa',
-        COLLAPSE_INDEX: false,
-        FILE_SUFFIX: '.html',
-        HAS_SOURCE:  false,
-        SOURCELINK_SUFFIX: '.txt'
-      };
-    </script>
+    <script type="text/javascript" id="documentation_options" data-url_root="../" src="../_static/documentation_options.js"></script>
     <script type="text/javascript" src="../_static/jquery.js"></script>
     <script type="text/javascript" src="../_static/underscore.js"></script>
     <script type="text/javascript" src="../_static/doctools.js"></script>
+    <script type="text/javascript" src="../_static/language_data.js"></script>
     <link rel="shortcut icon" href="../_static/favicon.ico"/>
     <link rel="index" title="Index" href="../genindex.html" />
     <link rel="search" title="Search" href="../search.html" />
     <link rel="next" title="10.3. How to avoid mmap Cannot allocate memory error" href="mmap_cannot_allocate_memory.html" />
     <link rel="prev" title="10.1. 同じ検索キーワードなのに全文検索結果が異なる" href="different_results_with_the_same_keyword.html" />
-  </head>
-  <body>
+  </head><body>
 <div class="header">
   <h1 class="title">
     <a id="top-link" href="../index.html">
@@ -58,7 +50,7 @@
         <li class="right" >
           <a href="different_results_with_the_same_keyword.html" title="10.1. 同じ検索キーワードなのに全文検索結果が異なる"
              accesskey="P">previous</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfa documentation</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v9.0.2 documentation</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../troubleshooting.html" accesskey="U">10. Troubleshooting</a> &#187;</li>
       </ul>
     </div>
@@ -77,22 +69,22 @@
 <div class="section" id="example">
 <h3>10.2.1.1. Example<a class="headerlink" href="#example" title="Permalink to this headline">¶</a></h3>
 <p>The following is an example of an error message repoted by Groonga, where xxxxx is an arbitrary number:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>socket error[xxxxx]: no buffer: accept
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>socket error[xxxxx]: no buffer: accept
 </pre></div>
 </div>
 </div>
 <div class="section" id="how-to-analyze">
 <h3>10.2.1.2. How to analyze<a class="headerlink" href="#how-to-analyze" title="Permalink to this headline">¶</a></h3>
-<p>First, grep Groonga source files for &quot;SOERR&quot; that is the name of a macro for socket errors.</p>
-<p>Then, extract SOERRs whose argument contains &quot;accept&quot; from the grep output and you will find the following SOERRs:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>lib/com.c:      SOERR(&quot;listen - start accept&quot;);
+<p>First, grep Groonga source files for “SOERR” that is the name of a macro for socket errors.</p>
+<p>Then, extract SOERRs whose argument contains “accept” from the grep output and you will find the following SOERRs:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>lib/com.c:      SOERR(&quot;listen - start accept&quot;);
 lib/com.c:      SOERR(&quot;listen - disable accept&quot;);
 lib/com.c:        SOERR(&quot;accept&quot;);
 </pre></div>
 </div>
-<p>It is clear that the above error message is associated with the last line because the error message contains only &quot;accept&quot;.</p>
+<p>It is clear that the above error message is associated with the last line because the error message contains only “accept”.</p>
 <p>The source code around the line is as follows:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>grn_sock fd = accept(com-&gt;fd, NULL, NULL);
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>grn_sock fd = accept(com-&gt;fd, NULL, NULL);
 if (fd == -1) {
   if (errno == EMFILE) {
     grn_com_event_stop_accept(ctx, ev);
@@ -104,18 +96,18 @@ if (fd == -1) {
 </pre></div>
 </div>
 <p>From the above source code, you can confirm that the error occurred due to accept.
-Let's dig into the cause.</p>
+Let’s dig into the cause.</p>
 <p>The error message provides hints for investigation:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>[10055]: no buffer
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>[10055]: no buffer
 </pre></div>
 </div>
-<p>10055 is a Windows socket error code and &quot;no buffer&quot; is a message by Groonga given in SOERR.</p>
+<p>10055 is a Windows socket error code and “no buffer” is a message by Groonga given in SOERR.</p>
 <p>Windows socket error codes are listed in the following page:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>https://msdn.microsoft.com/ja-jp/library/windows/desktop/ms740668(v=vs.85).aspx
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>https://msdn.microsoft.com/ja-jp/library/windows/desktop/ms740668(v=vs.85).aspx
 </pre></div>
 </div>
 <p>10055 is assigned to WSAENOBUFS and its description is as follows:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>No buffer space available.
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>No buffer space available.
 An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.
 </pre></div>
@@ -133,7 +125,7 @@ Finally, determine which one is appropriate for the situation when the error occ
       </div>
       <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
         <div class="sphinxsidebarwrapper">
-  <h3><a href="../index.html">Table Of Contents</a></h3>
+  <h3><a href="../index.html">Table of Contents</a></h3>
   <ul>
 <li><a class="reference internal" href="#">10.2. How to analyze error messages</a><ul>
 <li><a class="reference internal" href="#how-to-analyze-socket-errors">10.2.1. How to analyze socket errors</a><ul>
@@ -153,12 +145,12 @@ Finally, determine which one is appropriate for the situation when the error occ
                         title="next chapter">10.3. How to avoid mmap Cannot allocate memory error</a></p>
 <div id="searchbox" style="display: none" role="search">
   <h3>Quick search</h3>
+    <div class="searchformwrapper">
     <form class="search" action="../search.html" method="get">
-      <div><input type="text" name="q" /></div>
-      <div><input type="submit" value="Go" /></div>
-      <input type="hidden" name="check_keywords" value="yes" />
-      <input type="hidden" name="area" value="default" />
+      <input type="text" name="q" />
+      <input type="submit" value="Go" />
     </form>
+    </div>
 </div>
 <script type="text/javascript">$('#searchbox').show(0);</script>
         </div>
@@ -177,12 +169,12 @@ Finally, determine which one is appropriate for the situation when the error occ
         <li class="right" >
           <a href="different_results_with_the_same_keyword.html" title="10.1. 同じ検索キーワードなのに全文検索結果が異なる"
              >previous</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfa documentation</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v9.0.2 documentation</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../troubleshooting.html" >10. Troubleshooting</a> &#187;</li>
       </ul>
     </div>
     <div class="footer" role="contentinfo">
-        &#169; Copyright 2009-2018, Brazil, Inc.
+        &#169; Copyright 2009-2019, Brazil, Inc.
     </div>
   </body>
 </html>

data/vendor/local/share/doc/groonga/en/html/troubleshooting/mmap_cannot_allocate_memory.html CHANGED Viewed

@@ -1,34 +1,26 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
-    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-    <title>10.3. How to avoid mmap Cannot allocate memory error &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>10.3. How to avoid mmap Cannot allocate memory error &#8212; Groonga v9.0.2 documentation</title>
     <link rel="stylesheet" href="../_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
-    <script type="text/javascript">
-      var DOCUMENTATION_OPTIONS = {
-        URL_ROOT:    '../',
-        VERSION:     '7.1.0-73-g6d02cfa',
-        COLLAPSE_INDEX: false,
-        FILE_SUFFIX: '.html',
-        HAS_SOURCE:  false,
-        SOURCELINK_SUFFIX: '.txt'
-      };
-    </script>
+    <script type="text/javascript" id="documentation_options" data-url_root="../" src="../_static/documentation_options.js"></script>
     <script type="text/javascript" src="../_static/jquery.js"></script>
     <script type="text/javascript" src="../_static/underscore.js"></script>
     <script type="text/javascript" src="../_static/doctools.js"></script>
+    <script type="text/javascript" src="../_static/language_data.js"></script>
     <link rel="shortcut icon" href="../_static/favicon.ico"/>
     <link rel="index" title="Index" href="../genindex.html" />
     <link rel="search" title="Search" href="../search.html" />
     <link rel="next" title="11. Development" href="../development.html" />
     <link rel="prev" title="10.2. How to analyze error messages" href="how_to_analyze_error_message.html" />
-  </head>
-  <body>
+  </head><body>
 <div class="header">
   <h1 class="title">
     <a id="top-link" href="../index.html">
@@ -58,7 +50,7 @@
         <li class="right" >
           <a href="how_to_analyze_error_message.html" title="10.2. How to analyze error messages"
              accesskey="P">previous</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfa documentation</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v9.0.2 documentation</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../troubleshooting.html" accesskey="U">10. Troubleshooting</a> &#187;</li>
       </ul>
     </div>
@@ -74,27 +66,30 @@
 <h2>10.3.1. Example<a class="headerlink" href="#example" title="Permalink to this headline">¶</a></h2>
 <p>There is a case following mmap error in log file:</p>
 <blockquote>
-<div>2013-06-04 08:19:34.835218|A|4e86e700|mmap(4194304,551,432017408)=Cannot allocate memory &lt;13036498944&gt;</div></blockquote>
+<div><p>2013-06-04 08:19:34.835218|A|4e86e700|mmap(4194304,551,432017408)=Cannot allocate memory &lt;13036498944&gt;</p>
+</div></blockquote>
 <p>Note that &lt;13036498944&gt; means total size of mmap (almost 12GB) in this case.</p>
 </div>
 <div class="section" id="solution">
 <h2>10.3.2. Solution<a class="headerlink" href="#solution" title="Permalink to this headline">¶</a></h2>
 <p>So you need to confirm following point of views.</p>
 <ul class="simple">
-<li>Are there enough free memory?</li>
-<li>Are maximum number of mappings exceeded?</li>
+<li><p>Are there enough free memory?</p></li>
+<li><p>Are maximum number of mappings exceeded?</p></li>
 </ul>
 <p>To check there are enough free memory, you can use vmstat command.</p>
 <p>To check whether maximum number of mappings are exceeded, you can investigate the value of vm.max_map_count.</p>
-<p>If this issue is fixed by modifying the value of vm.max_map_count, it's exactly the reason.</p>
+<p>If this issue is fixed by modifying the value of vm.max_map_count, it’s exactly the reason.</p>
 <p>As groonga allocates memory chunks each 256KB, you can estimate the size of database you can handle by following formula:</p>
 <blockquote>
-<div>(database size) = vm.max_map_count * (memory chunks)</div></blockquote>
+<div><p>(database size) = vm.max_map_count * (memory chunks)</p>
+</div></blockquote>
 <p>If you want to handle over 16GB groonga database, you must specify at least 65536 as the value of vm.max_map_count:</p>
 <blockquote>
-<div>database size (16GB) = vm.max_map_count (65536) * memory chunks (256KB)</div></blockquote>
+<div><p>database size (16GB) = vm.max_map_count (65536) * memory chunks (256KB)</p>
+</div></blockquote>
 <p>You can modify vm.max_map_count temporary by sudo sysctl -w vm.max_map_count=65536.</p>
-<p>Then save the configuration value to <code class="docutils literal"><span class="pre">/etc/sysctl.conf</span></code> or <code class="docutils literal"><span class="pre">/etc/sysctl.d/*.conf</span></code>.</p>
+<p>Then save the configuration value to <code class="docutils literal notranslate"><span class="pre">/etc/sysctl.conf</span></code> or <code class="docutils literal notranslate"><span class="pre">/etc/sysctl.d/*.conf</span></code>.</p>
 <p>See <a class="reference internal" href="../reference/tuning.html"><span class="doc">Tuning</span></a> documentation about tuning related parameters.</p>
 </div>
 </div>
@@ -105,7 +100,7 @@
       </div>
       <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
         <div class="sphinxsidebarwrapper">
-  <h3><a href="../index.html">Table Of Contents</a></h3>
+  <h3><a href="../index.html">Table of Contents</a></h3>
   <ul>
 <li><a class="reference internal" href="#">10.3. How to avoid mmap Cannot allocate memory error</a><ul>
 <li><a class="reference internal" href="#example">10.3.1. Example</a></li>
@@ -122,12 +117,12 @@
                         title="next chapter">11. Development</a></p>
 <div id="searchbox" style="display: none" role="search">
   <h3>Quick search</h3>
+    <div class="searchformwrapper">
     <form class="search" action="../search.html" method="get">
-      <div><input type="text" name="q" /></div>
-      <div><input type="submit" value="Go" /></div>
-      <input type="hidden" name="check_keywords" value="yes" />
-      <input type="hidden" name="area" value="default" />
+      <input type="text" name="q" />
+      <input type="submit" value="Go" />
     </form>
+    </div>
 </div>
 <script type="text/javascript">$('#searchbox').show(0);</script>
         </div>
@@ -146,12 +141,12 @@
         <li class="right" >
           <a href="how_to_analyze_error_message.html" title="10.2. How to analyze error messages"
              >previous</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfa documentation</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v9.0.2 documentation</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../troubleshooting.html" >10. Troubleshooting</a> &#187;</li>
       </ul>
     </div>
     <div class="footer" role="contentinfo">
-        &#169; Copyright 2009-2018, Brazil, Inc.
+        &#169; Copyright 2009-2019, Brazil, Inc.
     </div>
   </body>
 </html>

data/vendor/local/share/doc/groonga/en/html/tutorial.html CHANGED Viewed

@@ -1,34 +1,26 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
-    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-    <title>4. Tutorial &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>4. Tutorial &#8212; Groonga v9.0.2 documentation</title>
     <link rel="stylesheet" href="_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="_static/pygments.css" type="text/css" />
-    <script type="text/javascript">
-      var DOCUMENTATION_OPTIONS = {
-        URL_ROOT:    './',
-        VERSION:     '7.1.0-73-g6d02cfa',
-        COLLAPSE_INDEX: false,
-        FILE_SUFFIX: '.html',
-        HAS_SOURCE:  false,
-        SOURCELINK_SUFFIX: '.txt'
-      };
-    </script>
+    <script type="text/javascript" id="documentation_options" data-url_root="./" src="_static/documentation_options.js"></script>
     <script type="text/javascript" src="_static/jquery.js"></script>
     <script type="text/javascript" src="_static/underscore.js"></script>
     <script type="text/javascript" src="_static/doctools.js"></script>
+    <script type="text/javascript" src="_static/language_data.js"></script>
     <link rel="shortcut icon" href="_static/favicon.ico"/>
     <link rel="index" title="Index" href="genindex.html" />
     <link rel="search" title="Search" href="search.html" />
     <link rel="next" title="4.1. Basic operations" href="tutorial/introduction.html" />
     <link rel="prev" title="3. Community" href="community.html" />
-  </head>
-  <body>
+  </head><body>
 <div class="header">
   <h1 class="title">
     <a id="top-link" href="index.html">
@@ -58,7 +50,7 @@
         <li class="right" >
           <a href="community.html" title="3. Community"
              accesskey="P">previous</a> |</li>
-        <li class="nav-item nav-item-0"><a href="index.html">Groonga v7.1.0-73-g6d02cfa documentation</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="index.html">Groonga v9.0.2 documentation</a> &#187;</li>
       </ul>
     </div>
@@ -108,7 +100,7 @@
 </li>
 <li class="toctree-l1"><a class="reference internal" href="tutorial/search.html">4.4. Various search conditions</a><ul>
 <li class="toctree-l2"><a class="reference internal" href="tutorial/search.html#narrow-down-full-text-search-by-using-syntax-like-javascript">4.4.1. Narrow down &amp; Full-text search by using syntax like JavaScript</a></li>
-<li class="toctree-l2"><a class="reference internal" href="tutorial/search.html#sort-by-using-scorer">4.4.2. Sort by using <code class="docutils literal"><span class="pre">scorer</span></code></a></li>
+<li class="toctree-l2"><a class="reference internal" href="tutorial/search.html#sort-by-using-scorer">4.4.2. Sort by using <code class="docutils literal notranslate"><span class="pre">scorer</span></code></a></li>
 <li class="toctree-l2"><a class="reference internal" href="tutorial/search.html#narrow-down-sort-by-using-location-information">4.4.3. Narrow down &amp; sort by using location information</a></li>
 </ul>
 </li>
@@ -137,7 +129,7 @@
 </ul>
 </li>
 <li class="toctree-l1"><a class="reference internal" href="tutorial/lexicon.html">4.9. Additional information about lexicon for full text search</a></li>
-<li class="toctree-l1"><a class="reference internal" href="tutorial/micro_blog.html">4.10. Let's create micro-blog</a><ul>
+<li class="toctree-l1"><a class="reference internal" href="tutorial/micro_blog.html">4.10. Let’s create micro-blog</a><ul>
 <li class="toctree-l2"><a class="reference internal" href="tutorial/micro_blog.html#create-a-table">4.10.1. Create a table</a></li>
 <li class="toctree-l2"><a class="reference internal" href="tutorial/micro_blog.html#loading-data">4.10.2. Loading data</a></li>
 <li class="toctree-l2"><a class="reference internal" href="tutorial/micro_blog.html#search">4.10.3. Search</a></li>
@@ -166,12 +158,12 @@
                         title="next chapter">4.1. Basic operations</a></p>
 <div id="searchbox" style="display: none" role="search">
   <h3>Quick search</h3>
+    <div class="searchformwrapper">
     <form class="search" action="search.html" method="get">
-      <div><input type="text" name="q" /></div>
-      <div><input type="submit" value="Go" /></div>
-      <input type="hidden" name="check_keywords" value="yes" />
-      <input type="hidden" name="area" value="default" />
+      <input type="text" name="q" />
+      <input type="submit" value="Go" />
     </form>
+    </div>
 </div>
 <script type="text/javascript">$('#searchbox').show(0);</script>
         </div>
@@ -190,11 +182,11 @@
         <li class="right" >
           <a href="community.html" title="3. Community"
              >previous</a> |</li>
-        <li class="nav-item nav-item-0"><a href="index.html">Groonga v7.1.0-73-g6d02cfa documentation</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="index.html">Groonga v9.0.2 documentation</a> &#187;</li>
       </ul>
     </div>
     <div class="footer" role="contentinfo">
-        &#169; Copyright 2009-2018, Brazil, Inc.
+        &#169; Copyright 2009-2019, Brazil, Inc.
     </div>
   </body>
 </html>

data/vendor/local/share/doc/groonga/en/html/tutorial/data.html CHANGED Viewed

@@ -1,34 +1,26 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
-  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!DOCTYPE html>
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en">
   <head>
-    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-    <title>4.3. Various data types &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>4.3. Various data types &#8212; Groonga v9.0.2 documentation</title>
     <link rel="stylesheet" href="../_static/groonga.css" type="text/css" />
     <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
-    <script type="text/javascript">
-      var DOCUMENTATION_OPTIONS = {
-        URL_ROOT:    '../',
-        VERSION:     '7.1.0-73-g6d02cfa',
-        COLLAPSE_INDEX: false,
-        FILE_SUFFIX: '.html',
-        HAS_SOURCE:  false,
-        SOURCELINK_SUFFIX: '.txt'
-      };
-    </script>
+    <script type="text/javascript" id="documentation_options" data-url_root="../" src="../_static/documentation_options.js"></script>
     <script type="text/javascript" src="../_static/jquery.js"></script>
     <script type="text/javascript" src="../_static/underscore.js"></script>
     <script type="text/javascript" src="../_static/doctools.js"></script>
+    <script type="text/javascript" src="../_static/language_data.js"></script>
     <link rel="shortcut icon" href="../_static/favicon.ico"/>
     <link rel="index" title="Index" href="../genindex.html" />
     <link rel="search" title="Search" href="../search.html" />
     <link rel="next" title="4.4. Various search conditions" href="search.html" />
     <link rel="prev" title="4.2. Remote access" href="network.html" />
-  </head>
-  <body>
+  </head><body>
 <div class="header">
   <h1 class="title">
     <a id="top-link" href="../index.html">
@@ -58,7 +50,7 @@
         <li class="right" >
           <a href="network.html" title="4.2. Remote access"
              accesskey="P">previous</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfa documentation</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v9.0.2 documentation</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../tutorial.html" accesskey="U">4. Tutorial</a> &#187;</li>
       </ul>
     </div>
@@ -73,11 +65,11 @@
 <p>Groonga is a full text search engine but also serves as a column-oriented data store. Groonga supports various data types, such as numeric types, string types, date and time type, longitude and latitude types, etc. This tutorial shows a list of data types and explains how to use them.</p>
 <div class="section" id="overview">
 <h2>4.3.1. Overview<a class="headerlink" href="#overview" title="Permalink to this headline">¶</a></h2>
-<p>The basic data types of Groonga are roughly divided into 5 groups --- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see <a class="reference internal" href="../reference/types.html"><span class="doc">Data types</span></a>.</p>
+<p>The basic data types of Groonga are roughly divided into 5 groups — boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see <a class="reference internal" href="../reference/types.html"><span class="doc">Data types</span></a>.</p>
 <p>In addition, Groonga supports reference types and vector types. Reference types are designed for accessing other tables. Vector types are designed for storing a variable number of values in one element.</p>
-<p>First, let's create a table for this tutorial.</p>
+<p>First, let’s create a table for this tutorial.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create --name ToyBox --flags TABLE_HASH_KEY --key_type ShortText
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create --name ToyBox --flags TABLE_HASH_KEY --key_type ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 </pre></div>
 </div>
@@ -87,7 +79,7 @@
 <p>The boolean type is used to store true or false. To create a boolean type column, specify Bool to the <cite>type</cite> parameter of <a class="reference internal" href="../reference/commands/column_create.html"><span class="doc">column_create</span></a> command. The default value of the boolean type is false.</p>
 <p>The following example creates a boolean type column and adds three records. Note that the third record has the default value because no value is specified.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>column_create --table ToyBox --name is_animal --type Bool
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>column_create --table ToyBox --name is_animal --type Bool
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 load --table ToyBox
 [
@@ -141,7 +133,7 @@ select --table ToyBox --output_columns _key,is_animal
 <p>The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see <a class="reference internal" href="../reference/types.html"><span class="doc">Data types</span></a>. The default value of the numeric types is 0.</p>
 <p>The following example creates an Int8 column and a Float column, and then updates existing records. The <a class="reference internal" href="../reference/commands/load.html"><span class="doc">load</span></a> command updates the weight column as expected. On the other hand, the price column values are different from the specified values because 15.9 is not an integer and 200 is too large. 15.9 is converted to 15 by removing the fractional part. 200 causes an overflow and the result becomes -56. Note that the result of an overflow/underflow is undefined.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>column_create --table ToyBox --name price --type Int8
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>column_create --table ToyBox --name price --type Int8
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 column_create --table ToyBox --name weight --type Float
 # [[0, 1337566253.89858, 0.000355720520019531], true]
@@ -202,11 +194,11 @@ select --table ToyBox --output_columns _key,price,weight
 <div class="section" id="string-types">
 <h2>4.3.4. String types<a class="headerlink" href="#string-types" title="Permalink to this headline">¶</a></h2>
 <p>The string types are divided according to the maximum length. For more details, see <a class="reference internal" href="../reference/types.html"><span class="doc">Data types</span></a>. The default value is the zero-length string.</p>
-<p>The following example creates a <code class="docutils literal"><span class="pre">ShortText</span></code> column and updates
-existing records. The third record (<code class="docutils literal"><span class="pre">&quot;Block&quot;</span></code> key record) has the
-default value (zero-length string) because it's not updated.</p>
+<p>The following example creates a <code class="docutils literal notranslate"><span class="pre">ShortText</span></code> column and updates
+existing records. The third record (<code class="docutils literal notranslate"><span class="pre">&quot;Block&quot;</span></code> key record) has the
+default value (zero-length string) because it’s not updated.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>column_create --table ToyBox --name name --type ShortText
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>column_create --table ToyBox --name name --type ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 load --table ToyBox
 [
@@ -258,15 +250,15 @@ select --table ToyBox --output_columns _key,name
 <h2>4.3.5. Date and time type<a class="headerlink" href="#date-and-time-type" title="Permalink to this headline">¶</a></h2>
 <p>The date and time type of Groonga is Time. Actually, a Time column stores a date and time as the number of microseconds since the Epoch, 1970-01-01 00:00:00. A Time value can represent a date and time before the Epoch because the actual data type is a signed integer. Note that <a class="reference internal" href="../reference/commands/load.html"><span class="doc">load</span></a> and <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> commands use a decimal number to represent a data and time in seconds. The default value is 0.0, which means the Epoch.</p>
 <div class="admonition note">
-<p class="first admonition-title">Note</p>
-<p class="last">Groonga internally holds the value of Epoch as pair of integer. The first integer represents the value of seconds, on the other hand, the second integer represents the value of micro seconds.
+<p class="admonition-title">Note</p>
+<p>Groonga internally holds the value of Epoch as pair of integer. The first integer represents the value of seconds, on the other hand, the second integer represents the value of micro seconds.
 So, Groonga shows the value of Epoch as floating point. Integral part means the value of seconds, fraction part means the value of micro seconds.</p>
 </div>
-<p>The following example creates a <code class="docutils literal"><span class="pre">Time</span></code> column and updates existing
-records. The first record (<code class="docutils literal"><span class="pre">&quot;Monkey&quot;</span></code> key record) has the default
-value (<code class="docutils literal"><span class="pre">0.0</span></code>) because it's not updated.</p>
+<p>The following example creates a <code class="docutils literal notranslate"><span class="pre">Time</span></code> column and updates existing
+records. The first record (<code class="docutils literal notranslate"><span class="pre">&quot;Monkey&quot;</span></code> key record) has the default
+value (<code class="docutils literal notranslate"><span class="pre">0.0</span></code>) because it’s not updated.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>column_create --table ToyBox --name time --type Time
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>column_create --table ToyBox --name time --type Time
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 load --table ToyBox
 [
@@ -318,15 +310,15 @@ select --table ToyBox --output_columns _key,time
 <h2>4.3.6. Longitude and latitude types<a class="headerlink" href="#longitude-and-latitude-types" title="Permalink to this headline">¶</a></h2>
 <p>The longitude and latitude types are divided according to the geographic coordinate system. For more details, see <a class="reference internal" href="../reference/types.html"><span class="doc">Data types</span></a>. To represent a longitude and latitude, Groonga uses a string formatted as follows:</p>
 <ul class="simple">
-<li>&quot;longitude x latitude&quot; in milliseconds (e.g.: &quot;128452975x503157902&quot;)</li>
-<li>&quot;longitude x latitude&quot; in degrees (e.g.: &quot;35.6813819x139.7660839&quot;)</li>
+<li><p>“longitude x latitude” in milliseconds (e.g.: “128452975x503157902”)</p></li>
+<li><p>“longitude x latitude” in degrees (e.g.: “35.6813819x139.7660839”)</p></li>
 </ul>
-<p>A number with/without a decimal point represents a longitude or latitude in milliseconds/degrees respectively. Note that a combination of a number with a decimal point and a number without a decimal point (e.g. 35.1x139) must not be used. A comma (',') is also available as a delimiter. The default value is &quot;0x0&quot;.</p>
-<p>The following example creates a <code class="docutils literal"><span class="pre">WGS84GeoPoint</span></code> column and updates
-existing records. The second record (<code class="docutils literal"><span class="pre">&quot;Flower&quot;</span></code> key record) has the
-default value (<code class="docutils literal"><span class="pre">&quot;0x0&quot;</span></code>) because it's not updated.</p>
+<p>A number with/without a decimal point represents a longitude or latitude in milliseconds/degrees respectively. Note that a combination of a number with a decimal point and a number without a decimal point (e.g. 35.1x139) must not be used. A comma (‘,’) is also available as a delimiter. The default value is “0x0”.</p>
+<p>The following example creates a <code class="docutils literal notranslate"><span class="pre">WGS84GeoPoint</span></code> column and updates
+existing records. The second record (<code class="docutils literal notranslate"><span class="pre">&quot;Flower&quot;</span></code> key record) has the
+default value (<code class="docutils literal notranslate"><span class="pre">&quot;0x0&quot;</span></code>) because it’s not updated.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>column_create --table ToyBox --name location --type WGS84GeoPoint
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>column_create --table ToyBox --name location --type WGS84GeoPoint
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 load --table ToyBox
 [
@@ -377,13 +369,13 @@ select --table ToyBox --output_columns _key,location
 <div class="section" id="reference-types">
 <h2>4.3.7. Reference types<a class="headerlink" href="#reference-types" title="Permalink to this headline">¶</a></h2>
 <p>Groonga supports a reference column, which stores references to records in its associated table. In practice, a reference column stores the IDs of the referred records in the associated table and enables access to those records.</p>
-<p>You can specify a column in the associated table to the <code class="docutils literal"><span class="pre">output_columns</span></code> parameter of a <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command. The format is <code class="docutils literal"><span class="pre">Src.Dest</span></code> where Src is the name of the reference column and Dest is the name of the target column. If only the reference column is specified, it is handled as <code class="docutils literal"><span class="pre">Src._key</span></code>. Note that if a reference does not point to a valid record, a <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command outputs the default value of the target column.</p>
-<p>The following example adds a reference column to the <code class="docutils literal"><span class="pre">Site</span></code> table
+<p>You can specify a column in the associated table to the <code class="docutils literal notranslate"><span class="pre">output_columns</span></code> parameter of a <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command. The format is <code class="docutils literal notranslate"><span class="pre">Src.Dest</span></code> where Src is the name of the reference column and Dest is the name of the target column. If only the reference column is specified, it is handled as <code class="docutils literal notranslate"><span class="pre">Src._key</span></code>. Note that if a reference does not point to a valid record, a <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command outputs the default value of the target column.</p>
+<p>The following example adds a reference column to the <code class="docutils literal notranslate"><span class="pre">Site</span></code> table
 that was created in <a class="reference internal" href="introduction.html#tutorial-introduction-create-table"><span class="std std-ref">Create a table</span></a>. The new
-column, named <code class="docutils literal"><span class="pre">link</span></code>, is designed for storing links among records in
-the <code class="docutils literal"><span class="pre">Site</span></code> table.</p>
+column, named <code class="docutils literal notranslate"><span class="pre">link</span></code>, is designed for storing links among records in
+the <code class="docutils literal notranslate"><span class="pre">Site</span></code> table.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>column_create --table Site --name link --type Site
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>column_create --table Site --name link --type Site
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 load --table Site
 [
@@ -431,14 +423,14 @@ select --table Site --output_columns _key,title,link._key,link.title --query tit
 # ]
 </pre></div>
 </div>
-<p>The <cite>type</cite> parameter of the <a class="reference internal" href="../reference/commands/column_create.html"><span class="doc">column_create</span></a> command specifies the table to be associated with the reference column. In this example, the reference column is associated with the own table. Then, the <a class="reference internal" href="../reference/commands/load.html"><span class="doc">load</span></a> command registers a link from &quot;<a class="reference external" href="http://example.org">http://example.org</a>&quot; to &quot;<a class="reference external" href="http://example.net">http://example.net</a>&quot;. Note that a reference column requires the primary key, not the ID, of the record to be referred to. After that, the link is confirmed by the <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command. In this case, the primary key and the title of the referred record are output because link._key and link.title are specified to the <cite>output_columns</cite> parameter.</p>
+<p>The <cite>type</cite> parameter of the <a class="reference internal" href="../reference/commands/column_create.html"><span class="doc">column_create</span></a> command specifies the table to be associated with the reference column. In this example, the reference column is associated with the own table. Then, the <a class="reference internal" href="../reference/commands/load.html"><span class="doc">load</span></a> command registers a link from “<a class="reference external" href="http://example.org">http://example.org</a>” to “<a class="reference external" href="http://example.net">http://example.net</a>”. Note that a reference column requires the primary key, not the ID, of the record to be referred to. After that, the link is confirmed by the <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command. In this case, the primary key and the title of the referred record are output because link._key and link.title are specified to the <cite>output_columns</cite> parameter.</p>
 </div>
 <div class="section" id="vector-types">
 <h2>4.3.8. Vector types<a class="headerlink" href="#vector-types" title="Permalink to this headline">¶</a></h2>
 <p>Groonga supports a vector column, in which each element can store a variable number of values. To create a vector column, specify the COLUMN_VECTOR flag to the <cite>flags</cite> parameter of a <a class="reference internal" href="../reference/commands/column_create.html"><span class="doc">column_create</span></a> command. A vector column is useful to represent a many-to-many relationship.</p>
 <p>The previous example used a regular column, so each record could have at most one link. Obviously, the specification is insufficient because a site usually has more than one links. To solve this problem, the following example uses a vector column.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>column_create --table Site --name links --flags COLUMN_VECTOR --type Site
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>column_create --table Site --name links --flags COLUMN_VECTOR --type Site
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 load --table Site
 [
@@ -494,7 +486,7 @@ select --table Site --output_columns _key,title,links._key,links.title --query t
 # ]
 </pre></div>
 </div>
-<p>The only difference at the first step is the <cite>flags</cite> parameter that specifies to create a vector column. The <cite>type</cite> parameter of the <a class="reference internal" href="../reference/commands/column_create.html"><span class="doc">column_create</span></a> command is the same as in the previous example. Then, the <a class="reference internal" href="../reference/commands/load.html"><span class="doc">load</span></a> command registers three links from &quot;<a class="reference external" href="http://example.org/">http://example.org/</a>&quot; to &quot;<a class="reference external" href="http://example.net/">http://example.net/</a>&quot;, &quot;<a class="reference external" href="http://example.org/">http://example.org/</a>&quot; and &quot;<a class="reference external" href="http://example.com/">http://example.com/</a>&quot;. After that, the links are confirmed by the <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command. In this case, the primary keys and the titles are output as arrays because links._key and links.title are specified to the <cite>output_columns</cite> parameter.</p>
+<p>The only difference at the first step is the <cite>flags</cite> parameter that specifies to create a vector column. The <cite>type</cite> parameter of the <a class="reference internal" href="../reference/commands/column_create.html"><span class="doc">column_create</span></a> command is the same as in the previous example. Then, the <a class="reference internal" href="../reference/commands/load.html"><span class="doc">load</span></a> command registers three links from “<a class="reference external" href="http://example.org/">http://example.org/</a>” to “<a class="reference external" href="http://example.net/">http://example.net/</a>”, “<a class="reference external" href="http://example.org/">http://example.org/</a>” and “<a class="reference external" href="http://example.com/">http://example.com/</a>”. After that, the links are confirmed by the <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command. In this case, the primary keys and the titles are output as arrays because links._key and links.title are specified to the <cite>output_columns</cite> parameter.</p>
 </div>
 </div>
@@ -504,7 +496,7 @@ select --table Site --output_columns _key,title,links._key,links.title --query t
       </div>
       <div class="sphinxsidebar" role="navigation" aria-label="main navigation">
         <div class="sphinxsidebarwrapper">
-  <h3><a href="../index.html">Table Of Contents</a></h3>
+  <h3><a href="../index.html">Table of Contents</a></h3>
   <ul>
 <li><a class="reference internal" href="#">4.3. Various data types</a><ul>
 <li><a class="reference internal" href="#overview">4.3.1. Overview</a></li>
@@ -527,12 +519,12 @@ select --table Site --output_columns _key,title,links._key,links.title --query t
                         title="next chapter">4.4. Various search conditions</a></p>
 <div id="searchbox" style="display: none" role="search">
   <h3>Quick search</h3>
+    <div class="searchformwrapper">
     <form class="search" action="../search.html" method="get">
-      <div><input type="text" name="q" /></div>
-      <div><input type="submit" value="Go" /></div>
-      <input type="hidden" name="check_keywords" value="yes" />
-      <input type="hidden" name="area" value="default" />
+      <input type="text" name="q" />
+      <input type="submit" value="Go" />
     </form>
+    </div>
 </div>
 <script type="text/javascript">$('#searchbox').show(0);</script>
         </div>
@@ -551,12 +543,12 @@ select --table Site --output_columns _key,title,links._key,links.title --query t
         <li class="right" >
           <a href="network.html" title="4.2. Remote access"
              >previous</a> |</li>
-        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v7.1.0-73-g6d02cfa documentation</a> &#187;</li>
+        <li class="nav-item nav-item-0"><a href="../index.html">Groonga v9.0.2 documentation</a> &#187;</li>
           <li class="nav-item nav-item-1"><a href="../tutorial.html" >4. Tutorial</a> &#187;</li>
       </ul>
     </div>
     <div class="footer" role="contentinfo">
-        &#169; Copyright 2009-2018, Brazil, Inc.
+        &#169; Copyright 2009-2019, Brazil, Inc.
     </div>
   </body>
 </html>