rroonga 5.0.5-x64-mingw32 → 5.0.8-x64-mingw32

data/vendor/local/share/man/man1/groonga.1

@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "GROONGA" "1" "August 31, 2015" "5.0.7" "Groonga"
+.TH "GROONGA" "1" "September 28, 2015" "5.0.8" "Groonga"
 .SH NAME
 groonga \- Groonga documentation
 .
@@ -110,7 +110,7 @@ packages.groonga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/windows/groonga/groonga\-5.0.7\-x86.exe\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-5.0.8\-x86.exe\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -123,7 +123,7 @@ packages.goronga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/windows/groonga/groonga\-5.0.7\-x64.exe\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-5.0.8\-x64.exe\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -140,7 +140,7 @@ packages.groonga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/windows/groonga/groonga\-5.0.7\-x86.zip\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-5.0.8\-x86.zip\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -153,7 +153,7 @@ packages.groonga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/windows/groonga/groonga\-5.0.7\-x64.zip\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-5.0.8\-x64.zip\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -181,7 +181,7 @@ Download zipped source from packages.groonga.org:
 .INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fI\%http://packages.groonga.org/source/groonga/groonga\-5.0.7.zip\fP
+\fI\%http://packages.groonga.org/source/groonga/groonga\-5.0.8.zip\fP
 .UNINDENT
 .UNINDENT
 .UNINDENT
@@ -194,7 +194,7 @@ Move to the Groonga\(aqs source folder:
 .sp
 .nf
 .ft C
-> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-5.0.7
+> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-5.0.8
 .ft P
 .fi
 .UNINDENT
@@ -208,7 +208,7 @@ parameter instead:
 .sp
 .nf
 .ft C
-groonga\-5.0.7> cmake . \-G "Visual Studio 12 2013 Win64" \-DCMAKE_INSTALL_PREFIX=C:\eGroonga
+groonga\-5.0.8> cmake . \-G "Visual Studio 12 2013 Win64" \-DCMAKE_INSTALL_PREFIX=C:\eGroonga
 .ft P
 .fi
 .UNINDENT
@@ -220,7 +220,7 @@ Build:
 .sp
 .nf
 .ft C
-groonga\-5.0.7> cmake \-\-build . \-\-config Release
+groonga\-5.0.8> cmake \-\-build . \-\-config Release
 .ft P
 .fi
 .UNINDENT
@@ -232,7 +232,7 @@ Install:
 .sp
 .nf
 .ft C
-groonga\-5.0.7> cmake \-\-build . \-\-config Release \-\-target Install
+groonga\-5.0.8> cmake \-\-build . \-\-config Release \-\-target Install
 .ft P
 .fi
 .UNINDENT
@@ -294,9 +294,9 @@ Download source:
 .sp
 .nf
 .ft C
-% curl \-O http://packages.groonga.org/source/groonga/groonga\-5.0.7.tar.gz
-% tar xvzf groonga\-5.0.7.tar.gz
-% cd groonga\-5.0.7
+% curl \-O http://packages.groonga.org/source/groonga/groonga\-5.0.8.tar.gz
+% tar xvzf groonga\-5.0.8.tar.gz
+% cd groonga\-5.0.8
 .ft P
 .fi
 .UNINDENT
@@ -592,9 +592,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.0.7.tar.gz
-% tar xvzf groonga\-5.0.7.tar.gz
-% cd groonga\-5.0.7
+% wget http://packages.groonga.org/source/groonga/groonga\-5.0.8.tar.gz
+% tar xvzf groonga\-5.0.8.tar.gz
+% cd groonga\-5.0.8
 .ft P
 .fi
 .UNINDENT
@@ -801,9 +801,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.0.7.tar.gz
-% tar xvzf groonga\-5.0.7.tar.gz
-% cd groonga\-5.0.7
+% wget http://packages.groonga.org/source/groonga/groonga\-5.0.8.tar.gz
+% tar xvzf groonga\-5.0.8.tar.gz
+% cd groonga\-5.0.8
 .ft P
 .fi
 .UNINDENT
@@ -1208,9 +1208,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.0.7.tar.gz
-% tar xvzf groonga\-5.0.7.tar.gz
-% cd groonga\-5.0.7
+% wget http://packages.groonga.org/source/groonga/groonga\-5.0.8.tar.gz
+% tar xvzf groonga\-5.0.8.tar.gz
+% cd groonga\-5.0.8
 .ft P
 .fi
 .UNINDENT
@@ -1411,9 +1411,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.0.7.tar.gz
-% tar xvzf groonga\-5.0.7.tar.gz
-% cd groonga\-5.0.7
+% wget http://packages.groonga.org/source/groonga/groonga\-5.0.8.tar.gz
+% tar xvzf groonga\-5.0.8.tar.gz
+% cd groonga\-5.0.8
 .ft P
 .fi
 .UNINDENT
@@ -1478,9 +1478,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.0.7.tar.gz
-% gtar xvzf groonga\-5.0.7.tar.gz
-% cd groonga\-5.0.7
+% wget http://packages.groonga.org/source/groonga/groonga\-5.0.8.tar.gz
+% gtar xvzf groonga\-5.0.8.tar.gz
+% cd groonga\-5.0.8
 .ft P
 .fi
 .UNINDENT
@@ -1620,9 +1620,9 @@ steps:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.0.7.tar.gz
-% tar xvzf groonga\-5.0.7.tar.gz
-% cd groonga\-5.0.7
+% wget http://packages.groonga.org/source/groonga/groonga\-5.0.8.tar.gz
+% tar xvzf groonga\-5.0.8.tar.gz
+% cd groonga\-5.0.8
 % ./configure
 % make
 % sudo make install
@@ -1912,6 +1912,9 @@ There are mailing lists for discussion about Groonga.
 .B For Japanese speakers
 \fI\%groonga\-dev@lists.osdn.me\fP
 .UNINDENT
+.SS Chat room
+.sp
+You can join \fI\%groonga/public chat room on Gitter\fP\&.
 .SS Twitter
 .sp
 \fI\%@groonga\fP tweets Groonga related
@@ -3373,7 +3376,9 @@ select \-\-table ToyBox \-\-output_columns _key,price,weight
 .sp
 The string types are divided according to the maximum length. For more details, see \fB/reference/types\fP\&. The default value is the zero\-length string.
 .sp
-The following example creates a ShortText column and updates existing records. The third record has the default value because not updated.
+The following example creates a \fBShortText\fP column and updates
+existing records. The third record (\fB"Block"\fP key record) has the
+default value (zero\-length string) because it\(aqs not updated.
 .sp
 Execution example:
 .INDENT 0.0
@@ -3442,7 +3447,9 @@ So, Groonga shows the value of Epoch as floating point. Integral part means the
 .UNINDENT
 .UNINDENT
 .sp
-The following example creates a Time column and updates existing records. The first record has the default value because not updated.
+The following example creates a \fBTime\fP column and updates existing
+records. The first record (\fB"Monkey"\fP key record) has the default
+value (\fB0.0\fP) because it\(aqs not updated.
 .sp
 Execution example:
 .INDENT 0.0
@@ -3511,7 +3518,9 @@ The longitude and latitude types are divided according to the geographic coordin
 .sp
 A number with/without a decimal point represents a longitude or latitude in milliseconds/degrees respectively. Note that a combination of a number with a decimal point and a number without a decimal point (e.g. 35.1x139) must not be used. A comma (\(aq,\(aq) is also available as a delimiter. The default value is "0x0".
 .sp
-The following example creates a WGS84GeoPoint column and updates existing records. The second record has the default value because not updated.
+The following example creates a \fBWGS84GeoPoint\fP column and updates
+existing records. The second record (\fB"Flower"\fP key record) has the
+default value (\fB"0x0"\fP) because it\(aqs not updated.
 .sp
 Execution example:
 .INDENT 0.0
@@ -3572,9 +3581,12 @@ select \-\-table ToyBox \-\-output_columns _key,location
 .sp
 Groonga supports a reference column, which stores references to records in its associated table. In practice, a reference column stores the IDs of the referred records in the associated table and enables access to those records.
 .sp
-You can specify a column in the associated table to the \fIoutput_columns\fP parameter of a \fB/reference/commands/select\fP command. The format is "Src.Dest" where Src is the name of the reference column and Dest is the name of the target column. If only the reference column is specified, it is handled as "Src._key". Note that if a reference does not point to a valid record, a \fB/reference/commands/select\fP command outputs the default value of the target column.
+You can specify a column in the associated table to the \fBoutput_columns\fP parameter of a \fB/reference/commands/select\fP command. The format is \fBSrc.Dest\fP where Src is the name of the reference column and Dest is the name of the target column. If only the reference column is specified, it is handled as \fBSrc._key\fP\&. Note that if a reference does not point to a valid record, a \fB/reference/commands/select\fP command outputs the default value of the target column.
 .sp
-The following example adds a reference column to the Site table that was created in the previous tutorial. The new column, named link, is designed for storing links among records in the Site table.
+The following example adds a reference column to the \fBSite\fP table
+that was created in tutorial\-introduction\-create\-table\&. The new
+column, named \fBlink\fP, is designed for storing links among records in
+the \fBSite\fP table.
 .sp
 Execution example:
 .INDENT 0.0
@@ -3766,7 +3778,7 @@ _id <= 1
 .UNINDENT
 .UNINDENT
 .sp
-In this case, this query returns the records which meets the condition that the value of \fB_id\fP is equal to 1.
+In this case, this query returns the records which meets the condition that the value of \fB_id\fP is equal to or less than 1.
 .sp
 Moreover, you can use \fB&&\fP for AND search, \fB||\fP for OR search.
 .sp
@@ -14077,7 +14089,7 @@ See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
 .sp
 define_selector \- 検索コマンドを定義
 .sp
-Groonga組込コマンドの一つであるdefine_selectorについて説明します。組込コマンドは、groonga実行ファイルの引数>、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+Groonga組込コマンドの一つであるdefine_selectorについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
 .sp
 define_selectorは、検索条件をカスタマイズした新たな検索コマンドを定義します。
 .SS Syntax
@@ -15651,7 +15663,7 @@ debug
 .sp
 log_put \- ログ出力
 .sp
-groonga組込コマンドの一つであるlog_putについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入>力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+groonga組込コマンドの一つであるlog_putについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
 .sp
 log_putは、ログにmessageを出力します。
 .SS Syntax
@@ -15731,8 +15743,7 @@ debug
 .sp
 log_reopen \- ログファイルの再読み込み
 .sp
-Groonga組込コマンドの一つであるlog_reopenについて説明します。組込コマンドは、groonga実行ファイルの引数、標準
-入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+Groonga組込コマンドの一つであるlog_reopenについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
 .sp
 log_reopenは、ログファイルを再読み込みします。
 .sp
@@ -19501,11 +19512,9 @@ See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
 .sp
 quit \- セッション終了
 .sp
-Groonga組込コマンドの一つであるquitについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、
-またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+Groonga組込コマンドの一つであるquitについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
 .sp
-quitは、groongaプロセスとのセッションを終了します。クライアントプロセスならばgroongaプロセスとの接続を切りま
-す。
+quitは、groongaプロセスとのセッションを終了します。クライアントプロセスならばgroongaプロセスとの接続を切ります。
 .SS Syntax
 .INDENT 0.0
 .INDENT 3.5
@@ -20750,11 +20759,11 @@ be matched against both \fBquery\fP and \fBfilter\fP\&. If both \fBquery\fP
 and \fBfilter\fP aren\(aqt specified, all records are selected.
 .SS \fBmatch_columns\fP
 .sp
-Specifies the default target column for fulltext search by
-\fBquery\fP parameter value. A target column for fulltext search can be
-specified in \fBquery\fP parameter. The difference between
-\fBmatch_columns\fP and \fBquery\fP is whether weight is supported or
-not. \fBmatch_columns\fP supports weight but \fBquery\fP doesn\(aqt.
+Specifies the default target column for fulltext search by \fBquery\fP
+parameter value. A target column for fulltext search can be specified
+in \fBquery\fP parameter. The difference between \fBmatch_columns\fP and
+\fBquery\fP is whether weight and score function are supported or
+not. \fBmatch_columns\fP supports them but \fBquery\fP doesn\(aqt.
 .sp
 Weight is relative importance of target column. A higher weight target
 column gets more hit score rather than a lower weight target column
@@ -20929,6 +20938,12 @@ columns for fulltext search are \fB_key\fP and \fBcontent\fP columns and
 is 1. This weight allocation means \fB_key\fP column value is more
 important rather than \fBcontent\fP column value. In this example, title
 of blog entry is more important rather thatn content of blog entry.
+.sp
+You can also specify score function. See \fB/reference/scorer\fP for
+details.
+.sp
+Note that score function isn\(aqt related to \fI\%scorer\fP
+parameter.
 .SS \fBquery\fP
 .sp
 Specifies the query text. Normally, it is used for fulltext search
@@ -26079,12 +26094,14 @@ shutdown
 .SS \fBstatus\fP
 .SS Summary
 .sp
-status \- groongaプロセスの状態表示
+\fBstatus\fP returns the current status of the context that processes
+the request.
 .sp
-Groonga組込コマンドの一つであるstatusについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
-.sp
-statusコマンドは、groongaプロセスの状態を表示します。主にgroongaサーバプロセスに対して使用することを想定しています。
+Context is an unit that processes requests. Normally, context is
+created for each thread.
 .SS Syntax
+.sp
+This command takes no parameters:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -26097,6 +26114,8 @@ status
 .UNINDENT
 .SS Usage
 .sp
+Here is a simple example:
+.sp
 Execution example:
 .INDENT 0.0
 .INDENT 3.5
@@ -26111,56 +26130,206 @@ status
 #     0.000355720520019531
 #   ],
 #   {
-#     "uptime": 1,
+#     "uptime": 0,
 #     "max_command_version": 2,
-#     "n_queries": 0,
+#     "start_time": 1441980651,
 #     "cache_hit_rate": 0.0,
-#     "version": "5.0.6\-128\-g8029ddb",
+#     "version": "5.0.7\-126\-gb6fd7f7",
 #     "alloc_count": 206,
 #     "command_version": 1,
-#     "starttime": 1439994621,
-#     "default_command_version": 1
+#     "starttime": 1441980651,
+#     "default_command_version": 1,
+#     "n_queries": 0
 #   }
 # ]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
+.sp
+It returns the current status of the context that processes the
+request. See \fI\%Return value\fP for details.
 .SS Parameters
 .sp
-ありません。
+This section describes all parameters.
+.SS Required parameters
+.sp
+There is no required parameters.
+.SS Optional parameters
+.sp
+There is no optional parameters.
 .SS Return value
+.sp
+The command returns the current status as an object:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-下記の項目がハッシュ形式で出力されます。
+[
+  HEADER,
+  {
+    "alloc_count": ALLOC_COUNT,
+    "cache_hit_rate": CACHE_HIT_RATE,
+    "command_version": COMMAND_VERSION,
+    "default_command_version": DEFAULT_COMMAND_VERSION,
+    "max_command_version": MAX_COMMAND_VERSION,
+    "n_queries": N_QUERIES,
+    "start_time": START_TIME,
+    "starttime": STARTTIME,
+    "uptime": UPTIME,
+    "version": VERSION
+  }
+]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
+See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
+.sp
+Here are descriptions about values. See \fI\%Usage\fP for real
+values:
+.TS
+center;
+|l|l|l|.
+_
+T{
+Key
+T}	T{
+Description
+T}	T{
+Example
+T}
+_
+T{
 \fBalloc_count\fP
+T}	T{
+The number of allocated memory blocks that aren\(aqt freed.  If
+this value is continuously increased, there may be a memory
+leak.
+T}	T{
+\fB1400\fP
+T}
+_
+T{
+\fBcache_hit_rate\fP
+T}	T{
+Percentage of cache used responses in the Groonga process. If
+there are 10 requests and 7 responses are created from cache,
+\fBcache_hit_rate\fP is \fB70.0\fP\&. The percentage is computed from
+only requests that use commands that support cache.
+.sp
+Here are commands that support cache:
 .INDENT 0.0
 .INDENT 3.5
-groongaプロセスの内部でアロケートされ、まだ解放されてないメモリブロックの数を示します。Groongaをbuildする際に、configureオプションで \-\-enable\-exact\-alloc\-countが指定されていたならば、正確な値を返します。それ以外の場合は不正確な値を返す場合があります。
+.INDENT 0.0
+.IP \(bu 2
+\fBselect\fP
+.IP \(bu 2
+\fBlogical_select\fP
+.IP \(bu 2
+\fBlogical_range_filter\fP
+.IP \(bu 2
+\fBlogical_count\fP
 .UNINDENT
 .UNINDENT
+.UNINDENT
+T}	T{
+\fB29.4\fP
+T}
+_
+T{
+\fBcommand_version\fP
+T}	T{
+The \fB/reference/command/command_version\fP that is used by
+the context.
+T}	T{
+\fB1\fP
+T}
+_
+T{
+\fBdefault_command_version\fP
+T}	T{
+The default \fB/reference/command/command_version\fP of the
+Groonga process.
+T}	T{
+\fB1\fP
+T}
+_
+T{
+\fBmax_command_version\fP
+T}	T{
+The max \fB/reference/command/command_version\fP of the
+Groonga process.
+T}	T{
+\fB2\fP
+T}
+_
+T{
+\fBn_queries\fP
+T}	T{
+The number of requests processed by the Groonga process. It
+counts only requests that use commands that support cache.
 .sp
-\fBstarttime\fP
+Here are commands that support cache:
 .INDENT 0.0
 .INDENT 3.5
-groongaプロセスが起動した時刻のtvsec値を返します。
+.INDENT 0.0
+.IP \(bu 2
+\fBselect\fP
+.IP \(bu 2
+\fBlogical_select\fP
+.IP \(bu 2
+\fBlogical_range_filter\fP
+.IP \(bu 2
+\fBlogical_count\fP
+.UNINDENT
 .UNINDENT
 .UNINDENT
+T}	T{
+\fB29\fP
+T}
+_
+T{
+\fBstart_time\fP
+T}	T{
+New in version 5.0.8.
+
 .sp
+The time that the Groonga process started in UNIX time.
+T}	T{
+\fB1441761403\fP
+T}
+_
+T{
+\fBstarttime\fP
+T}	T{
+Deprecated since version 5.0.8: Use \fBstart_time\fP instead.
+T}	T{
+\fB1441761403\fP
+T}
+_
+T{
 \fBuptime\fP
-.INDENT 0.0
-.INDENT 3.5
-groongaプロセスが起動してから経過した秒数を返します。
-.UNINDENT
-.UNINDENT
+T}	T{
+The elapsed time since the Groonga process started in second.
+.sp
+For example, \fB216639\fP means that \fB2.5\fP (= \fB216639 / 60 /
+60 / 24 = 2.507\fP) days.
+T}	T{
+\fB216639\fP
+T}
+_
+T{
+\fBversion\fP
+T}	T{
+The version of the Groonga process.
+T}	T{
+\fB5.0.7\fP
+T}
+_
+.TE
 .SS \fBsuggest\fP
 .sp
 \fBNOTE:\fP
@@ -27124,8 +27293,7 @@ See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
 .sp
 table_list \- DBに定義されているテーブルをリスト表示
 .sp
-Groonga組込コマンドの一つであるtable_listについて説明します。組込コマンドは、groonga実行ファイルの引数、標準
-入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+Groonga組込コマンドの一つであるtable_listについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
 .sp
 table_listは、DBに定義されているテーブルのリストを表示します。
 .SS Syntax
@@ -27319,12 +27487,12 @@ valueが属する型
 .SS \fBtable_remove\fP
 .SS Summary
 .sp
-table_remove \- テーブルの削除
-.sp
-groonga組込コマンドの一つであるtable_removeについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
-.sp
-table_removeはテーブルと定義されているカラムを削除します。カラムに付随するインデックスも再帰的に削除されます。
+\fBtable_remove\fP removes a table and its columns. If there are one or
+more indexes against key of the table and its columns, they are also
+removed.
 .SS Syntax
+.sp
+This command takes only one required parameter:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -27336,42 +27504,422 @@ table_remove name
 .UNINDENT
 .UNINDENT
 .SS Usage
+.sp
+You just specify table name that you want to remove. \fBtable_remove\fP
+removes the table and its columns. If the table and its columns are
+indexed, all index columns for the table and its columns are also
+removed.
+.sp
+This section describes about the followings:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+Basic usage
+.IP \(bu 2
+Unremovable cases
+.IP \(bu 2
+Decreases used resources
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS Basic usage
+.sp
+Let\(aqs think about the following case:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+There is one table \fBEntries\fP\&.
+.IP \(bu 2
+\fBEntries\fP table has some columns.
+.IP \(bu 2
+\fBEntries\fP table\(aqs key is indexed.
+.IP \(bu 2
+A column of \fBEntries\fP is indexed.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+Here are commands that create \fBEntries\fP table:
+.sp
+Execution example:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-table_remove Entry
-
-[true]
+table_create Entries TABLE_HASH_KEY UInt32
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Entries title COLUMN_SCALAR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Entries content COLUMN_SCALAR Text
+# [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
-.SS Parameters
+.sp
+Here are commands that create an index for \fBEntries\fP table\(aqs key:
+.sp
+Execution example:
 .INDENT 0.0
-.TP
-.B \fBname\fP
-削除対象のカラムが定義されているテーブルの名前を指定します。
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create EntryKeys TABLE_HASH_KEY UInt32
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create EntryKeys key_index COLUMN_INDEX Entries _key
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
 .UNINDENT
-.SS Return value
+.UNINDENT
+.sp
+Here are commands that create an index for \fBEntries\fP table\(aqs column:
+.sp
+Execution example:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[成功かどうかのフラグ]
+table_create Terms TABLE_PAT_KEY ShortText \e
+  \-\-default_tokenizer TokenBigram \e
+  \-\-normalizer NormalizerAuto
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Terms content_index COLUMN_INDEX Entries content
+# [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-\fB成功かどうかのフラグ\fP
+Let\(aqs confirm the current schema before running \fBtable_remove\fP:
+.sp
+Execution example:
 .INDENT 0.0
 .INDENT 3.5
-エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+.sp
+.nf
+.ft C
+dump
+# table_create Entries TABLE_HASH_KEY UInt32
+# column_create Entries content COLUMN_SCALAR Text
+# column_create Entries title COLUMN_SCALAR ShortText
+#
+# table_create EntryKeys TABLE_HASH_KEY UInt32
+#
+# table_create Terms TABLE_PAT_KEY ShortText \-\-default_tokenizer TokenBigram \-\-normalizer NormalizerAuto
+#
+# column_create EntryKeys key_index COLUMN_INDEX Entries _key
+# column_create Terms content_index COLUMN_INDEX Entries content
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If you remove \fBEntries\fP table, the following tables and columns are
+removed:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBEntries\fP
+.IP \(bu 2
+\fBEntries.title\fP
+.IP \(bu 2
+\fBEntries.context\fP
+.IP \(bu 2
+\fBEntryKeys.key_index\fP
+.IP \(bu 2
+\fBTerms.content_index\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+The following tables (lexicons) aren\(aqt removed:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBEntryKeys\fP
+.IP \(bu 2
+\fBTerms\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+Let\(aqs run \fBtable_remove\fP:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_remove Entries
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is schema after \fBtable_remove\fP\&. Only \fBEntryKeys\fP and
+\fBTerms\fP exist:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+dump
+# table_create EntryKeys TABLE_HASH_KEY UInt32
+#
+# table_create Terms TABLE_PAT_KEY ShortText \-\-default_tokenizer TokenBigram \-\-normalizer NormalizerAuto
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Unremovable cases
+.sp
+There are some unremovable cases:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+One or more tables use the table as key type.
+.IP \(bu 2
+One or more columns use the table as value type.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+Both cases blocks dangling references. If the table is referenced as
+type and the table is removed, tables and columns that refer the table
+are broken.
+.sp
+If the target table satisfies one of them, \fBtable_remove\fP is
+failed. The target table and its columns aren\(aqt removed.
+.sp
+Here is an example for the table is used as key type case.
+.sp
+The following commands create a table to be removed and a table that
+uses the table to be removed as key type:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create ReferencedByTable TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_create ReferenceTable TABLE_HASH_KEY ReferencedByTable
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBtable_remove\fP against \fBReferencedByTable\fP is failed:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_remove ReferencedByTable
+# [
+#   [
+#     \-2,
+#     1337566253.89858,
+#     0.000355720520019531,
+#     "[table][remove] a table that references the table exists: <ReferenceTable._key> \-> <ReferencedByTable>",
+#     [
+#       [
+#         "is_removable_table",
+#         "db.c",
+#         8480
+#       ]
+#     ]
+#   ],
+#   false
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+You need to remove \fBReferenceTable\fP before you remove
+\fBReferencedByTable\fP:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_remove ReferenceTable
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_remove ReferencedByTable
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example for the table is used as value type case.
+.sp
+The following commands create a table to be removed and a column that
+uses the table to be removed as value type:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create ReferencedByColumn TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_create Table TABLE_NO_KEY
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Table reference_column COLUMN_SCALAR ReferencedByColumn
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBtable_remove\fP against \fBReferencedByColumn\fP is failed:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_remove ReferencedByColumn
+# [
+#   [
+#     \-2,
+#     1337566253.89858,
+#     0.000355720520019531,
+#     "[table][remove] a column that references the table exists: <Table.reference_column> \-> <ReferencedByColumn>",
+#     [
+#       [
+#         "is_removable_table",
+#         "db.c",
+#         8500
+#       ]
+#     ]
+#   ],
+#   false
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+You need to remove \fBTable.reference_column\fP before you remove
+\fBReferencedByColumn\fP:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+column_remove Table reference_column
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_remove ReferencedByColumn
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
 .UNINDENT
 .UNINDENT
+.SS Decreases used resources
+.sp
+\fBtable_remove\fP opens all tables and columns in database to check
+\fI\%Unremovable cases\fP\&.
+.sp
+If you have many tables and columns, \fBtable_remove\fP may use many
+resources. There is a workaround to avoid the case.
+.sp
+\fBtable_remove\fP closes temporary opened tables and columns for
+checking when the max number of threads is \fB1\fP\&.
+.sp
+You can confirm and change the current max number of threads by
+\fBthread_limit\fP\&.
+.sp
+The feature is used in the following case:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Entries TABLE_NO_KEY
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+thread_limit 2
+# [[0, 1337566253.89858, 0.000355720520019531], 1]
+table_remove Entries
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+The feature isn\(aqt used in the following case:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Entries TABLE_NO_KEY
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+thread_limit 2
+# [[0, 1337566253.89858, 0.000355720520019531], 1]
+table_remove Entries
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS Required parameters
+.sp
+There is only one required parameters.
+.SS \fBname\fP
+.sp
+Specifies the table name to be removed.
+.sp
+See \fI\%Usage\fP how to use this parameter.
+.SS Return value
+.sp
+The command returns \fBtrue\fP as body on success such as:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If the command fails, error details are in \fBHEADER\fP\&.
+.sp
+See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
 .SS \fBtable_rename\fP
 .SS Summary
 .sp
@@ -29328,138 +29876,68 @@ If you specify other table to column type, this column becomes reference key of
 .SS Builtin types
 .sp
 The following types are defined as builtin types.
+.SS \fBBool\fP
 .sp
-\fBObject\fP
-.INDENT 0.0
-.INDENT 3.5
-All records that belong to any table. [1]
-.UNINDENT
-.UNINDENT
-.sp
-\fBBool\fP
-.INDENT 0.0
-.INDENT 3.5
 Boolean type. The possible values are true and false. (default: false)
 .sp
 To store a value by \fB/reference/commands/load\fP command, becomes false if you specify false, 0 or empty string, becomes true if you specify others.
-.UNINDENT
-.UNINDENT
+.SS \fBInt8\fP
 .sp
-\fBInt8\fP
-.INDENT 0.0
-.INDENT 3.5
 Signed 8bit integer. It\(aqs \-128 or more and 127 or less. (default: 0)
-.UNINDENT
-.UNINDENT
+.SS \fBUInt8\fP
 .sp
-\fBUInt8\fP
-.INDENT 0.0
-.INDENT 3.5
 Unsigned 8bit integer. Is\(aqt 0 or more and 255 or less. (default: 0)
-.UNINDENT
-.UNINDENT
+.SS \fBInt16\fP
 .sp
-\fBInt16\fP
-.INDENT 0.0
-.INDENT 3.5
 Signed 16bit integer. It\(aqs \-32,768 or more and 32,767 or less. (default: 0)
-.UNINDENT
-.UNINDENT
+.SS \fBUInt16\fP
 .sp
-\fBUInt16\fP
-.INDENT 0.0
-.INDENT 3.5
 Unsigned 16bit integer. It\(aqs 0 or more and 65,535 or less. (default: 0)
-.UNINDENT
-.UNINDENT
+.SS \fBInt32\fP
 .sp
-\fBInt32\fP
-.INDENT 0.0
-.INDENT 3.5
 Signed 32bit integer. It\(aqs \-2,147,483,648 or more and 2,147,483,647 or less. (default: 0)
-.UNINDENT
-.UNINDENT
+.SS \fBUInt32\fP
 .sp
-\fBUInt32\fP
-.INDENT 0.0
-.INDENT 3.5
 Unsigned 32bit integer. It\(aqs 0 or more and 4,294,967,295 or less. (default: 0)
-.UNINDENT
-.UNINDENT
+.SS \fBInt64\fP
 .sp
-\fBInt64\fP
-.INDENT 0.0
-.INDENT 3.5
 Signed 64bit integer. It\(aqs \-9,223,372,036,854,775,808 or more and 9,223,372,036,854,775,807 or less. (default: 0)
-.UNINDENT
-.UNINDENT
+.SS \fBUInt64\fP
 .sp
-\fBUInt64\fP
-.INDENT 0.0
-.INDENT 3.5
 Unsigned 64bit integer. It\(aqs 0 or more and 18,446,744,073,709,551,615 or less. (default: 0)
-.UNINDENT
-.UNINDENT
+.SS \fBFloat\fP
 .sp
-\fBFloat\fP
-.INDENT 0.0
-.INDENT 3.5
 Double\-precision floating\-point number of IEEE 754 as a real number. (default: 0.0)
 .sp
 See \fI\%IEEE floating point \- Wikipedia, the free encyclopedia\fP or \fI\%IEEE 754: Standard for Binary Floating\-Point\fP for details of IEEE 754 format.
-.UNINDENT
-.UNINDENT
+.SS \fBTime\fP
 .sp
-\fBTime\fP
-.INDENT 0.0
-.INDENT 3.5
 Date and Time, the number of seconds that have elapsed since 1970\-01\-01 00:00:00 by 64 bit signed integer. (default: 0)
 .sp
 To store a value by \fB/reference/commands/load\fP command, specifies the number of elapsed seconds since 1970\-01\-01 00:00:00. To specify the detailed date and time than seconds, use the decimal.
-.UNINDENT
-.UNINDENT
+.SS \fBShortText\fP
 .sp
-\fBShortText\fP
-.INDENT 0.0
-.INDENT 3.5
 String of 4,095 or less bytes. (default: "")
-.UNINDENT
-.UNINDENT
+.SS \fBText\fP
 .sp
-\fBText\fP
-.INDENT 0.0
-.INDENT 3.5
 String of 65,535 or less bytes. (default: "")
-.UNINDENT
-.UNINDENT
+.SS \fBLongText\fP
 .sp
-\fBLongText\fP
-.INDENT 0.0
-.INDENT 3.5
 String of 2,147,483,647 or less bytes. (default: "")
-.UNINDENT
-.UNINDENT
+.SS \fBTokyoGeoPoint\fP
 .sp
-\fBTokyoGeoPoint\fP
-.INDENT 0.0
-.INDENT 3.5
 旧日本測地系による経緯度であり、経度と緯度をミリ秒単位で表現した整数の組により表現します。（デフォルト値: 0x0）
 .sp
 度分秒形式でx度y分z秒となる経度・緯度は、(((x * 60) + y) * 60 + z) * 1000という計算式でミリ秒単位へと変換されます。
+.sp
 \fB/reference/commands/load\fP コマンドで値を格納するときは、"ミリ秒単位の経度xミリ秒単位の緯度" もしくは "経度の小数表記x緯度の小数表記" という文字列表現を使って指定します。経度と緯度の区切りとしては、\(aqx\(aq のほかに \(aq,\(aq を使うことができます。
 .sp
 測地系の詳細については、 \fI\%測地系 \- Wikipedia\fP を参照してください。
-.UNINDENT
-.UNINDENT
+.SS \fBWGS84GeoPoint\fP
 .sp
-\fBWGS84GeoPoint\fP
-.INDENT 0.0
-.INDENT 3.5
 世界測地系（World Geodetic System, WGS 84）による経緯度であり、経度と緯度をミリ秒単位で表現した整数の組により表現します。（デフォルト値: 0x0）
 .sp
 度分秒形式からミリ秒形式への変換方法や \fB/reference/commands/load\fP コマンドにおける指定方法はTokyoGeoPointと同じです。
-.UNINDENT
-.UNINDENT
 .SS Limitations about types
 .SS Types that can\(aqt be specified in primary key of table
 .sp
@@ -29469,9 +29947,6 @@ String of 2,147,483,647 or less bytes. (default: "")
 Groongaのカラムは、ある型のベクターを保存することができます。しかし、ShortText, Text, LongTextの３つの型についてはベクターとして保存したり出力したりすることはできますが、検索条件やドリルダウン条件に指定することができません。
 .sp
 テーブル型は、ベクターとして格納することができます。よって、ShortTextのベクターを検索条件やドリルダウン条件に使用したい場合には、主キーがShortText型のテーブルを別途作成し、そのテーブルを型として利用します。
-脚注
-.IP [1] 5
-Object型はv1.2でサポートされます。
 .SS Tables
 .SS Summary
 .sp
@@ -33110,10 +33585,6 @@ Groonga provides TF\-IDF based scorer as
 \fB/reference/scorers/scorer_tf_idf\fP but doesn\(aqt provide Okapi BM25
 based scorer yet.
 .INDENT 0.0
-.TP
-.B orphan
-.UNINDENT
-.INDENT 0.0
 .INDENT 3.5
 You don\(aqt need to resolve scoring only by score function. Score
 function is highly depends on search query. You may be able to use
@@ -33448,18 +33919,56 @@ Because the scorer used in the \fBselect\fP command limits the maximum
 score value to \fB2\fP\&.
 .sp
 Here is an example that uses multiple scorers:
+.sp
+Execution example:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-\&.. groonga\-command
-\&.. include:: ../example/reference/scorer/usage_multiple_scorers.log
-\&.. select Memos \e
-\&..   \-\-match_columns "scorer_tf_idf(title) || scorer_tf_at_most(content, 2.0)" \e
-\&..   \-\-query "Groonga" \e
-\&..   \-\-output_columns "title, content, _score" \e
-\&..   \-\-sortby "\-_score"
+select Memos \e
+  \-\-match_columns "scorer_tf_idf(title) || scorer_tf_at_most(content, 2.0)" \e
+  \-\-query "Groonga" \e
+  \-\-output_columns "title, content, _score" \e
+  \-\-sortby "\-_score"
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         2
+#       ],
+#       [
+#         [
+#           "title",
+#           "ShortText"
+#         ],
+#         [
+#           "content",
+#           "Text"
+#         ],
+#         [
+#           "_score",
+#           "Int32"
+#         ]
+#       ],
+#       [
+#         "Groonga is fast",
+#         "Groonga! Groonga! Groonga! Groonga is very fast!",
+#         3
+#       ],
+#       [
+#         "Groonga is easy",
+#         "Groonga is very easy full text search engine!",
+#         2
+#       ]
+#     ]
+#   ]
+# ]
 .ft P
 .fi
 .UNINDENT
@@ -33471,18 +33980,56 @@ The \fB\-\-match_columns\fP uses \fBscorer_tf_idf(title)\fP and
 You can use the default scorer and custom scorer in the same
 \fB\-\-match_columns\fP\&. You can use the default scorer by just specifying
 a match column:
+.sp
+Execution example:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-\&.. groonga\-command
-\&.. include:: ../example/reference/scorer/usage_default_and_custom_scorers.log
-\&.. select Memos \e
-\&..   \-\-match_columns "title || scorer_tf_at_most(content, 2.0)" \e
-\&..   \-\-query "Groonga" \e
-\&..   \-\-output_columns "title, content, _score" \e
-\&..   \-\-sortby "\-_score"
+select Memos \e
+  \-\-match_columns "title || scorer_tf_at_most(content, 2.0)" \e
+  \-\-query "Groonga" \e
+  \-\-output_columns "title, content, _score" \e
+  \-\-sortby "\-_score"
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         2
+#       ],
+#       [
+#         [
+#           "title",
+#           "ShortText"
+#         ],
+#         [
+#           "content",
+#           "Text"
+#         ],
+#         [
+#           "_score",
+#           "Int32"
+#         ]
+#       ],
+#       [
+#         "Groonga is fast",
+#         "Groonga! Groonga! Groonga! Groonga is very fast!",
+#         3
+#       ],
+#       [
+#         "Groonga is easy",
+#         "Groonga is very easy full text search engine!",
+#         2
+#       ]
+#     ]
+#   ]
+# ]
 .ft P
 .fi
 .UNINDENT
@@ -33509,7 +34056,196 @@ New in version 5.0.1.
 .sp
 \fBscorer_tf_at_most\fP is a scorer based on TF (term frequency).
 .sp
-TODO
+TF based scorer includes TF\-IDF based scorer has a problem for the
+following case:
+.sp
+If document contains many same keywords such as "They are keyword,
+keyword, keyword ... and keyword", the document has high score. It\(aqs
+not expected. Search engine spammer may use the technique.
+.sp
+\fBscorer_tf_at_most\fP is a TF based scorer but it can solve the case.
+.sp
+\fBscorer_tf_at_most\fP limits the maximum score value. It means that
+\fBscorer_tf_at_most\fP limits effect of a match.
+.sp
+If document contains many same keywords such as "They are keyword,
+keyword, keyword ... and keyword", \fBscorer_tf_at_most(column, 2.0)\fP
+returns at most \fB2\fP as score.
+.INDENT 0.0
+.INDENT 3.5
+You don\(aqt need to resolve scoring only by score function. Score
+function is highly depends on search query. You may be able to use
+metadata of matched record.
+.sp
+For example, Google uses \fI\%PageRank\fP for scoring. You may be
+able to use data type ("title" data are important rather than
+"memo" data), tag, geolocation and so on.
+.sp
+Please stop to think about only score function for scoring.
+.UNINDENT
+.UNINDENT
+.SS Syntax
+.sp
+This scorer has two parameters:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+scorer_tf_at_most(column, max)
+scorer_tf_at_most(index, max)
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+This section describes how to use this scorer.
+.sp
+Here are a schema definition and sample data to show usage.
+.sp
+Sample schema:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Logs TABLE_NO_KEY
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Logs message COLUMN_SCALAR Text
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_create Terms TABLE_PAT_KEY ShortText \e
+  \-\-default_tokenizer TokenBigram \e
+  \-\-normalizer NormalizerAuto
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Terms message_index COLUMN_INDEX|WITH_POSITION Logs message
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Sample data:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+load \-\-table Logs
+[
+{"message": "Notice"},
+{"message": "Notice Notice"},
+{"message": "Notice Notice Notice"},
+{"message": "Notice Notice Notice Notice"},
+{"message": "Notice Notice Notice Notice Notice"}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 5]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+You specify \fBscorer_tf_at_most\fP in select\-match\-columns like
+the following:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+select Logs \e
+  \-\-match_columns "scorer_tf_at_most(message, 3.0)" \e
+  \-\-query "Notice" \e
+  \-\-output_columns "message, _score" \e
+  \-\-sortby "\-_score"
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         5
+#       ],
+#       [
+#         [
+#           "message",
+#           "Text"
+#         ],
+#         [
+#           "_score",
+#           "Int32"
+#         ]
+#       ],
+#       [
+#         "Notice Notice Notice Notice Notice",
+#         3
+#       ],
+#       [
+#         "Notice Notice Notice Notice",
+#         3
+#       ],
+#       [
+#         "Notice Notice Notice",
+#         3
+#       ],
+#       [
+#         "Notice Notice",
+#         2
+#       ],
+#       [
+#         "Notice",
+#         1
+#       ]
+#     ]
+#   ]
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If a document has three or more \fBNotice\fP terms, its score is \fB3\fP\&.
+Because the \fBselect\fP specify \fB3.0\fP as the max score.
+.sp
+If a document has one or two \fBNotice\fP terms, its score is \fB1\fP or
+\fB2\fP\&. Because the score is less than \fB3.0\fP specified as the max score.
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS Required parameters
+.sp
+There is only one required parameters.
+.SS \fBcolumn\fP
+.sp
+The data column that is match target. The data column must be indexed.
+.SS \fBindex\fP
+.sp
+The index column to be used for search.
+.SS Optional parameters
+.sp
+There is no optional parameters.
+.SS Return value
+.sp
+This scorer returns score as builtin\-type\-float\&.
+.sp
+\fB/reference/commands/select\fP returns \fB_score\fP as \fBInt32\fP not
+\fBFloat\fP\&. Because it casts to \fBInt32\fP from \fBFloat\fP for keeping
+backward compatibility.
+.sp
+Score is computed as TF with limitation.
+.SS See also
+.INDENT 0.0
+.IP \(bu 2
+\fB\&../scorer\fP
+.UNINDENT
 .SS \fBscorer_tf_idf\fP
 .sp
 \fBNOTE:\fP
@@ -33540,17 +34276,16 @@ TF\-IDF will compute more suitable score rather than TF for many cases.
 But it\(aqs not perfect.
 .sp
 If document contains many same keywords such as "They are keyword,
-keyword, keyword ... and keyword". It increases score by TF and
+keyword, keyword ... and keyword", it increases score by TF and
 TF\-IDF. Search engine spammer may use the technique. But TF\-IDF
 doesn\(aqt guard from the technique.
 .sp
 \fI\%Okapi BM25\fP can solve the
 case. But it\(aqs more slower than TF\-IDF and not implemented yet in
 Groonga.
-.INDENT 0.0
-.TP
-.B orphan
-.UNINDENT
+.sp
+Groonga provides \fBscorer_tf_at_most\fP scorer that can also solve
+the case.
 .INDENT 0.0
 .INDENT 3.5
 You don\(aqt need to resolve scoring only by score function. Score
@@ -33564,6 +34299,20 @@ able to use data type ("title" data are important rather than
 Please stop to think about only score function for scoring.
 .UNINDENT
 .UNINDENT
+.SS Syntax
+.sp
+This scorer has only one parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+scorer_tf_idf(column)
+scorer_tf_idf(index)
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .SS Usage
 .sp
 This section describes how to use this scorer.
@@ -33693,6 +34442,30 @@ documents that include \fBInfo\fP is \fB4\fP\&. The number of documents that
 include \fBError\fP is \fB1\fP\&. Term that is included in less documents
 means that the term is more characteristic term. Characteristic term
 is important term.
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS Required parameters
+.sp
+There is only one required parameters.
+.SS \fBcolumn\fP
+.sp
+The data column that is match target. The data column must be indexed.
+.SS \fBindex\fP
+.sp
+The index column to be used for search.
+.SS Optional parameters
+.sp
+There is no optional parameters.
+.SS Return value
+.sp
+This scorer returns score as builtin\-type\-float\&.
+.sp
+\fB/reference/commands/select\fP returns \fB_score\fP as \fBInt32\fP not
+\fBFloat\fP\&. Because it casts to \fBInt32\fP from \fBFloat\fP for keeping
+backward compatibility.
+.sp
+Score is computed as TF\-IDF based algorithm.
 .SS See also
 .INDENT 0.0
 .IP \(bu 2
@@ -38226,6 +38999,26 @@ sequential search. It\(aqll be slow for many records and many texts.
 In some cases, pattern match by regular expression can be evaluated
 by index. It\(aqs very fast rather than sequential search. Patterns
 that can be evaluated by index are described later.
+.sp
+New in version 5.0.7: Groonga normalizes match target text by normalizer\-auto
+normalizer when Groonga doesn\(aqt use index for regular expression
+search. It means that regular expression that has upper case such
+as \fBGroonga\fP never match. Because normalizer\-auto
+normalizer normalizes all alphabets to lower case. \fBgroonga\fP
+matches to both \fBGroonga\fP and \fBgroonga\fP\&.
+.sp
+Why is match target text normalizered? It\(aqs for increasing index
+search\-able patterns. If Groonga doesn\(aqt normalize match target
+text, you need to write complex regular expression such as
+\fB[Dd][Ii][Ss][Kk]\fP and \fB(?i)disk\fP for case\-insensitive match.
+Groonga can\(aqt use index against complex regular expression.
+.sp
+If you write \fBdisk\fP regular expression for case\-insensitive
+match, Groonga can search the pattern with index. It\(aqs fast.
+.sp
+You may feel the behavior is strange. But fast search based on this
+behavior will help you.
+
 .sp
 There are many regular expression syntaxes. Groonga uses the same
 syntax in Ruby. Because Groonga uses the same regular expression
@@ -38237,8 +39030,12 @@ means the end of text in other most regular expression syntaxes. The regular
 expression syntax in Ruby uses \fB\eA\fP for the beginning of text and
 \fB\ez\fP for the end of text.
 .sp
-Groonga uses multiline mode since 5.0.6. It means that \fB\&.\fP matches
-on \fB\en\fP\&.
+New in version 5.0.6: Groonga uses multiline mode since 5.0.6. It means that \fB\&.\fP
+matches on \fB\en\fP\&.
+.sp
+But it\(aqs meaningless. Because \fB\en\fP is removed by
+normalizer\-auto normalizer.
+
 .sp
 You can use regular expression in select\-query and
 select\-filter options of \fB/reference/commands/select\fP
@@ -38283,7 +39080,7 @@ Execution example:
 .sp
 .nf
 .ft C
-select Logs \-\-query \(aqmessage:~"[Dd]isk"\(aq
+select Logs \-\-query \(aqmessage:~"disk (space|full)"\(aq
 # [
 #   [
 #     0,
@@ -38331,7 +39128,7 @@ Execution example:
 .sp
 .nf
 .ft C
-select Logs \-\-filter \(aqmessage @~ "[Dd]isk"\(aq
+select Logs \-\-filter \(aqmessage @~ "disk (space|full)"\(aq
 # [
 #   [
 #     0,
@@ -38920,7 +39717,7 @@ index.
 Character class syntax is \fB[...]\fP\&. Character class is useful to
 specify multiple characters to be matched.
 .sp
-For example, \fB[Dd]\fP matches \fBD\fP or \fBd\fP\&.
+For example, \fB[12]\fP matches \fB1\fP or \fB2\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -38928,7 +39725,7 @@ Execution example:
 .sp
 .nf
 .ft C
-select Logs \-\-filter \(aqmessage @~ "[Dd]isk"\(aq
+select Logs \-\-filter \(aqmessage @~ "host[12]"\(aq
 # [
 #   [
 #     0,
@@ -38938,7 +39735,7 @@ select Logs \-\-filter \(aqmessage @~ "[Dd]isk"\(aq
 #   [
 #     [
 #       [
-#         2
+#         5
 #       ],
 #       [
 #         [
@@ -38951,12 +39748,24 @@ select Logs \-\-filter \(aqmessage @~ "[Dd]isk"\(aq
 #         ]
 #       ],
 #       [
+#         1,
+#         "host1:[error]: No memory"
+#       ],
+#       [
 #         2,
 #         "host1:[warning]: Remained disk space is less than 30%"
 #       ],
 #       [
 #         3,
 #         "host1:[error]: Disk full"
+#       ],
+#       [
+#         4,
+#         "host2:[error]: No memory"
+#       ],
+#       [
+#         5,
+#         "host2:[info]: Shutdown"
 #       ]
 #     ]
 #   ]
@@ -40446,6 +41255,9 @@ You can specify multiple close tags for each three arguments.
 This feature is experimental. API will be changed.
 .UNINDENT
 .UNINDENT
+.sp
+New in version 4.0.5.
+
 .SS Summary
 .sp
 \fBhighlight_html\fP tags target text. It can use to highlight the search
@@ -40456,13 +41268,13 @@ For example, a tagged text of \fBI am a groonga user. <3\fP for keyword
 \fBgroonga\fP is \fBI am a <span class="keyword">groonga</span> user. &lt;3\fP\&.
 .SS Syntax
 .sp
-\fBhighlight_html\fP has only one parameter:
+This function has only one parameter:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-highlight_html(column)
+highlight_html(text)
 .ft P
 .fi
 .UNINDENT
@@ -40498,8 +41310,6 @@ load \-\-table Entries
 \fBhighlight_html\fP can be used in only \fB\-\-output_columns\fP in
 \fB/reference/commands/select\fP\&.
 .sp
-\fBhighlight_html\fP requires Groonga 4.0.5 or later.
-.sp
 \fBhighlight_html\fP requires \fB/reference/command/command_version\fP 2
 or later.
 .sp
@@ -40589,10 +41399,16 @@ select Entries \-\-output_columns \(aqhighlight_html("Groonga is very fast fullt
 .UNINDENT
 .SS Parameters
 .sp
-There is only one parameter \fBcolumn\fP .
-.SS \fBcolumn\fP
+This section describes all parameters.
+.SS Required parameters
 .sp
-Specifies a column of the table.
+There is only one required parameters.
+.SS \fBtext\fP
+.sp
+The text to be highlighted in HTML.
+.SS Optional parameters
+.sp
+There is no optional parameters.
 .SS Return value
 .sp
 \fBhighlight_html\fP returns a tagged string or \fBnull\fP\&. If
@@ -48265,6 +49081,25 @@ Normally, this function isn\(aqt needed.
 \fBGRN_SUCCESS\fP on success, not \fBGRN_SUCCESS\fP on error.
 .UNINDENT
 .UNINDENT
+.INDENT 0.0
+.TP
+.B grn_bool_rc grn_ctx_is_opened(grn_ctx\fI\ *ctx\fP, grn_id\fI\ id\fP)
+Checks whether object with the ID is opened or not.
+.INDENT 7.0
+.TP
+.B Parameters
+.INDENT 7.0
+.IP \(bu 2
+\fBctx\fP \-\- The context object.
+.IP \(bu 2
+\fBid\fP \-\- The object ID to be checked.
+.UNINDENT
+.TP
+.B Returns
+\fBGRN_TRUE\fP if object with the ID is opened,
+\fBGRN_FALSE\fP otherwise.
+.UNINDENT
+.UNINDENT
 .SS \fBgrn_db\fP
 .SS Summary
 .sp
@@ -49583,6 +50418,42 @@ dbのidに対応するpathを返します。mroonga向けに用意した内部AP
 .UNINDENT
 .UNINDENT
 .UNINDENT
+.INDENT 0.0
+.TP
+.B grn_rc grn_obj_cast_by_id(grn_ctx\fI\ *ctx\fP, grn_obj\fI\ *source\fP, grn_obj\fI\ *destination\fP, grn_bool\fI\ add_record_if_not_exist\fP)
+It casts value of \fBsource\fP to value with type of
+\fBdestination\fP\&. Casted value is appended to \fBdestination\fP\&.
+.sp
+Both \fBsource\fP and \fBdestination\fP must be bulk.
+.sp
+If \fBdestination\fP is a reference type bulk. (Reference type bulk
+means that type of \fBdestination\fP is a table.)
+\fBadd_record_if_not_exist\fP is used. If \fBsource\fP value doesn\(aqt
+exist in the table that is a type of \fBdestination\fP\&. The \fBsource\fP
+value is added to the table.
+.INDENT 7.0
+.TP
+.B Parameters
+.INDENT 7.0
+.IP \(bu 2
+\fBctx\fP \-\- The context object.
+.IP \(bu 2
+\fBsource\fP \-\- The bulk to be casted.
+.IP \(bu 2
+\fBdestination\fP \-\- The bulk to specify cast target type and store
+casted value.
+.IP \(bu 2
+\fBadd_record_if_not_exist\fP \-\- Whether adding a new record if
+\fBsource\fP value doesn\(aqt exist in
+cast target table. This parameter
+is only used when \fBdestination\fP
+is a reference type bulk.
+.UNINDENT
+.TP
+.B Returns
+\fBGRN_SUCCESS\fP on success, not \fBGRN_SUCCESS\fP on error.
+.UNINDENT
+.UNINDENT
 .SS \fBgrn_proc\fP
 .SS Summary
 .sp
@@ -52458,7 +53329,7 @@ twitterでサポートされている安心感からGroongaユーザーの拡大
 .sp
 twitterは気軽につぶやけることが重要なので、気軽にできないことを相手に要求すると萎縮されてしまう可能性があります。
 .sp
-いきなりredmineでバグ報告をお願いすると、しりごみしてしまうかも知れません。:
+いきなりredmineでバグ報告をお願いすると、しりごみしてしまうかもしれません。:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -52470,8 +53341,7 @@ twitterは気軽につぶやけることが重要なので、気軽にできな
 .UNINDENT
 .UNINDENT
 .sp
-Groonga関連で気軽につぶやけないとなると開発者は困っている人を見つけられないし、利用者は困ったままとなるので、双方にとって嬉しくない状態になっ
-てしまいます。
+Groonga関連で気軽につぶやけないとなると開発者は困っている人を見つけられないし、利用者は困ったままとなるので、双方にとって嬉しくない状態になってしまいます。
 .SS 対応
 .sp
 twitterでやりとりを完結できるようにします。