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

rroonga 7.1.1-x64-mingw32 → 9.0.2-x64-mingw32

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (980) hide show

data/vendor/local/share/doc/groonga/en/html/tutorial/network.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.2. Remote access &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>4.2. Remote access &#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.3. Various data types" href="data.html" />
     <link rel="prev" title="4.1. Basic operations" href="introduction.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="introduction.html" title="4.1. Basic operations"
              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>
@@ -77,28 +69,28 @@
 <h3>4.2.1.1. How to run an HTTP server<a class="headerlink" href="#how-to-run-an-http-server" title="Permalink to this headline">¶</a></h3>
 <p>Groonga supports the hypertext transfer protocol (HTTP). The following form shows how to run Groonga as an HTTP server daemon.</p>
 <p>Form:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>groonga [-p PORT_NUMBER] -d --protocol http DB_PATH
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>groonga [-p PORT_NUMBER] -d --protocol http DB_PATH
 </pre></div>
 </div>
-<p>The <cite>--protocol</cite> option and its argument specify the protocol of the server. &quot;http&quot; specifies to use HTTP. If the <cite>-p</cite> option is not specified, Groonga uses the default port number 10041.</p>
+<p>The <cite>–protocol</cite> option and its argument specify the protocol of the server. “http” specifies to use HTTP. If the <cite>-p</cite> option is not specified, Groonga uses the default port number 10041.</p>
 <p>The following command runs an HTTP server that listens on the port number 80.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>% sudo groonga -p 80 -d --protocol http /tmp/groonga-databases/introduction.db
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>% sudo groonga -p 80 -d --protocol http /tmp/groonga-databases/introduction.db
 %
 </pre></div>
 </div>
 <div class="admonition note">
-<p class="first admonition-title">Note</p>
-<p class="last">You must have root privileges if you listen on the port number 80 (well known port).
+<p class="admonition-title">Note</p>
+<p>You must have root privileges if you listen on the port number 80 (well known port).
 There is no such a limitation about the port number 1024 or over.</p>
 </div>
 </div>
 <div class="section" id="how-to-send-a-command-to-an-http-server">
 <h3>4.2.1.2. How to send a command to an HTTP server<a class="headerlink" href="#how-to-send-a-command-to-an-http-server" title="Permalink to this headline">¶</a></h3>
-<p>You can send a command to an HTTP server by sending a GET request to /d/COMMAND_NAME. Command parameters can be passed as parameters of the GET request. The format is &quot;?NAME_1=VALUE_1&amp;NAME_2=VALUE_2&amp;...&quot;.</p>
+<p>You can send a command to an HTTP server by sending a GET request to /d/COMMAND_NAME. Command parameters can be passed as parameters of the GET request. The format is “?NAME_1=VALUE_1&amp;NAME_2=VALUE_2&amp;…”.</p>
 <p>The following example shows how to send commands to an HTTP server.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/d/status
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/d/status
 Executed command:
 status
 # [
@@ -195,7 +187,7 @@ select --table Site --query title:@this
 </div>
 <div class="section" id="security-issues">
 <h2>4.2.3. Security issues<a class="headerlink" href="#security-issues" title="Permalink to this headline">¶</a></h2>
-<p>Groonga servers don't support user authentication. Everyone can view and modify databases hosted by Groonga servers. You are recommended to restrict IP addresses that can access Groonga servers. You can use iptables or similar for this purpose.</p>
+<p>Groonga servers don’t support user authentication. Everyone can view and modify databases hosted by Groonga servers. You are recommended to restrict IP addresses that can access Groonga servers. You can use iptables or similar for this purpose.</p>
 </div>
 </div>
@@ -205,7 +197,7 @@ select --table Site --query title:@this
       </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.2. Remote access</a><ul>
 <li><a class="reference internal" href="#hypertext-transfer-protocol-http">4.2.1. Hypertext transfer protocol (HTTP)</a><ul>
@@ -227,12 +219,12 @@ select --table Site --query title:@this
                         title="next chapter">4.3. Various data types</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>
@@ -251,12 +243,12 @@ select --table Site --query title:@this
         <li class="right" >
           <a href="introduction.html" title="4.1. Basic operations"
              >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>

data/vendor/local/share/doc/groonga/en/html/tutorial/patricia_trie.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.8. Prefix search with patricia trie &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>4.8. Prefix search with patricia trie &#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.9. Additional information about lexicon for full text search" href="lexicon.html" />
     <link rel="prev" title="4.7. match_columns parameter" href="match_columns.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="match_columns.html" title="4.7. match_columns parameter"
              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>
@@ -77,7 +69,7 @@ By specifying it, You can do prefix search.</p>
 <h2>4.8.1. Prefix search by primary key<a class="headerlink" href="#prefix-search-by-primary-key" title="Permalink to this headline">¶</a></h2>
 <p>table_create command which uses TABLE_PAT_KEY for flags option supports prefix search by primary key.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create --name PatPrefix --flags TABLE_PAT_KEY --key_type ShortText
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create --name PatPrefix --flags TABLE_PAT_KEY --key_type ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 load --table PatPrefix
 [
@@ -129,9 +121,9 @@ select --table PatPrefix --query _key:^Je
 <h2>4.8.2. Suffix search by primary key<a class="headerlink" href="#suffix-search-by-primary-key" title="Permalink to this headline">¶</a></h2>
 <p>table_create command which uses TABLE_PAT_KEY and KEY_WITH_SIS for flags option supports prefix search and suffix search by primary key.</p>
 <p>If you set KEY_WITH_SIS flag, suffix search records also are added when you add the data. So if you search simply, the automatically added records are hit in addition to the original records. In order to search only the original records, you need a plan.</p>
-<p>For example, in order to make this distinction between the original records and automatically added records, add the original column indicating that it is the original record, and add original column is <code class="docutils literal"><span class="pre">true</span></code> to the search condition. For attention, use <code class="docutils literal"><span class="pre">--filter</span></code> option because <code class="docutils literal"><span class="pre">--query</span></code> option is not specify <code class="docutils literal"><span class="pre">Bool</span></code> type value intuitively.</p>
+<p>For example, in order to make this distinction between the original records and automatically added records, add the original column indicating that it is the original record, and add original column is <code class="docutils literal notranslate"><span class="pre">true</span></code> to the search condition. For attention, use <code class="docutils literal notranslate"><span class="pre">--filter</span></code> option because <code class="docutils literal notranslate"><span class="pre">--query</span></code> option is not specify <code class="docutils literal notranslate"><span class="pre">Bool</span></code> type value intuitively.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create --name PatSuffix --flags TABLE_PAT_KEY|KEY_WITH_SIS --key_type ShortText
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create --name PatSuffix --flags TABLE_PAT_KEY|KEY_WITH_SIS --key_type ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 column_create --table PatSuffix --name original --type Bool
 # [[0, 1337566253.89858, 0.000355720520019531], true]
@@ -242,7 +234,7 @@ select --table PatSuffix --filter &#39;_key @$ &quot;ゆき&quot; &amp;&amp; ori
       </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.8. Prefix search with patricia trie</a><ul>
 <li><a class="reference internal" href="#prefix-search-by-primary-key">4.8.1. Prefix search by primary key</a></li>
@@ -259,12 +251,12 @@ select --table PatSuffix --filter &#39;_key @$ &quot;ゆき&quot; &amp;&amp; ori
                         title="next chapter">4.9. Additional information about lexicon for full text search</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>
@@ -283,12 +275,12 @@ select --table PatSuffix --filter &#39;_key @$ &quot;ゆき&quot; &amp;&amp; ori
         <li class="right" >
           <a href="match_columns.html" title="4.7. match_columns parameter"
              >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>

data/vendor/local/share/doc/groonga/en/html/tutorial/query_expansion.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.11. Query expansion &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>4.11. Query expansion &#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="5. Server" href="../server.html" />
-    <link rel="prev" title="4.10. Let&#39;s create micro-blog" href="micro_blog.html" />
-  </head>
-  <body>
+    <link rel="prev" title="4.10. Let’s create micro-blog" href="micro_blog.html" />
+  </head><body>
 <div class="header">
   <h1 class="title">
     <a id="top-link" href="../index.html">
@@ -56,9 +48,9 @@
           <a href="../server.html" title="5. Server"
              accesskey="N">next</a> |</li>
         <li class="right" >
-          <a href="micro_blog.html" title="4.10. Let&#39;s create micro-blog"
+          <a href="micro_blog.html" title="4.10. Let’s create micro-blog"
              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>
@@ -70,18 +62,18 @@
   <div class="section" id="query-expansion">
 <h1>4.11. Query expansion<a class="headerlink" href="#query-expansion" title="Permalink to this headline">¶</a></h1>
-<p>Groonga accepts <code class="docutils literal"><span class="pre">query_expander</span></code> parameter for <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command.
+<p>Groonga accepts <code class="docutils literal notranslate"><span class="pre">query_expander</span></code> parameter for <a class="reference internal" href="../reference/commands/select.html"><span class="doc">select</span></a> command.
 It enables you to extend your query string.</p>
-<p>For example, if user searches &quot;theatre&quot; instead of &quot;theater&quot;,
-query expansion enables to return search results of &quot;theatre OR theater&quot;.
+<p>For example, if user searches “theatre” instead of “theater”,
+query expansion enables to return search results of “theatre OR theater”.
 This kind of way reduces search leakages. This is what really user wants.</p>
 <div class="section" id="preparation">
 <h2>4.11.1. Preparation<a class="headerlink" href="#preparation" title="Permalink to this headline">¶</a></h2>
 <p>To use query expansion, you need to create table which stores documents, synonym table which stores query string and replacement string.
 In synonym table, primary key represents original string, the column of ShortText represents modified string.</p>
-<p>Let's create document table and synonym table.</p>
+<p>Let’s create document table and synonym table.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create Doc TABLE_PAT_KEY ShortText
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create Doc TABLE_PAT_KEY ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 column_create Doc body COLUMN_SCALAR ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
@@ -107,14 +99,14 @@ load --table Synonym
 # [[0, 1337566253.89858, 0.000355720520019531], 2]
 </pre></div>
 </div>
-<p>In this case, it doesn't occur search leakage because it creates synonym table which accepts &quot;theatre&quot; and &quot;theater&quot; as query string.</p>
+<p>In this case, it doesn’t occur search leakage because it creates synonym table which accepts “theatre” and “theater” as query string.</p>
 </div>
 <div class="section" id="search">
 <h2>4.11.2. Search<a class="headerlink" href="#search" title="Permalink to this headline">¶</a></h2>
-<p>Then, let's use prepared synonym table.
-First, use select command without <code class="docutils literal"><span class="pre">query_expander</span></code> parameter.</p>
+<p>Then, let’s use prepared synonym table.
+First, use select command without <code class="docutils literal notranslate"><span class="pre">query_expander</span></code> parameter.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select Doc --match_columns body --query &quot;theater&quot;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select Doc --match_columns body --query &quot;theater&quot;
 # [
 #   [
 #     0,
@@ -185,9 +177,9 @@ select Doc --match_columns body --query &quot;theatre&quot;
 </pre></div>
 </div>
 <p>Above query returns the record which completely equal to query string.</p>
-<p>Then, use <code class="docutils literal"><span class="pre">query_expander</span></code> parameter against <code class="docutils literal"><span class="pre">body</span></code> column of <code class="docutils literal"><span class="pre">Synonym</span></code> table.</p>
+<p>Then, use <code class="docutils literal notranslate"><span class="pre">query_expander</span></code> parameter against <code class="docutils literal notranslate"><span class="pre">body</span></code> column of <code class="docutils literal notranslate"><span class="pre">Synonym</span></code> table.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select Doc --match_columns body --query &quot;theater&quot; --query_expander Synonym.body
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select Doc --match_columns body --query &quot;theater&quot; --query_expander Synonym.body
 # [
 #   [
 #     0,
@@ -267,7 +259,7 @@ select Doc --match_columns body --query &quot;theatre&quot; --query_expander Syn
 # ]
 </pre></div>
 </div>
-<p>In which cases, query string is replaced to &quot;(theater OR theatre)&quot;, thus synonym is considered for full text search.</p>
+<p>In which cases, query string is replaced to “(theater OR theatre)”, thus synonym is considered for full text search.</p>
 </div>
 </div>
@@ -277,7 +269,7 @@ select Doc --match_columns body --query &quot;theatre&quot; --query_expander Syn
       </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.11. Query expansion</a><ul>
 <li><a class="reference internal" href="#preparation">4.11.1. Preparation</a></li>
@@ -288,18 +280,18 @@ select Doc --match_columns body --query &quot;theatre&quot; --query_expander Syn
   <h4>Previous topic</h4>
   <p class="topless"><a href="micro_blog.html"
-                        title="previous chapter">4.10. Let's create micro-blog</a></p>
+                        title="previous chapter">4.10. Let’s create micro-blog</a></p>
   <h4>Next topic</h4>
   <p class="topless"><a href="../server.html"
                         title="next chapter">5. Server</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>
@@ -316,14 +308,14 @@ select Doc --match_columns body --query &quot;theatre&quot; --query_expander Syn
           <a href="../server.html" title="5. Server"
              >next</a> |</li>
         <li class="right" >
-          <a href="micro_blog.html" title="4.10. Let&#39;s create micro-blog"
+          <a href="micro_blog.html" title="4.10. Let’s create micro-blog"
              >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>

data/vendor/local/share/doc/groonga/en/html/tutorial/search.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.4. Various search conditions &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>4.4. Various search conditions &#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.5. Drilldown" href="drilldown.html" />
     <link rel="prev" title="4.3. Various data types" href="data.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="data.html" title="4.3. Various data types"
              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,10 +65,10 @@
 <p>Groonga supports to narrow down by using syntax like JavaScript, sort by the calculated value. Additionally, Groonga also supports to narrow down &amp; sort search results by using location information (latitude &amp; longitude).</p>
 <div class="section" id="narrow-down-full-text-search-by-using-syntax-like-javascript">
 <h2>4.4.1. Narrow down &amp; Full-text search by using syntax like JavaScript<a class="headerlink" href="#narrow-down-full-text-search-by-using-syntax-like-javascript" title="Permalink to this headline">¶</a></h2>
-<p>The <code class="docutils literal"><span class="pre">filter</span></code> parameter of <code class="docutils literal"><span class="pre">select</span></code> command accepts the search condition.
-There is one difference between <code class="docutils literal"><span class="pre">filter</span></code> parameter and <code class="docutils literal"><span class="pre">query</span></code> parameter, you need to specify the condition by syntax like JavaScript for <code class="docutils literal"><span class="pre">filter</span></code> parameter.</p>
+<p>The <code class="docutils literal notranslate"><span class="pre">filter</span></code> parameter of <code class="docutils literal notranslate"><span class="pre">select</span></code> command accepts the search condition.
+There is one difference between <code class="docutils literal notranslate"><span class="pre">filter</span></code> parameter and <code class="docutils literal notranslate"><span class="pre">query</span></code> parameter, you need to specify the condition by syntax like JavaScript for <code class="docutils literal notranslate"><span class="pre">filter</span></code> parameter.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --filter &quot;_id &lt;= 1&quot; --output_columns _id,_key
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Site --filter &quot;_id &lt;= 1&quot; --output_columns _id,_key
 # [
 #   [
 #     0,
@@ -107,14 +99,14 @@ There is one difference between <code class="docutils literal"><span class="pre"
 # ]
 </pre></div>
 </div>
-<p>See the detail of above query. Here is the condition which is specified as <code class="docutils literal"><span class="pre">filter</span></code> parameter:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>_id &lt;= 1
+<p>See the detail of above query. Here is the condition which is specified as <code class="docutils literal notranslate"><span class="pre">filter</span></code> parameter:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>_id &lt;= 1
 </pre></div>
 </div>
-<p>In this case, this query returns the records which meets the condition that the value of <code class="docutils literal"><span class="pre">_id</span></code> is equal to or less than 1.</p>
-<p>Moreover, you can use <code class="docutils literal"><span class="pre">&amp;&amp;</span></code> for AND search, <code class="docutils literal"><span class="pre">||</span></code> for OR search.</p>
+<p>In this case, this query returns the records which meets the condition that the value of <code class="docutils literal notranslate"><span class="pre">_id</span></code> is equal to or less than 1.</p>
+<p>Moreover, you can use <code class="docutils literal notranslate"><span class="pre">&amp;&amp;</span></code> for AND search, <code class="docutils literal notranslate"><span class="pre">||</span></code> for OR search.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --filter &quot;_id &gt;= 4 &amp;&amp; _id &lt;= 6&quot; --output_columns _id,_key
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Site --filter &quot;_id &gt;= 4 &amp;&amp; _id &lt;= 6&quot; --output_columns _id,_key
 # [
 #   [
 #     0,
@@ -198,14 +190,14 @@ select --table Site --filter &quot;_id &lt;= 2 || _id &gt;= 7&quot; --output_col
 # ]
 </pre></div>
 </div>
-<p>If you specify <code class="docutils literal"><span class="pre">query</span></code> parameter and <code class="docutils literal"><span class="pre">filter</span></code> parameter at the same time, you can get the records which meets both of the condition as a result.</p>
+<p>If you specify <code class="docutils literal notranslate"><span class="pre">query</span></code> parameter and <code class="docutils literal notranslate"><span class="pre">filter</span></code> parameter at the same time, you can get the records which meets both of the condition as a result.</p>
 </div>
 <div class="section" id="sort-by-using-scorer">
-<h2>4.4.2. Sort by using <code class="docutils literal"><span class="pre">scorer</span></code><a class="headerlink" href="#sort-by-using-scorer" title="Permalink to this headline">¶</a></h2>
-<p><code class="docutils literal"><span class="pre">select</span></code> command accepts <code class="docutils literal"><span class="pre">scorer</span></code> parameter which is used to process each record of full-text search results.</p>
-<p>This parameter accepts the conditions which is specified by syntax like JavaScript as same as <code class="docutils literal"><span class="pre">filter</span></code> parameter.</p>
+<h2>4.4.2. Sort by using <code class="docutils literal notranslate"><span class="pre">scorer</span></code><a class="headerlink" href="#sort-by-using-scorer" title="Permalink to this headline">¶</a></h2>
+<p><code class="docutils literal notranslate"><span class="pre">select</span></code> command accepts <code class="docutils literal notranslate"><span class="pre">scorer</span></code> parameter which is used to process each record of full-text search results.</p>
+<p>This parameter accepts the conditions which is specified by syntax like JavaScript as same as <code class="docutils literal notranslate"><span class="pre">filter</span></code> parameter.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --filter &quot;true&quot; --scorer &quot;_score = rand()&quot; --output_columns _id,_key,_score --sort_keys _score
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Site --filter &quot;true&quot; --scorer &quot;_score = rand()&quot; --output_columns _id,_key,_score --sort_keys _score
 # [
 #   [
 #     0,
@@ -355,15 +347,15 @@ select --table Site --filter &quot;true&quot; --scorer &quot;_score = rand()&quo
 # ]
 </pre></div>
 </div>
-<p>'_score' is one of a pseudo column. The score of full-text search is assigned to it.
-See <a class="reference internal" href="../reference/columns/pseudo.html"><span class="doc">Pseudo column</span></a> about '_score' column.</p>
-<p>In the above query, the condition of <code class="docutils literal"><span class="pre">scorer</span></code> parameter is:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>_score = rand()
+<p>‘_score’ is one of a pseudo column. The score of full-text search is assigned to it.
+See <a class="reference internal" href="../reference/columns/pseudo.html"><span class="doc">Pseudo column</span></a> about ‘_score’ column.</p>
+<p>In the above query, the condition of <code class="docutils literal notranslate"><span class="pre">scorer</span></code> parameter is:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>_score = rand()
 </pre></div>
 </div>
 <p>In this case, the score of full-text search is overwritten by the value of rand() function.</p>
-<p>The condition of <code class="docutils literal"><span class="pre">sort_keys</span></code> parameter is:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>_score
+<p>The condition of <code class="docutils literal notranslate"><span class="pre">sort_keys</span></code> parameter is:</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>_score
 </pre></div>
 </div>
 <p>This means that sorting the search result by ascending order.</p>
@@ -372,18 +364,18 @@ See <a class="reference internal" href="../reference/columns/pseudo.html"><span
 <div class="section" id="narrow-down-sort-by-using-location-information">
 <h2>4.4.3. Narrow down &amp; sort by using location information<a class="headerlink" href="#narrow-down-sort-by-using-location-information" title="Permalink to this headline">¶</a></h2>
 <p>Groonga supports to store location information (Longitude &amp; Latitude) and not only narrow down but also sort by using it.</p>
-<p>Groonga supports two kind of column types to store location information. One is <code class="docutils literal"><span class="pre">TokyoGeoPoint</span></code>, the other is <code class="docutils literal"><span class="pre">WGS84GeoPoint</span></code>. <code class="docutils literal"><span class="pre">TokyoGeoPoint</span></code> is used for Japan geodetic system. <code class="docutils literal"><span class="pre">WGS84GeoPoint</span></code> is used for world geodetic system.</p>
+<p>Groonga supports two kind of column types to store location information. One is <code class="docutils literal notranslate"><span class="pre">TokyoGeoPoint</span></code>, the other is <code class="docutils literal notranslate"><span class="pre">WGS84GeoPoint</span></code>. <code class="docutils literal notranslate"><span class="pre">TokyoGeoPoint</span></code> is used for Japan geodetic system. <code class="docutils literal notranslate"><span class="pre">WGS84GeoPoint</span></code> is used for world geodetic system.</p>
 <p>Specify longitude and latitude as follows:</p>
 <ul class="simple">
-<li>&quot;[latitude in milliseconds]x[longitude in milliseconds]&quot;（e.g.: &quot;128452975x503157902&quot;）</li>
-<li>&quot;[latitude in milliseconds],[longitude in milliseconds]&quot;（e.g.: &quot;128452975,503157902&quot;）</li>
-<li>&quot;[latitude in degrees]x[longitude in degrees]&quot;（e.g.: &quot;35.6813819x139.7660839&quot;）</li>
-<li>&quot;[latitude in degrees],[longitude in degrees]&quot;（e.g.: &quot;35.6813819,139.7660839&quot;）</li>
+<li><p>“[latitude in milliseconds]x[longitude in milliseconds]”（e.g.: “128452975x503157902”）</p></li>
+<li><p>“[latitude in milliseconds],[longitude in milliseconds]”（e.g.: “128452975,503157902”）</p></li>
+<li><p>“[latitude in degrees]x[longitude in degrees]”（e.g.: “35.6813819x139.7660839”）</p></li>
+<li><p>“[latitude in degrees],[longitude in degrees]”（e.g.: “35.6813819,139.7660839”）</p></li>
 </ul>
-<p>Let's store two location information about station in Japan by WGS. One is Tokyo station, the other is Shinjyuku station. Both of them are station in Japan. The latitude of Tokyo station is 35 degrees 40 minutes 52.975 seconds, the longitude of Tokyo station is 139 degrees 45 minutes 57.902 seconds. The latitude of Shinjyuku station is  35 degrees 41 minutes  27.316 seconds, the longitude of Shinjyuku station is 139 degrees 42 minutes 0.929 seconds. Thus, location information in milliseconds are &quot;128452975x503157902&quot; and &quot;128487316x502920929&quot; respectively. location information in degrees are  &quot;35.6813819x139.7660839&quot; and &quot;35.6909211x139.7002581&quot; respectively.</p>
-<p>Let's register location information in milliseconds.</p>
+<p>Let’s store two location information about station in Japan by WGS. One is Tokyo station, the other is Shinjyuku station. Both of them are station in Japan. The latitude of Tokyo station is 35 degrees 40 minutes 52.975 seconds, the longitude of Tokyo station is 139 degrees 45 minutes 57.902 seconds. The latitude of Shinjyuku station is  35 degrees 41 minutes  27.316 seconds, the longitude of Shinjyuku station is 139 degrees 42 minutes 0.929 seconds. Thus, location information in milliseconds are “128452975x503157902” and “128487316x502920929” respectively. location information in degrees are  “35.6813819x139.7660839” and “35.6909211x139.7002581” respectively.</p>
+<p>Let’s register location information in milliseconds.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>column_create --table Site --name location --type WGS84GeoPoint
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>column_create --table Site --name location --type WGS84GeoPoint
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 load --table Site
 [
@@ -426,10 +418,10 @@ select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,loc
 # ]
 </pre></div>
 </div>
-<p>Then assign the value of geo distance which is calculated by <a class="reference internal" href="../reference/functions/geo_distance.html"><span class="doc">geo_distance</span></a> function to <code class="docutils literal"><span class="pre">scorer</span></code> parameter.</p>
-<p>Let's show geo distance from Akihabara station in Japan. In world geodetic system, the latitude of Akihabara station is  35 degrees 41 minutes 55.259 seconds, the longitude of Akihabara station is 139 degrees 46 minutes 27.188 seconds. Specify &quot;128515259x503187188&quot; for geo_distance function.</p>
+<p>Then assign the value of geo distance which is calculated by <a class="reference internal" href="../reference/functions/geo_distance.html"><span class="doc">geo_distance</span></a> function to <code class="docutils literal notranslate"><span class="pre">scorer</span></code> parameter.</p>
+<p>Let’s show geo distance from Akihabara station in Japan. In world geodetic system, the latitude of Akihabara station is  35 degrees 41 minutes 55.259 seconds, the longitude of Akihabara station is 139 degrees 46 minutes 27.188 seconds. Specify “128515259x503187188” for geo_distance function.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,location,_score --scorer &#39;_score = geo_distance(location, &quot;128515259x503187188&quot;)&#39;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,location,_score --scorer &#39;_score = geo_distance(location, &quot;128515259x503187188&quot;)&#39;
 # [
 #   [
 #     0,
@@ -471,9 +463,9 @@ select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,loc
 </pre></div>
 </div>
 <p>As you can see, the geo distance between Tokyo station and Akihabara station is 2054 meters, the geo distance between Akihabara station and Shinjyuku station is 6720 meters.</p>
-<p>The return value of geo_distance function is also used for sorting by specifying pseudo <code class="docutils literal"><span class="pre">_score</span></code> column to <code class="docutils literal"><span class="pre">sort_keys</span></code> parameter.</p>
+<p>The return value of geo_distance function is also used for sorting by specifying pseudo <code class="docutils literal notranslate"><span class="pre">_score</span></code> column to <code class="docutils literal notranslate"><span class="pre">sort_keys</span></code> parameter.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,location,_score --scorer &#39;_score = geo_distance(location, &quot;128515259x503187188&quot;)&#39; --sort_keys -_score
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,location,_score --scorer &#39;_score = geo_distance(location, &quot;128515259x503187188&quot;)&#39; --sort_keys -_score
 # [
 #   [
 #     0,
@@ -514,11 +506,11 @@ select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,loc
 # ]
 </pre></div>
 </div>
-<p>Groonga also supports to narrow down by &quot;a certain point within specified meters&quot;.</p>
-<p>In such a case, use <a class="reference internal" href="../reference/functions/geo_in_circle.html"><span class="doc">geo_in_circle</span></a> function in <code class="docutils literal"><span class="pre">filter</span></code> parameter.</p>
+<p>Groonga also supports to narrow down by “a certain point within specified meters”.</p>
+<p>In such a case, use <a class="reference internal" href="../reference/functions/geo_in_circle.html"><span class="doc">geo_in_circle</span></a> function in <code class="docutils literal notranslate"><span class="pre">filter</span></code> parameter.</p>
 <p>For example, search the records which exists within 5000 meters from Akihabara station.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Site --output_columns _key,location --filter &#39;geo_in_circle(location, &quot;128515259x503187188&quot;, 5000)&#39;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Site --output_columns _key,location --filter &#39;geo_in_circle(location, &quot;128515259x503187188&quot;, 5000)&#39;
 # [
 #   [
 #     0,
@@ -559,11 +551,11 @@ select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,loc
       </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.4. Various search conditions</a><ul>
 <li><a class="reference internal" href="#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><a class="reference internal" href="#sort-by-using-scorer">4.4.2. Sort by using <code class="docutils literal"><span class="pre">scorer</span></code></a></li>
+<li><a class="reference internal" href="#sort-by-using-scorer">4.4.2. Sort by using <code class="docutils literal notranslate"><span class="pre">scorer</span></code></a></li>
 <li><a class="reference internal" href="#narrow-down-sort-by-using-location-information">4.4.3. Narrow down &amp; sort by using location information</a></li>
 </ul>
 </li>
@@ -577,12 +569,12 @@ select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,loc
                         title="next chapter">4.5. Drilldown</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>
@@ -601,12 +593,12 @@ select --table Site --query &quot;_id:1 OR _id:2&quot; --output_columns _key,loc
         <li class="right" >
           <a href="data.html" title="4.3. Various data types"
              >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>