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

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/lexicon.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.9. Additional information about lexicon for full text search &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>4.9. Additional information about lexicon for full text search &#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.10. Let&#39;s create micro-blog" href="micro_blog.html" />
+    <link rel="next" title="4.10. Let’s create micro-blog" href="micro_blog.html" />
     <link rel="prev" title="4.8. Prefix search with patricia trie" href="patricia_trie.html" />
-  </head>
-  <body>
+  </head><body>
 <div class="header">
   <h1 class="title">
     <a id="top-link" href="../index.html">
@@ -53,12 +45,12 @@
           <a href="../genindex.html" title="General Index"
              accesskey="I">index</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="N">next</a> |</li>
         <li class="right" >
           <a href="patricia_trie.html" title="4.8. Prefix search with patricia trie"
              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>
@@ -86,15 +78,15 @@ For example, Groonga holds frequency of word, flags for stop word, importance of
                         title="previous chapter">4.8. Prefix search with patricia trie</a></p>
   <h4>Next topic</h4>
   <p class="topless"><a href="micro_blog.html"
-                        title="next chapter">4.10. Let's create micro-blog</a></p>
+                        title="next chapter">4.10. Let’s create micro-blog</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>
@@ -108,17 +100,17 @@ For example, Groonga holds frequency of word, flags for stop word, importance of
           <a href="../genindex.html" title="General Index"
              >index</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"
              >next</a> |</li>
         <li class="right" >
           <a href="patricia_trie.html" title="4.8. Prefix search with patricia trie"
              >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/match_columns.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.7. match_columns parameter &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>4.7. match_columns parameter &#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.8. Prefix search with patricia trie" href="patricia_trie.html" />
     <link rel="prev" title="4.6. Tag search and reverse resolution of reference relationships" href="index.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="index.html" title="4.6. Tag search and reverse resolution of reference relationships"
              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>
@@ -72,15 +64,15 @@
 <h1>4.7. match_columns parameter<a class="headerlink" href="#match-columns-parameter" title="Permalink to this headline">¶</a></h1>
 <div class="section" id="full-text-search-against-multiple-columns">
 <h2>4.7.1. Full-text search against multiple columns<a class="headerlink" href="#full-text-search-against-multiple-columns" title="Permalink to this headline">¶</a></h2>
-<p>Groonga supports full-text search against multiple columns. Let's consider blog site. Usually, blog site has a table which contains title column and content column. How do you search the blog entry which contains specified keywords in title or content?</p>
+<p>Groonga supports full-text search against multiple columns. Let’s consider blog site. Usually, blog site has a table which contains title column and content column. How do you search the blog entry which contains specified keywords in title or content?</p>
 <p>In such a case, there are two ways to create indexes. One way is creating column index against each column. The other way is creating one column index against multiple columns. Either way, Groonga supports similar full-text search syntax.</p>
 <div class="section" id="creating-column-index-against-each-column">
 <h3>4.7.1.1. Creating column index against each column<a class="headerlink" href="#creating-column-index-against-each-column" title="Permalink to this headline">¶</a></h3>
 <p>Here is the example which create column index against each column.</p>
-<p>First, create <code class="docutils literal"><span class="pre">Blog1</span></code> table, add <code class="docutils literal"><span class="pre">title</span></code> column which stores title string, <code class="docutils literal"><span class="pre">message</span></code> column which stores content of blog entry.</p>
-<p>Then create <code class="docutils literal"><span class="pre">IndexBlog1</span></code> table for column indexes, add <code class="docutils literal"><span class="pre">index_title</span></code> column for <code class="docutils literal"><span class="pre">title</span></code> column, <code class="docutils literal"><span class="pre">index_message</span></code> column for <code class="docutils literal"><span class="pre">message</span></code> column.</p>
+<p>First, create <code class="docutils literal notranslate"><span class="pre">Blog1</span></code> table, add <code class="docutils literal notranslate"><span class="pre">title</span></code> column which stores title string, <code class="docutils literal notranslate"><span class="pre">message</span></code> column which stores content of blog entry.</p>
+<p>Then create <code class="docutils literal notranslate"><span class="pre">IndexBlog1</span></code> table for column indexes, add <code class="docutils literal notranslate"><span class="pre">index_title</span></code> column for <code class="docutils literal notranslate"><span class="pre">title</span></code> column, <code class="docutils literal notranslate"><span class="pre">index_message</span></code> column for <code class="docutils literal notranslate"><span class="pre">message</span></code> column.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create --name Blog1 --flags TABLE_HASH_KEY --key_type ShortText
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create --name Blog1 --flags TABLE_HASH_KEY --key_type ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 column_create --table Blog1 --name title --flags COLUMN_SCALAR --type ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
@@ -101,11 +93,11 @@ load --table Blog1
 # [[0, 1337566253.89858, 0.000355720520019531], 3]
 </pre></div>
 </div>
-<p><code class="docutils literal"><span class="pre">match_columns</span></code> option of <code class="docutils literal"><span class="pre">select</span></code> command accepts multiple columns as search target.
-Specify query string to <code class="docutils literal"><span class="pre">query</span></code> option. Then you can do full-text search title and content of blog entries.</p>
-<p>Let's try to search blog entries.</p>
+<p><code class="docutils literal notranslate"><span class="pre">match_columns</span></code> option of <code class="docutils literal notranslate"><span class="pre">select</span></code> command accepts multiple columns as search target.
+Specify query string to <code class="docutils literal notranslate"><span class="pre">query</span></code> option. Then you can do full-text search title and content of blog entries.</p>
+<p>Let’s try to search blog entries.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Blog1 --match_columns title||message --query groonga
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Blog1 --match_columns title||message --query groonga
 # [
 #   [
 #     0,
@@ -249,7 +241,7 @@ select --table Blog1 --match_columns title --query message
 <p>The difference for previous example is only one column index exists. Thus, There is one common column index against title and message column.</p>
 <p>Even though same column index is used, Groonga supports to search against title column only, message column only and title or message column.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create --name Blog2 --flags TABLE_HASH_KEY --key_type ShortText
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create --name Blog2 --flags TABLE_HASH_KEY --key_type ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 column_create --table Blog2 --name title --flags COLUMN_SCALAR --type ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
@@ -268,9 +260,9 @@ load --table Blog2
 # [[0, 1337566253.89858, 0.000355720520019531], 3]
 </pre></div>
 </div>
-<p>Let's search same query in previous section. You can get same search results.</p>
+<p>Let’s search same query in previous section. You can get same search results.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Blog2 --match_columns title||message --query groonga
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Blog2 --match_columns title||message --query groonga
 # [
 #   [
 #     0,
@@ -408,12 +400,12 @@ select --table Blog2 --match_columns title --query message
 </pre></div>
 </div>
 <div class="admonition note">
-<p class="first admonition-title">Note</p>
-<p>There may be a question that &quot;which is the better solution for indexing.&quot;
+<p class="admonition-title">Note</p>
+<p>There may be a question that “which is the better solution for indexing.”
 It depends on the case.</p>
-<ul class="last simple">
-<li>Indexes for each column - The update performance tends to be better than multiple colum index because there is enough buffer for updating. On the other hand, the efficiency of disk usage is not so good.</li>
-<li>Indexes for multiple column - It saves disk usage because it shares common buffer. On the other hand, the update performance is not so good.</li>
+<ul class="simple">
+<li><p>Indexes for each column - The update performance tends to be better than multiple colum index because there is enough buffer for updating. On the other hand, the efficiency of disk usage is not so good.</p></li>
+<li><p>Indexes for multiple column - It saves disk usage because it shares common buffer. On the other hand, the update performance is not so good.</p></li>
 </ul>
 </div>
 </div>
@@ -424,7 +416,7 @@ It depends on the case.</p>
 <p>In this section, you learn how to use specific index column efficiently.</p>
 <p>Here is the concrete example about specific index name.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create Entries TABLE_HASH_KEY ShortText
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create Entries TABLE_HASH_KEY ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 column_create Entries title COLUMN_SCALAR ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
@@ -452,14 +444,14 @@ column_create Terms entries_whole COLUMN_INDEX|WITH_POSITION|WITH_SECTION Entrie
 And the terms table has index columns for title and body to entries table.</p>
 <p>There are three index columns in terms table.</p>
 <ul class="simple">
-<li>entries_title: index column for title</li>
-<li>entries_body: index column for body</li>
-<li>entries_whole: index column for title and body</li>
+<li><p>entries_title: index column for title</p></li>
+<li><p>entries_body: index column for body</p></li>
+<li><p>entries_whole: index column for title and body</p></li>
 </ul>
 <p>If you specify index column which is related to specific data column, related data column is searched with that index implicitly.</p>
-<p>For example, if you want to search title or body only, specify <code class="docutils literal"><span class="pre">Terms.entries_title</span></code> or <code class="docutils literal"><span class="pre">Terms.entries_body</span></code> index column.</p>
+<p>For example, if you want to search title or body only, specify <code class="docutils literal notranslate"><span class="pre">Terms.entries_title</span></code> or <code class="docutils literal notranslate"><span class="pre">Terms.entries_body</span></code> index column.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Entries --output_columns title --match_columns Terms.entries_title --query &quot;Groonga&quot;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Entries --output_columns title --match_columns Terms.entries_title --query &quot;Groonga&quot;
 # [
 #   [
 #     0,
@@ -491,9 +483,9 @@ And the terms table has index columns for title and body to entries table.</p>
 # ]
 </pre></div>
 </div>
-<p>This example uses <code class="docutils literal"><span class="pre">Terms.entries_title</span></code> as index, then search &quot;Groonga&quot; against title data column.</p>
+<p>This example uses <code class="docutils literal notranslate"><span class="pre">Terms.entries_title</span></code> as index, then search “Groonga” against title data column.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Entries --output_columns body --match_columns Terms.entries_body --query &quot;Groonga&quot;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Entries --output_columns body --match_columns Terms.entries_body --query &quot;Groonga&quot;
 # [
 #   [
 #     0,
@@ -519,11 +511,11 @@ And the terms table has index columns for title and body to entries table.</p>
 # ]
 </pre></div>
 </div>
-<p>This example uses <code class="docutils literal"><span class="pre">Terms.entries_body</span></code> as index, then search &quot;Groonga&quot; against body data column.</p>
-<p>If you specify multiple index column which is related to specific data columns, you can also specify data column name as suffix. It means that &quot;Use specific index and search specific data column explicitly&quot;.</p>
-<p>For example, if you want to search title or body only with <code class="docutils literal"><span class="pre">entries_whole</span></code> index, specify <code class="docutils literal"><span class="pre">Terms.entries_whole.title</span></code> or <code class="docutils literal"><span class="pre">Terms.entries_whole.body</span></code>. It uses <code class="docutils literal"><span class="pre">Terms.entries_whole</span></code> index and search <code class="docutils literal"><span class="pre">title</span></code> column or <code class="docutils literal"><span class="pre">body</span></code> column explicitly.</p>
+<p>This example uses <code class="docutils literal notranslate"><span class="pre">Terms.entries_body</span></code> as index, then search “Groonga” against body data column.</p>
+<p>If you specify multiple index column which is related to specific data columns, you can also specify data column name as suffix. It means that “Use specific index and search specific data column explicitly”.</p>
+<p>For example, if you want to search title or body only with <code class="docutils literal notranslate"><span class="pre">entries_whole</span></code> index, specify <code class="docutils literal notranslate"><span class="pre">Terms.entries_whole.title</span></code> or <code class="docutils literal notranslate"><span class="pre">Terms.entries_whole.body</span></code>. It uses <code class="docutils literal notranslate"><span class="pre">Terms.entries_whole</span></code> index and search <code class="docutils literal notranslate"><span class="pre">title</span></code> column or <code class="docutils literal notranslate"><span class="pre">body</span></code> column explicitly.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Entries --output_columns title --match_columns Terms.entries_whole.title --query &quot;Groonga&quot;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Entries --output_columns title --match_columns Terms.entries_whole.title --query &quot;Groonga&quot;
 # [
 #   [
 #     0,
@@ -555,9 +547,9 @@ And the terms table has index columns for title and body to entries table.</p>
 # ]
 </pre></div>
 </div>
-<p>This example uses <code class="docutils literal"><span class="pre">Terms.entries_whole</span></code> as index, then search &quot;Groonga&quot; against title data column.</p>
+<p>This example uses <code class="docutils literal notranslate"><span class="pre">Terms.entries_whole</span></code> as index, then search “Groonga” against title data column.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Entries --output_columns body --match_columns Terms.entries_whole.body --query &quot;Groonga&quot;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Entries --output_columns body --match_columns Terms.entries_whole.body --query &quot;Groonga&quot;
 # [
 #   [
 #     0,
@@ -583,7 +575,7 @@ And the terms table has index columns for title and body to entries table.</p>
 # ]
 </pre></div>
 </div>
-<p>This example uses <code class="docutils literal"><span class="pre">Terms.entries_whole</span></code> as index, then search &quot;Groonga&quot; against body data column.</p>
+<p>This example uses <code class="docutils literal notranslate"><span class="pre">Terms.entries_whole</span></code> as index, then search “Groonga” against body data column.</p>
 </div>
 <div class="section" id="nested-index-search-among-related-table-by-column-index">
 <span id="nested-index-search"></span><h2>4.7.3. Nested index search among related table by column index<a class="headerlink" href="#nested-index-search-among-related-table-by-column-index" title="Permalink to this headline">¶</a></h2>
@@ -599,7 +591,7 @@ you need to execute fulltext search for table of comment, then search the record
 <p>But, you can search the records by specifying the reference column index at once.</p>
 <p>Here is the sample schema.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create Comments TABLE_HASH_KEY UInt32
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create Comments TABLE_HASH_KEY UInt32
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 column_create Comments content COLUMN_SCALAR ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
@@ -621,7 +613,7 @@ column_create Comments article COLUMN_INDEX Articles comment
 </div>
 <p>Here is the sample data.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>load --table Comments
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>load --table Comments
 [
 {&quot;_key&quot;: 1, &quot;content&quot;: &quot;I&#39;m using Groonga too!&quot;},
 {&quot;_key&quot;: 2, &quot;content&quot;: &quot;I&#39;m using Groonga and Mroonga!&quot;},
@@ -639,14 +631,14 @@ load --table Articles
 </div>
 <p>You can write the query that search the records which contains specified keyword as a comment, then fetch the articles which refers to it.</p>
 <p>Query for searching the records described above:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select Articles --match_columns comment.content --query groonga --output_columns &quot;_id, _score, *&quot;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select Articles --match_columns comment.content --query groonga --output_columns &quot;_id, _score, *&quot;
 </pre></div>
 </div>
-<p>You need to concatenate comment column of Articles table and content column of Comments table with period( <code class="docutils literal"><span class="pre">.</span></code> ) as <code class="docutils literal"><span class="pre">--match_columns</span></code> arguments.</p>
+<p>You need to concatenate comment column of Articles table and content column of Comments table with period( <code class="docutils literal notranslate"><span class="pre">.</span></code> ) as <code class="docutils literal notranslate"><span class="pre">--match_columns</span></code> arguments.</p>
 <p>At first, this query execute fulltext search from content of Comments table, then fetch the records of Articles table which refers to already searched records of Comments table.
-(Because of this, if you comment out the query which creates index column <code class="docutils literal"><span class="pre">article</span></code> of Comments table, you can't get intended search results.)</p>
+(Because of this, if you comment out the query which creates index column <code class="docutils literal notranslate"><span class="pre">article</span></code> of Comments table, you can’t get intended search results.)</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select Articles --match_columns comment.content --query groonga --output_columns &quot;_id, _score, *&quot;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select Articles --match_columns comment.content --query groonga --output_columns &quot;_id, _score, *&quot;
 # [
 #   [
 #     0,
@@ -689,9 +681,9 @@ load --table Articles
 </div>
 <p>Now, you can search articles which contains specific keywords as a comment.</p>
 <p>The feature of nested index search is not limited to the relationship between two table only.</p>
-<p>Here is the sample schema similar to previous one. The difference is added table which express 'Reply' and relationship is extended to three tables.</p>
+<p>Here is the sample schema similar to previous one. The difference is added table which express ‘Reply’ and relationship is extended to three tables.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create Replies2 TABLE_HASH_KEY UInt32
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create Replies2 TABLE_HASH_KEY UInt32
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 column_create Replies2 content COLUMN_SCALAR ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
@@ -723,7 +715,7 @@ column_create Replies2 reply_to COLUMN_INDEX Comments2 comment
 </div>
 <p>Here is the sample data.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>load --table Replies2
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>load --table Replies2
 [
 {&quot;_key&quot;: 1, &quot;content&quot;: &quot;I&#39;m using Rroonga too!&quot;},
 {&quot;_key&quot;: 2, &quot;content&quot;: &quot;I&#39;m using Groonga and Mroonga and Rroonga!&quot;},
@@ -747,13 +739,13 @@ load --table Articles2
 </pre></div>
 </div>
 <p>Query for searching the records described above:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select Articles2 --match_columns comment.content --query mroonga --output_columns &quot;_id, _score, *&quot;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select Articles2 --match_columns comment.content --query mroonga --output_columns &quot;_id, _score, *&quot;
 select Articles2 --match_columns comment.comment.content --query mroonga --output_columns &quot;_id, _score, *&quot;
 </pre></div>
 </div>
-<p>The first query searches <code class="docutils literal"><span class="pre">mroonga</span></code> from <code class="docutils literal"><span class="pre">Comments2</span></code> table, the second one searches <code class="docutils literal"><span class="pre">mroonga</span></code> from <code class="docutils literal"><span class="pre">Replies2</span></code> and <code class="docutils literal"><span class="pre">Comments2</span></code> table by using reference column index.</p>
+<p>The first query searches <code class="docutils literal notranslate"><span class="pre">mroonga</span></code> from <code class="docutils literal notranslate"><span class="pre">Comments2</span></code> table, the second one searches <code class="docutils literal notranslate"><span class="pre">mroonga</span></code> from <code class="docutils literal notranslate"><span class="pre">Replies2</span></code> and <code class="docutils literal notranslate"><span class="pre">Comments2</span></code> table by using reference column index.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select Articles2 --match_columns comment.content --query mroonga --output_columns &quot;_id, _score, *&quot;
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select Articles2 --match_columns comment.content --query mroonga --output_columns &quot;_id, _score, *&quot;
 # [
 #   [
 #     0,
@@ -839,8 +831,8 @@ select Articles2 --match_columns comment.comment.content --query mroonga --outpu
 # ]
 </pre></div>
 </div>
-<p>As a result, the first query matches two article because of <code class="docutils literal"><span class="pre">Comments2</span></code> table has two records which contains <code class="docutils literal"><span class="pre">mroonga</span></code> as keyword.</p>
-<p>On the other hand, the second one matches one article only because of <code class="docutils literal"><span class="pre">Replies2</span></code> table has only one record which contains <code class="docutils literal"><span class="pre">mroonga</span></code> as keyword, and there is one record which contains same keyword and refers to the record in <code class="docutils literal"><span class="pre">Comments2</span></code> table.</p>
+<p>As a result, the first query matches two article because of <code class="docutils literal notranslate"><span class="pre">Comments2</span></code> table has two records which contains <code class="docutils literal notranslate"><span class="pre">mroonga</span></code> as keyword.</p>
+<p>On the other hand, the second one matches one article only because of <code class="docutils literal notranslate"><span class="pre">Replies2</span></code> table has only one record which contains <code class="docutils literal notranslate"><span class="pre">mroonga</span></code> as keyword, and there is one record which contains same keyword and refers to the record in <code class="docutils literal notranslate"><span class="pre">Comments2</span></code> table.</p>
 </div>
 <div class="section" id="indexes-with-weight">
 <h2>4.7.4. Indexes with Weight<a class="headerlink" href="#indexes-with-weight" title="Permalink to this headline">¶</a></h2>
@@ -854,7 +846,7 @@ select Articles2 --match_columns comment.comment.content --query mroonga --outpu
       </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.7. match_columns parameter</a><ul>
 <li><a class="reference internal" href="#full-text-search-against-multiple-columns">4.7.1. Full-text search against multiple columns</a><ul>
@@ -877,12 +869,12 @@ select Articles2 --match_columns comment.comment.content --query mroonga --outpu
                         title="next chapter">4.8. Prefix search with patricia trie</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>
@@ -901,12 +893,12 @@ select Articles2 --match_columns comment.comment.content --query mroonga --outpu
         <li class="right" >
           <a href="index.html" title="4.6. Tag search and reverse resolution of reference relationships"
              >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/micro_blog.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.10. Let&#39;s create micro-blog &#8212; Groonga v7.1.0-73-g6d02cfa documentation</title>
+    <meta charset="utf-8" />
+    <title>4.10. Let’s create micro-blog &#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.11. Query expansion" href="query_expansion.html" />
     <link rel="prev" title="4.9. Additional information about lexicon for full text search" href="lexicon.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="lexicon.html" title="4.9. Additional information about lexicon for full text search"
              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>
@@ -69,13 +61,13 @@
           <div class="body" role="main">
   <div class="section" id="let-s-create-micro-blog">
-<h1>4.10. Let's create micro-blog<a class="headerlink" href="#let-s-create-micro-blog" title="Permalink to this headline">¶</a></h1>
-<p>Let's create micro-blog with full text search by Groonga.
+<h1>4.10. Let’s create micro-blog<a class="headerlink" href="#let-s-create-micro-blog" title="Permalink to this headline">¶</a></h1>
+<p>Let’s create micro-blog with full text search by Groonga.
 Micro-blog is one of the broadcast medium in the forms of blog. It is mainly used to post small messages like a Twitter.</p>
 <div class="section" id="create-a-table">
 <h2>4.10.1. Create a table<a class="headerlink" href="#create-a-table" title="Permalink to this headline">¶</a></h2>
-<p>Let's create table.</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>table_create --name Users --flags TABLE_HASH_KEY --key_type ShortText
+<p>Let’s create table.</p>
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>table_create --name Users --flags TABLE_HASH_KEY --key_type ShortText
 table_create --name Comments --flags TABLE_HASH_KEY --key_type ShortText
 table_create --name HashTags --flags TABLE_HASH_KEY --key_type ShortText
 table_create --name Bigram --flags TABLE_PAT_KEY --key_type ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
@@ -111,91 +103,91 @@ column_create --table GeoIndex --name comments_location --type Comments --flags
 <h3>4.10.1.1. Users table<a class="headerlink" href="#users-table" title="Permalink to this headline">¶</a></h3>
 <p>This is the table which stores user information.
 It stores name of user, profile, list of follower and so on.</p>
-<dl class="docutils">
-<dt><code class="docutils literal"><span class="pre">_key</span></code></dt>
-<dd>User ID</dd>
-<dt><code class="docutils literal"><span class="pre">name</span></code></dt>
-<dd>User name</dd>
-<dt><code class="docutils literal"><span class="pre">follower</span></code></dt>
-<dd>List of following users</dd>
-<dt><code class="docutils literal"><span class="pre">favorites</span></code></dt>
-<dd>List of favorite comments</dd>
-<dt><code class="docutils literal"><span class="pre">location</span></code></dt>
-<dd>Current location of user (geolocation)</dd>
-<dt><code class="docutils literal"><span class="pre">location_str</span></code></dt>
-<dd>Current location of user (string)</dd>
-<dt><code class="docutils literal"><span class="pre">description</span></code></dt>
-<dd>User profile</dd>
-<dt><code class="docutils literal"><span class="pre">followee</span></code></dt>
-<dd>Indexes for <code class="docutils literal"><span class="pre">follower</span></code> column in <code class="docutils literal"><span class="pre">Users</span></code> table.
-With this indexes, you can search users who follows the person.</dd>
+<dl class="simple">
+<dt><code class="docutils literal notranslate"><span class="pre">_key</span></code></dt><dd><p>User ID</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">name</span></code></dt><dd><p>User name</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">follower</span></code></dt><dd><p>List of following users</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">favorites</span></code></dt><dd><p>List of favorite comments</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">location</span></code></dt><dd><p>Current location of user (geolocation)</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">location_str</span></code></dt><dd><p>Current location of user (string)</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">description</span></code></dt><dd><p>User profile</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">followee</span></code></dt><dd><p>Indexes for <code class="docutils literal notranslate"><span class="pre">follower</span></code> column in <code class="docutils literal notranslate"><span class="pre">Users</span></code> table.
+With this indexes, you can search users who follows the person.</p>
+</dd>
 </dl>
 </div>
 <div class="section" id="comments-table">
 <h3>4.10.1.2. Comments table<a class="headerlink" href="#comments-table" title="Permalink to this headline">¶</a></h3>
 <p>This is the table which stores comments and its metadata.
 It stores content of comment, posted date, comment which reply to, and so on.</p>
-<dl class="docutils">
-<dt><code class="docutils literal"><span class="pre">_key</span></code></dt>
-<dd>Comment ID</dd>
-<dt><code class="docutils literal"><span class="pre">comment</span></code></dt>
-<dd>Content of comment</dd>
-<dt><code class="docutils literal"><span class="pre">last_modified</span></code></dt>
-<dd>Posted date</dd>
-<dt><code class="docutils literal"><span class="pre">replied_to</span></code></dt>
-<dd>Comment which you reply to someone</dd>
-<dt><code class="docutils literal"><span class="pre">replied_users</span></code></dt>
-<dd>List of users who you reply to</dd>
-<dt><code class="docutils literal"><span class="pre">hash_tags</span></code></dt>
-<dd>List of hash tags about comment</dd>
-<dt><code class="docutils literal"><span class="pre">location</span></code></dt>
-<dd>Posted place (for geolocation)</dd>
-<dt><code class="docutils literal"><span class="pre">posted_by</span></code></dt>
-<dd>Person who write comment</dd>
-<dt><code class="docutils literal"><span class="pre">favorited_by</span></code></dt>
-<dd>Indexes for <code class="docutils literal"><span class="pre">favorites</span></code> column in <code class="docutils literal"><span class="pre">Users</span></code> table.
-With this indexes, you can search the person who mark comment as favorite one.</dd>
+<dl class="simple">
+<dt><code class="docutils literal notranslate"><span class="pre">_key</span></code></dt><dd><p>Comment ID</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">comment</span></code></dt><dd><p>Content of comment</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">last_modified</span></code></dt><dd><p>Posted date</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">replied_to</span></code></dt><dd><p>Comment which you reply to someone</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">replied_users</span></code></dt><dd><p>List of users who you reply to</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">hash_tags</span></code></dt><dd><p>List of hash tags about comment</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">location</span></code></dt><dd><p>Posted place (for geolocation)</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">posted_by</span></code></dt><dd><p>Person who write comment</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">favorited_by</span></code></dt><dd><p>Indexes for <code class="docutils literal notranslate"><span class="pre">favorites</span></code> column in <code class="docutils literal notranslate"><span class="pre">Users</span></code> table.
+With this indexes, you can search the person who mark comment as favorite one.</p>
+</dd>
 </dl>
 </div>
 <div class="section" id="hashtags-table">
 <h3>4.10.1.3. HashTags table<a class="headerlink" href="#hashtags-table" title="Permalink to this headline">¶</a></h3>
 <p>This is the table which stores hash tags for comments.</p>
-<dl class="docutils">
-<dt><code class="docutils literal"><span class="pre">_key</span></code></dt>
-<dd>Hash tag</dd>
-<dt><code class="docutils literal"><span class="pre">hash_index</span></code></dt>
-<dd>Indexes for <code class="docutils literal"><span class="pre">Comments.hash_tags</span></code>.
-With this indexes, you can search list of comments with specified hash tags.</dd>
+<dl class="simple">
+<dt><code class="docutils literal notranslate"><span class="pre">_key</span></code></dt><dd><p>Hash tag</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">hash_index</span></code></dt><dd><p>Indexes for <code class="docutils literal notranslate"><span class="pre">Comments.hash_tags</span></code>.
+With this indexes, you can search list of comments with specified hash tags.</p>
+</dd>
 </dl>
 </div>
 <div class="section" id="bigram-table">
 <h3>4.10.1.4. Bigram table<a class="headerlink" href="#bigram-table" title="Permalink to this headline">¶</a></h3>
 <p>This is the table which stores indexes for full text search by user information or comments.</p>
-<dl class="docutils">
-<dt><code class="docutils literal"><span class="pre">_key</span></code></dt>
-<dd>Word</dd>
-<dt><code class="docutils literal"><span class="pre">users_index</span></code></dt>
-<dd>Indexes of user information.
-This column contains indexes of user name (<code class="docutils literal"><span class="pre">Users.name</span></code>), current location (<code class="docutils literal"><span class="pre">Users.location_str</span></code>), profile (<code class="docutils literal"><span class="pre">Users.description</span></code>).</dd>
-<dt><code class="docutils literal"><span class="pre">comment_index</span></code></dt>
-<dd>Indexes about content of comments (<code class="docutils literal"><span class="pre">Comments.comment</span></code>).</dd>
+<dl class="simple">
+<dt><code class="docutils literal notranslate"><span class="pre">_key</span></code></dt><dd><p>Word</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">users_index</span></code></dt><dd><p>Indexes of user information.
+This column contains indexes of user name (<code class="docutils literal notranslate"><span class="pre">Users.name</span></code>), current location (<code class="docutils literal notranslate"><span class="pre">Users.location_str</span></code>), profile (<code class="docutils literal notranslate"><span class="pre">Users.description</span></code>).</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">comment_index</span></code></dt><dd><p>Indexes about content of comments (<code class="docutils literal notranslate"><span class="pre">Comments.comment</span></code>).</p>
+</dd>
 </dl>
 </div>
 <div class="section" id="geoindex-table">
 <h3>4.10.1.5. GeoIndex table<a class="headerlink" href="#geoindex-table" title="Permalink to this headline">¶</a></h3>
 <p>This is the table which stores indexes of location column to search geo location effectively.</p>
-<dl class="docutils">
-<dt><code class="docutils literal"><span class="pre">users_location</span></code></dt>
-<dd>Indexes of location column for Users table</dd>
-<dt><code class="docutils literal"><span class="pre">comments_location</span></code></dt>
-<dd>Indexes of location column for Comments table</dd>
+<dl class="simple">
+<dt><code class="docutils literal notranslate"><span class="pre">users_location</span></code></dt><dd><p>Indexes of location column for Users table</p>
+</dd>
+<dt><code class="docutils literal notranslate"><span class="pre">comments_location</span></code></dt><dd><p>Indexes of location column for Comments table</p>
+</dd>
 </dl>
 </div>
 </div>
 <div class="section" id="loading-data">
 <h2>4.10.2. Loading data<a class="headerlink" href="#loading-data" title="Permalink to this headline">¶</a></h2>
 <p>Then, load example data.</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>load --table Users
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>load --table Users
 [
   {
     &quot;_key&quot;: &quot;alice&quot;,
@@ -290,25 +282,25 @@ load --table Comments
 ]
 </pre></div>
 </div>
-<p><code class="docutils literal"><span class="pre">follower</span></code> column and <code class="docutils literal"><span class="pre">favorites</span></code> column in <code class="docutils literal"><span class="pre">Users</span></code> table and <code class="docutils literal"><span class="pre">replied_users</span></code> column in <code class="docutils literal"><span class="pre">Comments</span></code> table are vector column, so specify the value as an array.</p>
-<p><code class="docutils literal"><span class="pre">location</span></code> column in <code class="docutils literal"><span class="pre">Users</span></code> table, <code class="docutils literal"><span class="pre">location</span></code> column in <code class="docutils literal"><span class="pre">Comments</span></code> table use GeoPoint type. This type accepts &quot;[latitude]x[longitude]&quot;.</p>
-<p><code class="docutils literal"><span class="pre">last_modified</span></code> column in <code class="docutils literal"><span class="pre">Comments</span></code> table use Time type.</p>
+<p><code class="docutils literal notranslate"><span class="pre">follower</span></code> column and <code class="docutils literal notranslate"><span class="pre">favorites</span></code> column in <code class="docutils literal notranslate"><span class="pre">Users</span></code> table and <code class="docutils literal notranslate"><span class="pre">replied_users</span></code> column in <code class="docutils literal notranslate"><span class="pre">Comments</span></code> table are vector column, so specify the value as an array.</p>
+<p><code class="docutils literal notranslate"><span class="pre">location</span></code> column in <code class="docutils literal notranslate"><span class="pre">Users</span></code> table, <code class="docutils literal notranslate"><span class="pre">location</span></code> column in <code class="docutils literal notranslate"><span class="pre">Comments</span></code> table use GeoPoint type. This type accepts “[latitude]x[longitude]”.</p>
+<p><code class="docutils literal notranslate"><span class="pre">last_modified</span></code> column in <code class="docutils literal notranslate"><span class="pre">Comments</span></code> table use Time type.</p>
 <p>There are two way to specify the value.
 First, specify epoch (seconds since Jan, 1, 1970 AM 00:00:00) directly. In this case, you can specify micro seconds as fractional part.
 The value is converted from factional part to the time which is micro seconds based one when data is loaded.
-The second, specify the timestamp as string in following format: &quot;(YEAR)/(MONTH)/(DAY) (HOUR):(MINUTE):(SECOND)&quot;. In this way, the string is casted to proper micro seconds
+The second, specify the timestamp as string in following format: “(YEAR)/(MONTH)/(DAY) (HOUR):(MINUTE):(SECOND)”. In this way, the string is casted to proper micro seconds
 when data is loaded.</p>
 </div>
 <div class="section" id="search">
 <h2>4.10.3. Search<a class="headerlink" href="#search" title="Permalink to this headline">¶</a></h2>
-<p>Let's search micro-blog.</p>
+<p>Let’s search micro-blog.</p>
 <div class="section" id="search-users-by-keyword">
 <h3>4.10.3.1. Search users by keyword<a class="headerlink" href="#search-users-by-keyword" title="Permalink to this headline">¶</a></h3>
 <p>In this section, we search micro-blog against multiple column by keyword.
 See <a class="reference internal" href="match_columns.html"><span class="doc">match_columns parameter</span></a> to search multiple column at once.</p>
-<p>Let's search user from micro-blog's user name, location, description entries.</p>
+<p>Let’s search user from micro-blog’s user name, location, description entries.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Users --match_columns name,location_str,description --query &quot;New York&quot; --output_columns _key,name
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Users --match_columns name,location_str,description --query &quot;New York&quot; --output_columns _key,name
 # [
 #   [
 #     0,
@@ -339,7 +331,7 @@ See <a class="reference internal" href="match_columns.html"><span class="doc">ma
 # ]
 </pre></div>
 </div>
-<p>By using &quot;New York&quot; as searching keyword for user, &quot;Bob&quot; who lives in &quot;New York&quot; is listed in search result.</p>
+<p>By using “New York” as searching keyword for user, “Bob” who lives in “New York” is listed in search result.</p>
 </div>
 <div class="section" id="search-users-by-geolocation-data-geopoint">
 <h3>4.10.3.2. Search users by geolocation data (GeoPoint)<a class="headerlink" href="#search-users-by-geolocation-data-geopoint" title="Permalink to this headline">¶</a></h3>
@@ -347,7 +339,7 @@ See <a class="reference internal" href="match_columns.html"><span class="doc">ma
 See <a class="reference internal" href="search.html"><span class="doc">Various search conditions</span></a> about GeoPoint column.</p>
 <p>Following example searches users who live in within 20km from specified location.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Users --filter &#39;geo_in_circle(location,&quot;146710080x-266315480&quot;,20000)&#39; --output_columns _key,name
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Users --filter &#39;geo_in_circle(location,&quot;146710080x-266315480&quot;,20000)&#39; --output_columns _key,name
 # [
 #   [
 #     0,
@@ -382,14 +374,14 @@ See <a class="reference internal" href="search.html"><span class="doc">Various s
 # ]
 </pre></div>
 </div>
-<p>It shows that &quot;Bob&quot; and &quot;Charlie&quot; lives in within 20 km from station of &quot;Grand Central Terminal&quot;.</p>
+<p>It shows that “Bob” and “Charlie” lives in within 20 km from station of “Grand Central Terminal”.</p>
 </div>
 <div class="section" id="search-users-who-follows-specific-user">
 <h3>4.10.3.3. Search users who follows specific user<a class="headerlink" href="#search-users-who-follows-specific-user" title="Permalink to this headline">¶</a></h3>
 <p>In this section, we do reverse resolution of reference relationships which is described at <a class="reference internal" href="index.html"><span class="doc">Tag search and reverse resolution of reference relationships</span></a>.</p>
-<p>Following examples shows reverse resolution about <code class="docutils literal"><span class="pre">follower</span></code> column of <code class="docutils literal"><span class="pre">Users</span></code> table.</p>
+<p>Following examples shows reverse resolution about <code class="docutils literal notranslate"><span class="pre">follower</span></code> column of <code class="docutils literal notranslate"><span class="pre">Users</span></code> table.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Users --query follower:@bob --output_columns _key,name
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Users --query follower:@bob --output_columns _key,name
 # [
 #   [
 #     0,
@@ -424,7 +416,7 @@ See <a class="reference internal" href="search.html"><span class="doc">Various s
 # ]
 </pre></div>
 </div>
-<p>It shows that &quot;Alice&quot; and &quot;Charlie&quot; follows &quot;Bob&quot;.</p>
+<p>It shows that “Alice” and “Charlie” follows “Bob”.</p>
 </div>
 <div class="section" id="search-comments-by-using-the-value-of-geopoint-type">
 <h3>4.10.3.4. Search comments by using the value of GeoPoint type<a class="headerlink" href="#search-comments-by-using-the-value-of-geopoint-type" title="Permalink to this headline">¶</a></h3>
@@ -433,7 +425,7 @@ See <a class="reference internal" href="search.html"><span class="doc">Various s
 Following example shows how to drill down against search results.
 As a result, we get the value of count which is grouped by user, and hash tags respectively.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Comments --filter &#39;geo_in_circle(location,&quot;146867000x-266280000&quot;,20000)&#39; --output_columns posted_by.name,comment --drilldown hash_tags,posted_by
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Comments --filter &#39;geo_in_circle(location,&quot;146867000x-266280000&quot;,20000)&#39; --output_columns posted_by.name,comment --drilldown hash_tags,posted_by
 # [
 #   [
 #     0,
@@ -529,9 +521,9 @@ You know that search results contain 2 #groonga hash tags and one #travel hash t
 <div class="section" id="search-comments-by-keyword">
 <h3>4.10.3.5. Search comments by keyword<a class="headerlink" href="#search-comments-by-keyword" title="Permalink to this headline">¶</a></h3>
 <p>In this section, we search comments which contains specific keyword.
-And more, Let's calculate the value of <cite>_score</cite> which is described at <a class="reference internal" href="search.html"><span class="doc">Various search conditions</span></a>.</p>
+And more, Let’s calculate the value of <cite>_score</cite> which is described at <a class="reference internal" href="search.html"><span class="doc">Various search conditions</span></a>.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Comments --query comment:@Now --output_columns comment,_score
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Comments --query comment:@Now --output_columns comment,_score
 # [
 #   [
 #     0,
@@ -566,14 +558,14 @@ And more, Let's calculate the value of <cite>_score</cite> which is described at
 # ]
 </pre></div>
 </div>
-<p>By using 'Now' as a keyword, above query returns 2 comments. It also contains count of 'Now' as the value of <cite>_score</cite>.</p>
+<p>By using ‘Now’ as a keyword, above query returns 2 comments. It also contains count of ‘Now’ as the value of <cite>_score</cite>.</p>
 </div>
 <div class="section" id="search-comments-by-keyword-and-geolocation">
 <h3>4.10.3.6. Search comments by keyword and geolocation<a class="headerlink" href="#search-comments-by-keyword-and-geolocation" title="Permalink to this headline">¶</a></h3>
 <p>In this section, we search comments by specific keyword and geolocation.
-By using <cite>--query</cite> and <cite>--filter</cite> option, following query returns records which are matched to both conditions.</p>
+By using <cite>–query</cite> and <cite>–filter</cite> option, following query returns records which are matched to both conditions.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Comments --query comment:@New --filter &#39;geo_in_circle(location,&quot;146867000x-266280000&quot;,20000)&#39; --output_columns posted_by.name,comment --drilldown hash_tags,posted_by
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Comments --query comment:@New --filter &#39;geo_in_circle(location,&quot;146867000x-266280000&quot;,20000)&#39; --output_columns posted_by.name,comment --drilldown hash_tags,posted_by
 # [
 #   [
 #     0,
@@ -652,9 +644,9 @@ It also returns result of drilldown. There is 1 comment which is commented by Bo
 <div class="section" id="search-comments-by-hash-tags">
 <h3>4.10.3.7. Search comments by hash tags<a class="headerlink" href="#search-comments-by-hash-tags" title="Permalink to this headline">¶</a></h3>
 <p>In this section, we search comments which contains specific hash tags.
-Let's use reverse resolution of reference relationships.</p>
+Let’s use reverse resolution of reference relationships.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Comments --query hash_tags:@groonga --output_columns posted_by.name,comment --drilldown posted_by
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Comments --query hash_tags:@groonga --output_columns posted_by.name,comment --drilldown posted_by
 # [
 #   [
 #     0,
@@ -715,7 +707,7 @@ It also returns result of drilldown grouped by person who posted it. It shows th
 <h3>4.10.3.8. Search comments by user id<a class="headerlink" href="#search-comments-by-user-id" title="Permalink to this headline">¶</a></h3>
 <p>In this section, we search comments which are posted by specific user.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Comments --query posted_by:bob --output_columns comment --drilldown hash_tags
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Comments --query posted_by:bob --output_columns comment --drilldown hash_tags
 # [
 #   [
 #     0,
@@ -777,22 +769,22 @@ It also returns result of drilldown grouped by person who posted it. It shows th
 It also returns result of drilldown by hash tags. There are 2 comments which contains #groonga, and 1 comment which contains #travel as hash tag.</p>
 </div>
 <div class="section" id="search-user-s-favorite-comments">
-<h3>4.10.3.9. Search user's favorite comments<a class="headerlink" href="#search-user-s-favorite-comments" title="Permalink to this headline">¶</a></h3>
-<p>In this section, we search user's favorite comments.</p>
+<h3>4.10.3.9. Search user’s favorite comments<a class="headerlink" href="#search-user-s-favorite-comments" title="Permalink to this headline">¶</a></h3>
+<p>In this section, we search user’s favorite comments.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select --table Users --query _key:bob --output_columns favorites.posted_by,favorites.comment
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select --table Users --query _key:bob --output_columns favorites.posted_by,favorites.comment
 # [[0, 1337566253.89858, 0.000355720520019531], [[[0], []]]]
 </pre></div>
 </div>
-<p>Above query returns Bob's favorite comments.</p>
+<p>Above query returns Bob’s favorite comments.</p>
 </div>
 <div class="section" id="search-comments-by-posted-time">
 <h3>4.10.3.10. Search comments by posted time<a class="headerlink" href="#search-comments-by-posted-time" title="Permalink to this headline">¶</a></h3>
 <p>In this section, we search comments by posted time.
 See type of <cite>Time</cite> in <a class="reference internal" href="data.html"><span class="doc">Various data types</span></a>.</p>
-<p>Let's search comments that posted time are older than specified time.</p>
+<p>Let’s search comments that posted time are older than specified time.</p>
 <p>Execution example:</p>
-<div class="highlight-none"><div class="highlight"><pre><span></span>select Comments --filter &#39;last_modified&lt;=1268802000&#39; --output_columns posted_by.name,comment,last_modified --drilldown hash_tags,posted_by
+<div class="highlight-none notranslate"><div class="highlight"><pre><span></span>select Comments --filter &#39;last_modified&lt;=1268802000&#39; --output_columns posted_by.name,comment,last_modified --drilldown hash_tags,posted_by
 # [
 #   [
 #     0,
@@ -902,9 +894,9 @@ It also returns result of drilldown by posted person. There are 2 comments by Al
       </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.10. Let's create micro-blog</a><ul>
+<li><a class="reference internal" href="#">4.10. Let’s create micro-blog</a><ul>
 <li><a class="reference internal" href="#create-a-table">4.10.1. Create a table</a><ul>
 <li><a class="reference internal" href="#users-table">4.10.1.1. Users table</a></li>
 <li><a class="reference internal" href="#comments-table">4.10.1.2. Comments table</a></li>
@@ -923,7 +915,7 @@ It also returns result of drilldown by posted person. There are 2 comments by Al
 <li><a class="reference internal" href="#search-comments-by-keyword-and-geolocation">4.10.3.6. Search comments by keyword and geolocation</a></li>
 <li><a class="reference internal" href="#search-comments-by-hash-tags">4.10.3.7. Search comments by hash tags</a></li>
 <li><a class="reference internal" href="#search-comments-by-user-id">4.10.3.8. Search comments by user id</a></li>
-<li><a class="reference internal" href="#search-user-s-favorite-comments">4.10.3.9. Search user's favorite comments</a></li>
+<li><a class="reference internal" href="#search-user-s-favorite-comments">4.10.3.9. Search user’s favorite comments</a></li>
 <li><a class="reference internal" href="#search-comments-by-posted-time">4.10.3.10. Search comments by posted time</a></li>
 </ul>
 </li>
@@ -939,12 +931,12 @@ It also returns result of drilldown by posted person. There are 2 comments by Al
                         title="next chapter">4.11. Query expansion</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>
@@ -963,12 +955,12 @@ It also returns result of drilldown by posted person. There are 2 comments by Al
         <li class="right" >
           <a href="lexicon.html" title="4.9. Additional information about lexicon for full text search"
              >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>