RubyGems - rroonga - Versions diffs - 5.1.1-x64-mingw32 → 6.0.0-x64-mingw32 - Mend

rroonga 5.1.1-x64-mingw32 → 6.0.0-x64-mingw32

Files changed (1228) hide show

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

@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "GROONGA" "1" "December 28, 2015" "5.1.1" "Groonga"
+.TH "GROONGA" "1" "February 27, 2016" "6.0.0" "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.1.1\-x86.exe\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-6.0.0\-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.1.1\-x64.exe\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-6.0.0\-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.1.1\-x86.zip\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-6.0.0\-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.1.1\-x64.zip\fP
+\fI\%http://packages.groonga.org/windows/groonga/groonga\-6.0.0\-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.1.1.zip\fP
+\fI\%http://packages.groonga.org/source/groonga/groonga\-6.0.0.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.1.1
+> cd c:\eUsers\e%USERNAME%\eDownloads\egroonga\-6.0.0
 .ft P
 .fi
 .UNINDENT
@@ -208,7 +208,7 @@ parameter instead:
 .sp
 .nf
 .ft C
-groonga\-5.1.1> cmake . \-G "Visual Studio 12 2013 Win64" \-DCMAKE_INSTALL_PREFIX=C:\eGroonga
+groonga\-6.0.0> 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.1.1> cmake \-\-build . \-\-config Release
+groonga\-6.0.0> cmake \-\-build . \-\-config Release
 .ft P
 .fi
 .UNINDENT
@@ -232,7 +232,7 @@ Install:
 .sp
 .nf
 .ft C
-groonga\-5.1.1> cmake \-\-build . \-\-config Release \-\-target Install
+groonga\-6.0.0> 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.1.1.tar.gz
-% tar xvzf groonga\-5.1.1.tar.gz
-% cd groonga\-5.1.1
+% curl \-O http://packages.groonga.org/source/groonga/groonga\-6.0.0.tar.gz
+% tar xvzf groonga\-6.0.0.tar.gz
+% cd groonga\-6.0.0
 .ft P
 .fi
 .UNINDENT
@@ -592,9 +592,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.1.1.tar.gz
-% tar xvzf groonga\-5.1.1.tar.gz
-% cd groonga\-5.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-6.0.0.tar.gz
+% tar xvzf groonga\-6.0.0.tar.gz
+% cd groonga\-6.0.0
 .ft P
 .fi
 .UNINDENT
@@ -803,9 +803,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.1.1.tar.gz
-% tar xvzf groonga\-5.1.1.tar.gz
-% cd groonga\-5.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-6.0.0.tar.gz
+% tar xvzf groonga\-6.0.0.tar.gz
+% cd groonga\-6.0.0
 .ft P
 .fi
 .UNINDENT
@@ -1210,9 +1210,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.1.1.tar.gz
-% tar xvzf groonga\-5.1.1.tar.gz
-% cd groonga\-5.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-6.0.0.tar.gz
+% tar xvzf groonga\-6.0.0.tar.gz
+% cd groonga\-6.0.0
 .ft P
 .fi
 .UNINDENT
@@ -1413,9 +1413,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.1.1.tar.gz
-% tar xvzf groonga\-5.1.1.tar.gz
-% cd groonga\-5.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-6.0.0.tar.gz
+% tar xvzf groonga\-6.0.0.tar.gz
+% cd groonga\-6.0.0
 .ft P
 .fi
 .UNINDENT
@@ -1480,9 +1480,9 @@ Download source:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.1.1.tar.gz
-% gtar xvzf groonga\-5.1.1.tar.gz
-% cd groonga\-5.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-6.0.0.tar.gz
+% gtar xvzf groonga\-6.0.0.tar.gz
+% cd groonga\-6.0.0
 .ft P
 .fi
 .UNINDENT
@@ -1622,9 +1622,9 @@ steps:
 .sp
 .nf
 .ft C
-% wget http://packages.groonga.org/source/groonga/groonga\-5.1.1.tar.gz
-% tar xvzf groonga\-5.1.1.tar.gz
-% cd groonga\-5.1.1
+% wget http://packages.groonga.org/source/groonga/groonga\-6.0.0.tar.gz
+% tar xvzf groonga\-6.0.0.tar.gz
+% cd groonga\-6.0.0
 % ./configure
 % make
 % sudo make install
@@ -7675,7 +7675,7 @@ In which cases, query string is replaced to "(theater OR theatre)", thus synonym
 .SH SERVER
 .SS Server packages
 .sp
-The package \fBgroonga\fP is the mininum set of fulltext search engine.
+The package \fBgroonga\fP is the minimum set of fulltext search engine.
 If you want to use groonga for server use, you can install
 additional preconfigured packages.
 .sp
@@ -8654,6 +8654,8 @@ groonga [\-p PORT_NUMBER] \-d \-\-protocol memcached DB_PATH
 .UNINDENT
 .sp
 The \fI\-\-protocol\fP option and its argument specify the protocol of the server. "memcached" specifies to use the memcached binary protocol.
+.sp
+You don\(aqt need to create a table. When Groonga receives a request, it creates a table automatically. The table name will be \fIMemcache\fP .
 .SH CLIENT
 .sp
 Groonga supports the original protocol (\fB/spec/gqtp\fP), the memcached
@@ -8728,7 +8730,7 @@ Here is an example to check the database at \fB/var/lib/groonga/db/db\fP:
 .sp
 .nf
 .ft C
-$ grndb check /var/lib/groonga/db/db
+% grndb check /var/lib/groonga/db/db
 .ft P
 .fi
 .UNINDENT
@@ -8740,7 +8742,7 @@ Here is an example to recover the database at \fB/var/lib/groonga/db/db\fP:
 .sp
 .nf
 .ft C
-$ grndb recover /var/lib/groonga/db/db
+% grndb recover /var/lib/groonga/db/db
 .ft P
 .fi
 .UNINDENT
@@ -8760,6 +8762,58 @@ You must not use this command for opened database. If the database
 is opened, this command may report wrong result.
 .UNINDENT
 .UNINDENT
+.sp
+\fBcheck\fP has some options.
+.SS \fB\-\-target\fP
+.sp
+New in version 5.1.2.
+.sp
+It specifies a check target object.
+.sp
+If your database is large and you know an unreliable object, this
+option will help you. \fBcheck\fP need more time for large database. You
+can reduce check time by \fB\-\-target\fP option to reduce check target.
+.sp
+The check target is checked recursive. Because related objects of
+unreliable object will be unreliable.
+.sp
+If the check target is a table, all columns of the table are also
+checked recursive.
+.sp
+If the check target is a table and its key type is another table, the
+another table is also checked recursive.
+.sp
+If the check target is a column and its value type is a table, the
+table is also checked recursive.
+.sp
+If the check target is an index column, the table specified as value
+type and all sources are also checked recursive.
+.sp
+Here is an example that checks only \fBEntries\fP table and its
+columns:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+% grndb check \-\-target Entries /var/lib/groonga/db/db
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example that checks only \fBEntries.name\fP column:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+% grndb check \-\-target Entries.name /var/lib/groonga/db/db
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
 .SS \fBrecover\fP
 .sp
 It recovers an existing broken Groonga database.
@@ -9073,7 +9127,7 @@ groonga [options] \-\-protocol http \-d DB_PATH
 .UNINDENT
 .UNINDENT
 .sp
-\fB\-\-pid\-file\fP option will be useful for daemon mode.
+\fI\%\-\-pid\-path\fP option will be useful for daemon mode.
 .SS Client mode
 .sp
 In client mode, \fBgroonga\fP executable file runs as a client for GQTP
@@ -9297,10 +9351,10 @@ PIDを保存するパスを指定します。(デフォルトでは保存しま
 ; \(aq;\(aq以降もコメント。
 # \(aqキー = 値\(aqでオプションを指定。
-pid\-file = /var/run/groonga.pid
+pid\-path = /var/run/groonga.pid
 # \(aq=\(aqの前後の空白はは無視される。↓は↑と同じ意味。
-pid\-file=/var/run/groonga.pid
+pid\-path=/var/run/groonga.pid
 # \(aqキー\(aqは\(aq\-\-XXX\(aqスタイルのオプション名と同じものが使える。
 # 例えば、\(aq\-\-pid\-path\(aqに対応するキーは\(aqpid\-path\(aq。
@@ -11314,7 +11368,7 @@ Command is the most important processing unit in query API. You
 request a processing to groonga by a command.
 .sp
 This section describes about command and built\-in commands.
-.SS コマンドバージョン
+.SS Command version
 .SS 概要
 .sp
 Groonga1.1からコマンドバージョンという概念が導入されます。コマンドバージョンは、selectやloadなどのGroongaのコマンドの仕様の互換性を表します。Groongaパッケージのバージョンが新しくなったとしても、同一のコマンドバージョンが使用可能であるなら、すべてのコマンドについて互換性が保証されます。コマンドバージョンが異なれば、同じ名前のコマンドであっても、動作に互換性がない可能性があります。
@@ -14029,6 +14083,333 @@ See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
 It is \fBtrue\fP on success, \fBfalse\fP otherwise.
 .UNINDENT
 .UNINDENT
+.SS \fBconfig_delete\fP
+.SS Summary
+.sp
+New in version 5.1.2.
+.sp
+\fBconfig_delete\fP command deletes the specified configuration item.
+.SS Syntax
+.sp
+This command takes only one required parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+config_delete key
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+Here is an example to delete \fBalias.column\fP configuration item:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+config_set alias.column Aliases.real_name
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+config_get alias.column
+# [[0, 1337566253.89858, 0.000355720520019531], "Aliases.real_name"]
+config_delete alias.column
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+config_get alias.column
+# [[0, 1337566253.89858, 0.000355720520019531], ""]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example to delete nonexistent configuration item:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+config_delete nonexistent
+# [
+#   [
+#     \-22,
+#     1337566253.89858,
+#     0.000355720520019531,
+#     "[config][delete] failed to delete",
+#     [
+#       [
+#         "grn_config_delete",
+#         "config.c",
+#         166
+#       ]
+#     ]
+#   ],
+#   false
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBconfig_delete\fP returns an error when you try to delete nonexistent
+configuration item.
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS Required parameters
+.sp
+There is one required parameter.
+.SS \fBkey\fP
+.sp
+Specifies the key of target configuration item.
+.sp
+The max key size is 4KiB.
+.sp
+You can\(aqt use an empty string as key.
+.SS Optional parameters
+.sp
+There is no optional parameters.
+.SS Return value
+.sp
+\fBconfig_delete\fP command returns whether deleting a configuration
+item is succeeded or not:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, SUCCEEDED_OR_NOT]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBHEADER\fP
+.sp
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
+.SS \fBSUCCEEDED_OR_NOT\fP
+.sp
+If command succeeded, it returns true, otherwise it returns false on error.
+.SS See also
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/configuration\fP
+.IP \(bu 2
+\fBconfig_get\fP
+.IP \(bu 2
+\fBconfig_set\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS \fBconfig_get\fP
+.SS Summary
+.sp
+New in version 5.1.2.
+.sp
+\fBconfig_get\fP command returns the value of the specified
+configuration item.
+.SS Syntax
+.sp
+This command takes only one required parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+config_get key
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+Here is an example to set a value to \fBalias.column\fP
+configuration item and get the value:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+config_set alias.column Aliases.real_name
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+config_get alias.column
+# [[0, 1337566253.89858, 0.000355720520019531], "Aliases.real_name"]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example to get nonexistent configuration item value:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+config_get nonexistent
+# [[0, 1337566253.89858, 0.000355720520019531], ""]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBconfig_get\fP returns an empty string for nonexistent configuration
+item key.
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS Required parameters
+.sp
+There is one required parameter.
+.SS \fBkey\fP
+.sp
+Specifies the key of target configuration item.
+.sp
+The max key size is 4KiB.
+.sp
+You can\(aqt use an empty string as key.
+.SS Optional parameters
+.sp
+There is no optional parameters.
+.SS Return value
+.sp
+\fBconfig_get\fP command returns the value of the specified
+configuration item:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, VALUE]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBHEADER\fP
+.sp
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
+.SS \fBVALUE\fP
+.sp
+\fBVALUE\fP is the value of the configuration item specified by
+\fBkey\fP\&. It\(aqs a string.
+.SS See also
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/configuration\fP
+.IP \(bu 2
+\fBconfig_set\fP
+.IP \(bu 2
+\fBconfig_delete\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS \fBconfig_set\fP
+.SS Summary
+.sp
+New in version 5.1.2.
+.sp
+\fBconfig_set\fP command sets a value to the specified
+configuration item.
+.SS Syntax
+.sp
+This command takes two required parameters:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+config_set key value
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+Here is an example to set a value to \fBalias.column\fP
+configuration item and confirm the set value:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+config_set alias.column Aliases.real_name
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+config_get alias.column
+# [[0, 1337566253.89858, 0.000355720520019531], "Aliases.real_name"]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS Required parameters
+.sp
+There are required parameters.
+.SS \fBkey\fP
+.sp
+Specifies the key of target configuration item.
+.sp
+The max key size is 4KiB.
+.sp
+You can\(aqt use an empty string as key.
+.SS \fBvalue\fP
+.sp
+Specifies the value of the target configuration item specified by
+\fBkey\fP\&.
+.sp
+The max value size is 4091B (= 4KiB \- 5B).
+.SS Optional parameters
+.sp
+There is no optional parameters.
+.SS Return value
+.sp
+\fBconfig_set\fP command returns whether setting a configuration item
+value is succeeded or not:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, SUCCEEDED_OR_NOT]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBHEADER\fP
+.sp
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
+.SS \fBSUCCEEDED_OR_NOT\fP
+.sp
+If command succeeded, it returns true, otherwise it returns false on error.
+.SS See also
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/configuration\fP
+.IP \(bu 2
+\fBconfig_get\fP
+.IP \(bu 2
+\fBconfig_delete\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS \fBdatabase_unmap\fP
 .SS Summary
 .sp
@@ -15524,6 +15905,148 @@ load \-\-table Entry \-\-input_type json
 .SS See also
 .sp
 \fB/reference/grn_expr\fP
+.SS \fBlock_acquire\fP
+.SS Summary
+.sp
+New in version 5.1.2.
+.sp
+\fBlock_acquire\fP command acquires the lock of the target object. The
+target object is one of database, table and column.
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+This is a dangerous command. You must release locks by
+\fBlock_release\fP that you acquire when these locks are no longer
+needed. If you forget to release these locks, your database may be
+broken.
+.UNINDENT
+.UNINDENT
+.SS Syntax
+.sp
+This command takes only one optional parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+lock_clear [target_name=null]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If \fBtarget_name\fP parameters is omitted, database is used for the
+target object.
+.SS Usage
+.sp
+Here is an example to acquire the lock of the database:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+lock_acquire
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If the database is locked, you can\(aqt create a new table and
+column. Release the lock of the database to show another examples.
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+lock_release
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example to acquire the lock of \fBEntries\fP table:
+.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]
+lock_acquire Entries
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example to acquire the lock of \fBSites.title\fP column:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Sites TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Sites title COLUMN_SCALAR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+lock_acquire Sites.title
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS \fBtarget_name\fP
+.sp
+Specifies the name of table or column.
+.sp
+If you don\(aqt specify it, database is used for the target object.
+.sp
+The default is none. It means that the target object is database.
+.SS Return value
+.sp
+\fBlock_acquire\fP command returns whether lock is acquired or not:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, SUCCEEDED_OR_NOT]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBHEADER\fP
+.sp
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
+.SS \fBSUCCEEDED_OR_NOT\fP
+.sp
+If command succeeded, it returns true, otherwise it returns false on error.
+.SS See also
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBlock_release\fP
+.IP \(bu 2
+\fBlock_clear\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS \fBlock_clear\fP
 .SS Summary
 .sp
@@ -15575,7 +16098,7 @@ lock_clear
 .UNINDENT
 .UNINDENT
 .sp
-Here is an example to clear locks of \fBEntry\fP table and \fBEntry\fP
+Here is an example to clear locks of \fBEntries\fP table and \fBEntries\fP
 table columns:
 .sp
 Execution example:
@@ -15584,18 +16107,18 @@ Execution example:
 .sp
 .nf
 .ft C
-table_create Entry TABLE_NO_KEY
+table_create Entries TABLE_NO_KEY
 # [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create Entry body COLUMN_SCALAR Text
+column_create Entries body COLUMN_SCALAR Text
 # [[0, 1337566253.89858, 0.000355720520019531], true]
-lock_clear Entry
+lock_clear Entries
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-Here is an example to clear the lock of \fBSite.title\fP column:
+Here is an example to clear the lock of \fBSites.title\fP column:
 .sp
 Execution example:
 .INDENT 0.0
@@ -15603,11 +16126,11 @@ Execution example:
 .sp
 .nf
 .ft C
-table_create Site TABLE_HASH_KEY ShortText
+table_create Sites TABLE_HASH_KEY ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create Site title COLUMN_SCALAR ShortText
+column_create Sites title COLUMN_SCALAR ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
-lock_clear Site.title
+lock_clear Sites.title
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
@@ -15625,7 +16148,8 @@ If you don\(aqt specify it, database is used for the target object.
 The default is none. It means that the target object is database.
 .SS Return value
 .sp
-\fBlock_clear\fP command returns whether lock is acquired or not:
+\fBlock_clear\fP command returns whether lock is cleared successfully or
+not:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -15650,6 +16174,138 @@ See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
 If command succeeded, it returns true, otherwise it returns false on error.
 .UNINDENT
 .UNINDENT
+.SS \fBlock_release\fP
+.SS Summary
+.sp
+New in version 5.1.2.
+.sp
+\fBlock_release\fP command releases the lock of the target object. The
+target object is one of database, table and column.
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+This is a dangerous command. You must only release locks that you
+acquire by \fBlock_acquire\fP\&. If you release locks without
+\fBlock_acquire\fP, your database may be broken.
+.UNINDENT
+.UNINDENT
+.SS Syntax
+.sp
+This command takes only one optional parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+lock_clear [target_name=null]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If \fBtarget_name\fP parameters is omitted, database is used for the
+target object.
+.SS Usage
+.sp
+Here is an example to release the lock of the database:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+lock_acquire
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+lock_release
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example to release the lock of \fBEntries\fP table:
+.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]
+lock_acquire Entries
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+lock_release Entries
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example to release the lock of \fBSites.title\fP column:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Sites TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Sites title COLUMN_SCALAR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+lock_acquire Sites.title
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+lock_release Sites.title
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS \fBtarget_name\fP
+.sp
+Specifies the name of table or column.
+.sp
+If you don\(aqt specify it, database is used for the target object.
+.sp
+The default is none. It means that the target object is database.
+.SS Return value
+.sp
+\fBlock_release\fP command returns whether lock is released successfully
+or not:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, SUCCEEDED_OR_NOT]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBHEADER\fP
+.sp
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
+.SS \fBSUCCEEDED_OR_NOT\fP
+.sp
+If command succeeded, it returns true, otherwise it returns false on error.
+.SS See also
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBlock_acquire\fP
+.IP \(bu 2
+\fBlock_clear\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS \fBlog_level\fP
 .SS Summary
 .sp
@@ -19360,10 +20016,10 @@ object_exist Users
 .UNINDENT
 .UNINDENT
 .sp
-The \fBobject_exist Users\fP returns \fBfalse\fP before we create
+The \fBobject_exist Users\fP returns \fBfalse\fP before you create
 \fBUsers\fP table.
 .sp
-The \fBobject_exist Users\fP returns \fBtrue\fP after we create \fBUsers\fP
+The \fBobject_exist Users\fP returns \fBtrue\fP after you create \fBUsers\fP
 table.
 .SS Parameters
 .sp
@@ -19397,6 +20053,9 @@ object_exist Logs.timestamp
 .sp
 \fBLogs\fP is table name and \fBtimestamp\fP is column name in
 \fBLogs.timestamp\fP\&.
+.SS Optional parameters
+.sp
+There is no optional parameters.
 .SS Return value
 .sp
 The command returns \fBtrue\fP as body if object with the specified name
@@ -19425,39 +20084,44 @@ The command returns \fBfalse\fP otherwise such as:
 .UNINDENT
 .sp
 See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
-.SS \fBplugin_register\fP
-.sp
-New in version 5.0.1.
+.SS \fBobject_inspect\fP
 .SS Summary
 .sp
-\fBplugin_register\fP command registers a plugin. You need to register a plugin
-before you use a plugin.
+New in version 6.0.0.
 .sp
-You need just one \fBplugin_register\fP command for a plugin in the same
-database because registered plugin information is written into the
-database.  When you restart your \fBgroonga\fP process, \fBgroonga\fP
-process loads all registered plugins without \fBplugin_register\fP command.
+\fBobject_inspect\fP inspects an object. You can confirm details of an
+object.
 .sp
-You can unregister a registered plugin by \fBplugin_unregister\fP\&.
+For example:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+If the object is a table, you can confirm the number of records in
+the table.
+.IP \(bu 2
+If the object is a column, you can confirm the type of value of
+the column.
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS Syntax
 .sp
-This command takes only one required parameter:
+This command takes only one optional parameter:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-plugin_register name
+object_inspect [name=null]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .SS Usage
 .sp
-Here is a sample that registers \fBQueryExpanderTSV\fP query expander
-that is included in
-\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
+You can inspect an object in the database specified by \fBname\fP:
 .sp
 Execution example:
 .INDENT 0.0
@@ -19465,295 +20129,551 @@ Execution example:
 .sp
 .nf
 .ft C
-plugin_register query_expanders/tsv
+table_create Users TABLE_HASH_KEY ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
+load \-\-table Users
+[
+{"_key": "Alice"}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 1]
+object_inspect Users
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   {
+#     "name": "Users",
+#     "n_records": 1,
+#     "value": {
+#       "type": null
+#     },
+#     "key": {
+#       "total_size": 5,
+#       "max_total_size": 4294967295,
+#       "type": {
+#         "size": 4096,
+#         "type": {
+#           "id": 32,
+#           "name": "type"
+#         },
+#         "id": 14,
+#         "name": "ShortText"
+#       }
+#     },
+#     "type": {
+#       "id": 48,
+#       "name": "table:hash_key"
+#     },
+#     "id": 256
+#   }
+# ]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB\&.so\fP).
-They are completed automatically.
+The \fBobject_inspect Users\fP returns the following information:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+The name of the table: \fB"name": Users\fP
+.IP \(bu 2
+The total used key size: \fB"key": {"total_size": 5}\fP
+(\fB"Alice"\fP is 5 byte data)
+.IP \(bu 2
+The maximum total key size: \fB"key": {"max_total_size": 4294967295}\fP
+.IP \(bu 2
+and so on.
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .sp
-You can specify absolute path such as \fBplugin_register
-/usr/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
-.SS Return value
+You can inspect the database by not specifying \fBname\fP:
 .sp
-\fBplugin_register\fP returns \fBtrue\fP as body on success such as:
+Execution example:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[HEADER, true]
+object_inspect
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   {
+#     "name_table": {
+#       "name": "",
+#       "n_records": 256,
+#       "value": null,
+#       "key": {
+#         "type": null
+#       },
+#       "type": {
+#         "id": 50,
+#         "name": "table:dat_key"
+#       },
+#       "id": 0
+#     },
+#     "type": {
+#       "id": 55,
+#       "name": "db"
+#     }
+#   }
+# ]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-If \fBplugin_register\fP fails, error details are in \fBHEADER\fP\&.
-.sp
-See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
-.SS See also
+The \fBobject_inspect\fP returns the following information:
+.INDENT 0.0
+.INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fBplugin_unregister\fP
+The table type for object name management:
+\fB"key": {"type": {"name": "table:dat_key"}}\fP
+.IP \(bu 2
+and so on.
 .UNINDENT
-.SS \fBplugin_unregister\fP
-.sp
-\fBNOTE:\fP
-.INDENT 0.0
-.INDENT 3.5
-This command is an experimental feature.
 .UNINDENT
 .UNINDENT
+.SS Parameters
 .sp
-New in version 5.0.1.
-.SS Summary
+This section describes all parameters.
+.SS Required parameters
 .sp
-\fBplugin_unregister\fP command unregisters a plugin.
-.SS Syntax
+There is no required parameters.
+.SS Optional parameters
 .sp
-This command takes only one required parameter:
-.INDENT 0.0
-.INDENT 3.5
+There is only one optional parameter.
+.SS \fBname\fP
 .sp
-.nf
-.ft C
-plugin_unregister name
-.ft P
-.fi
-.UNINDENT
-.UNINDENT
-.SS Usage
+Specifies the object name to be inspected.
 .sp
-Here is a sample that unregisters \fBQueryExpanderTSV\fP query expander
-that is included in
-\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
+If \fBname\fP isn\(aqt specified, the database is inspected.
+.SS Return value
 .sp
-Execution example:
+The command returns an object (nested key and value pairs) that
+includes details of the object (such as table) as body:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-plugin_unregister query_expanders/tsv
-# [[0, 1337566253.89858, 0.000355720520019531], true]
+[HEADER, object]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB\&.so\fP).
-They are completed automatically.
+See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
 .sp
-You can specify absolute path such as \fBplugin_unregister
-/usr/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
-.SS Return value
+The format of the details is depends on object type. For example,
+table has key information but function doesn\(aqt have key information.
+.SS Database
 .sp
-\fBplugin_unregister\fP returns \fBtrue\fP as body on success such as:
+Database inspection returns the following information:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[HEADER, true]
+{
+  "type": {
+    "id": DATABASE_TYPE_ID,
+    "name": DATABASE_TYPE_NAME
+  },
+  "name_table": DATABASE_NAME_TABLE
+}
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
+.SS \fBDATABASE_TYPE_ID\fP
 .sp
-If \fBplugin_unregister\fP fails, error details are in \fBHEADER\fP\&.
+\fBDATABASE_TYPE_ID\fP is always \fB55\fP\&.
+.SS \fBDATABASE_TYPE_NAME\fP
 .sp
-See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
-.SS See also
-.INDENT 0.0
-.IP \(bu 2
-\fBplugin_register\fP
-.UNINDENT
-.SS \fBquit\fP
-.SS Summary
+\fBDATABASE_TYPE_NAME\fP is always \fB"db"\fP\&.
+.SS \fBDATABASE_NAME_TABLE\fP
 .sp
-quit \- セッション終了
+\fBDATABASE_NAME_TABLE\fP is a table for managing object names in the
+database. The table is table\-pat\-key or
+table\-dat\-key\&. Normally, it\(aqs table\-dat\-key\&.
 .sp
-Groonga組込コマンドの一つであるquitについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+See \fI\%Table\fP for format details.
+.SS Table
 .sp
-quitは、groongaプロセスとのセッションを終了します。クライアントプロセスならばgroongaプロセスとの接続を切ります。
-.SS Syntax
+Table inspection returns the following information:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-quit
+{
+  "name": TABLE_NAME,
+  "type": {
+    "id": TABLE_TYPE_ID,
+    "name": TABLE_TYPE_NAME
+  },
+  "key": {
+    "type": TABLE_KEY_TYPE,
+    "total_size": TABLE_KEY_TOTAL_SIZE
+    "max_total_size": TABLE_KEY_MAX_TOTAL_SIZE
+  },
+  "value": {
+    "type": TABLE_VALUE_TYPE,
+  },
+  "n_records": TABLE_N_RECORDS
+}
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
-.SS Usage
+.sp
+There are some exceptions:
 .INDENT 0.0
 .INDENT 3.5
-.sp
-.nf
-.ft C
-quit
-.ft P
-.fi
+.INDENT 0.0
+.IP \(bu 2
+table\-no\-key doesn\(aqt return key information because it
+doesn\(aqt have key.
+.IP \(bu 2
+table\-dat\-key doesn\(aqt return value information because it
+doesn\(aqt have value.
 .UNINDENT
 .UNINDENT
-.SS Parameters
+.UNINDENT
+.SS \fBTABLE_NAME\fP
 .sp
-ありません。
-.SS Return value
+The name of the inspected table.
+.SS \fBTABLE_TYPE_ID\fP
 .sp
-ありません。
-.SS \fBrange_filter\fP
-.SS Summary
+The type ID of the inspected table.
 .sp
-TODO: write me
-.SS Syntax
-.SS Usage
-.SS Return value
-.SS See also
-.INDENT 0.0
-.IP \(bu 2
-\fB/reference/commands/select\fP
-.UNINDENT
-.SS \fBregister\fP
+Here is a list of type IDs:
+.TS
+center;
+|l|l|.
+_
+T{
+Table type
+T}	T{
+ID
+T}
+_
+T{
+table\-hash\-key
+T}	T{
+\fB48\fP
+T}
+_
+T{
+table\-pat\-key
+T}	T{
+\fB49\fP
+T}
+_
+T{
+table\-dat\-key
+T}	T{
+\fB50\fP
+T}
+_
+T{
+table\-no\-key
+T}	T{
+\fB51\fP
+T}
+_
+.TE
+.SS \fBTABLE_TYPE_NAME\fP
 .sp
-Deprecated since version 5.0.1: Use \fBplugin_register\fP instead.
-.SS Summary
+The type name of the inspected table.
 .sp
-\fBregister\fP command registers a plugin. You need to register a plugin
-before you use a plugin.
+Here is a list of type names:
+.TS
+center;
+|l|l|.
+_
+T{
+Table type
+T}	T{
+Name
+T}
+_
+T{
+table\-hash\-key
+T}	T{
+\fB"table:hash_key"\fP
+T}
+_
+T{
+table\-pat\-key
+T}	T{
+\fB"table:pat_key"\fP
+T}
+_
+T{
+table\-dat\-key
+T}	T{
+\fB"table:dat_key"\fP
+T}
+_
+T{
+table\-no\-key
+T}	T{
+\fB"table:no_key"\fP
+T}
+_
+.TE
+.SS \fBTABLE_KEY_TYPE\fP
 .sp
-You need just one \fBregister\fP command for a plugin in the same
-database because registered plugin information is written into the
-database.  When you restart your \fBgroonga\fP process, \fBgroonga\fP
-process loads all registered plugins without \fBregister\fP command.
+The type of key of the inspected table.
 .sp
-\fBNOTE:\fP
-.INDENT 0.0
-.INDENT 3.5
-Registered plugins can be removed since Groonga 5.0.1. Use
-\fBplugin_unregister\fP in such a case.
-.UNINDENT
-.UNINDENT
-.SS Syntax
+See \fI\%Type\fP for format details.
+.SS \fBTABLE_KEY_TOTAL_SIZE\fP
 .sp
-This command takes only one required parameter:
-.INDENT 0.0
-.INDENT 3.5
+The total key size of the inspected table in bytes.
+.SS \fBTABLE_KEY_MAX_TOTAL_SIZE\fP
 .sp
-.nf
-.ft C
-register path
-.ft P
-.fi
-.UNINDENT
-.UNINDENT
-.SS Usage
+The maximum total key size of the inspected table in bytes.
+.SS \fBTABLE_VALUE_TYPE\fP
 .sp
-Here is a sample that registers \fBQueryExpanderTSV\fP query expander
-that is included in
-\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
+The type of value of the inspected table.
 .sp
-Execution example:
+See \fI\%Type\fP for format details.
+.SS \fBTABLE_N_RECORDS\fP
+.sp
+The number of records of the inspected table.
+.sp
+It\(aqs a 64bit unsigned integer value.
+.SS Type
+.sp
+Type inspection returns the following information:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-register query_expanders/tsv
-# [[0, 1337566253.89858, 0.000355720520019531], true]
+{
+  "id": TYPE_ID,
+  "name": TYPE_NAME,
+  "type": {
+    "id": TYPE_ID_OF_TYPE,
+    "name": TYPE_NAME_OF_TYPE
+  },
+  "size": TYPE_SIZE
+}
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
+.SS \fBTYPE_ID\fP
 .sp
-You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB\&.so\fP).
-They are completed automatically.
-.sp
-You can specify absolute path such as \fBregister
-/usr/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
-.SS Return value
-.sp
-\fBregister\fP returns \fBtrue\fP as body on success such as:
-.INDENT 0.0
-.INDENT 3.5
+The ID of the inspected type.
 .sp
-.nf
-.ft C
-[HEADER, true]
-.ft P
-.fi
-.UNINDENT
-.UNINDENT
+Here is an ID list of builtin types:
+.TS
+center;
+|l|l|.
+_
+T{
+Type
+T}	T{
+ID
+T}
+_
+T{
+builtin\-type\-bool
+T}	T{
+\fB3\fP
+T}
+_
+T{
+builtin\-type\-int8
+T}	T{
+\fB4\fP
+T}
+_
+T{
+builtin\-type\-uint8
+T}	T{
+\fB5\fP
+T}
+_
+T{
+builtin\-type\-int16
+T}	T{
+\fB6\fP
+T}
+_
+T{
+builtin\-type\-uint16
+T}	T{
+\fB7\fP
+T}
+_
+T{
+builtin\-type\-int32
+T}	T{
+\fB8\fP
+T}
+_
+T{
+builtin\-type\-uint32
+T}	T{
+\fB9\fP
+T}
+_
+T{
+builtin\-type\-int64
+T}	T{
+\fB10\fP
+T}
+_
+T{
+builtin\-type\-uint64
+T}	T{
+\fB11\fP
+T}
+_
+T{
+builtin\-type\-float
+T}	T{
+\fB12\fP
+T}
+_
+T{
+builtin\-type\-time
+T}	T{
+\fB13\fP
+T}
+_
+T{
+builtin\-type\-short\-text
+T}	T{
+\fB14\fP
+T}
+_
+T{
+builtin\-type\-text
+T}	T{
+\fB15\fP
+T}
+_
+T{
+builtin\-type\-long\-text
+T}	T{
+\fB16\fP
+T}
+_
+T{
+builtin\-type\-tokyo\-geo\-point
+T}	T{
+\fB17\fP
+T}
+_
+T{
+builtin\-type\-wgs84\-geo\-point
+T}	T{
+\fB18\fP
+T}
+_
+.TE
+.SS \fBTYPE_NAME\fP
 .sp
-If \fBregister\fP fails, error details are in \fBHEADER\fP\&.
+The name of the inspected type.
 .sp
-See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
-.SS See also
+Here is a name list of builtin types:
+.INDENT 0.0
+.INDENT 3.5
 .INDENT 0.0
 .IP \(bu 2
-\fBplugin_register\fP
+builtin\-type\-bool
 .IP \(bu 2
-\fBplugin_unregister\fP
+builtin\-type\-int8
+.IP \(bu 2
+builtin\-type\-uint8
+.IP \(bu 2
+builtin\-type\-int16
+.IP \(bu 2
+builtin\-type\-uint16
+.IP \(bu 2
+builtin\-type\-int32
+.IP \(bu 2
+builtin\-type\-uint32
+.IP \(bu 2
+builtin\-type\-int64
+.IP \(bu 2
+builtin\-type\-uint64
+.IP \(bu 2
+builtin\-type\-float
+.IP \(bu 2
+builtin\-type\-time
+.IP \(bu 2
+builtin\-type\-short\-text
+.IP \(bu 2
+builtin\-type\-text
+.IP \(bu 2
+builtin\-type\-long\-text
+.IP \(bu 2
+builtin\-type\-tokyo\-geo\-point
+.IP \(bu 2
+builtin\-type\-wgs84\-geo\-point
 .UNINDENT
-.SS \fBreindex\fP
-.SS Summary
-.sp
-New in version 5.1.0.
+.UNINDENT
+.UNINDENT
+.SS \fBTYPE_ID_OF_TYPE\fP
 .sp
-\fBreindex\fP command recreates one or more index columns.
+\fBTYPE_ID_OF_TYPE\fP is always \fB32\fP\&.
+.SS \fBTYPE_NAME_OF_TYPE\fP
 .sp
-If you specify a database as target object, all index columns are
-recreated.
+\fBTYPE_NAME_OF_TYPE\fP is always \fBtype\fP\&.
+.SS \fBTYPE_SIZE\fP
 .sp
-If you specify a table as target object, all index columns in the
-table are recreated.
+\fBTYPE_SIZE\fP is the size of the inspected type in bytes. If the
+inspected type is variable size type, the size means the maximum size.
+.SS \fBobject_remove\fP
+.SS Summary
 .sp
-If you specify a data column as target object, all index columns for
-the data column are recreated.
+New in version 6.0.0.
 .sp
-If you specify an index column as target object, the index column is
-recreated.
+\fBobject_remove\fP removes an object. You can remove any object
+including table, column, command and so on. Normally, you should use
+specific remove command such as \fBtable_remove\fP and
+\fBcolumn_remove\fP\&.
 .sp
-This command is a useful when your index column is broken.
-The target object is one of database, table and column.
+\fBobject_remove\fP is danger because you can remove any object. You
+should use \fBobject_remove\fP carefully.
 .sp
-\fBNOTE:\fP
-.INDENT 0.0
-.INDENT 3.5
-You can\(aqt use target index columns while \fBreindex\fP command is
-running. If you use the same database from multiple processes, all
-processes except running \fBreindex\fP should reopen the
-database. You can use \fBdatabase_unmap\fP for reopening database.
-.UNINDENT
-.UNINDENT
+\fBobject_remove\fP has "force mode". You can remove a broken object by
+"force mode". "Force mode" is useful to resolve problems reported by
+\fB/reference/executables/grndb\fP\&.
 .SS Syntax
 .sp
-This command takes only one optional parameter:
+This command takes two parameters:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-reindex [target_name=null]
+object_remove name
+              [force=no]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
-.sp
-If \fBtarget_name\fP parameters is omitted, database is used for the
-target object. It means that all index columns in the database are
-recreated.
 .SS Usage
 .sp
-Here is an example to recreate all index columns in the database:
+You can remove an object in the database specified by \fBname\fP:
 .sp
 Execution example:
 .INDENT 0.0
@@ -19761,16 +20681,39 @@ Execution example:
 .sp
 .nf
 .ft C
-reindex
+object_remove Users
+# [
+#   [
+#     \-22,
+#     1337566253.89858,
+#     0.000355720520019531,
+#     "[object][remove] target object doesn\(aqt exist: <Users>",
+#     [
+#       [
+#         "command_object_remove",
+#         "proc_object.c",
+#         121
+#       ]
+#     ]
+#   ],
+#   false
+# ]
+table_create Users TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+object_remove Users
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-Here is an example to recreate all index columns
-(\fBLexicon.entry_key\fP and \fBLexicon.entry_body\fP) in \fBLexicon\fP
-table:
+The \fBobject_remove Users\fP returns \fBfalse\fP before you create
+\fBUsers\fP table.
+.sp
+The \fBobject_remove Users\fP returns \fBtrue\fP after you create \fBUsers\fP
+table.
+.sp
+You can\(aqt remove a broken object by default:
 .sp
 Execution example:
 .INDENT 0.0
@@ -19778,30 +20721,38 @@ Execution example:
 .sp
 .nf
 .ft C
-table_create Entry TABLE_HASH_KEY ShortText
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create Entry body COLUMN_SCALAR Text
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-table_create Lexicon TABLE_PAT_KEY ShortText \e
-  \-\-default_tokenizer TokenBigram \e
-  \-\-normalizer NormalizerAuto
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create Lexicon entry_key COLUMN_INDEX|WITH_POSITION \e
-  Entry _key
+table_create Users TABLE_HASH_KEY ShortText
 # [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create Lexicon entry_body COLUMN_INDEX|WITH_POSITION \e
-  Entry body
+thread_limit 1
+# [[0, 1337566253.89858, 0.000355720520019531], 1]
+database_unmap
 # [[0, 1337566253.89858, 0.000355720520019531], true]
-reindex Lexicon
+echo "BROKEN" > ${DB_PATH}.0000100
+object_remove Users
+# [
+#   [
+#     \-22,
+#     1337566253.89858,
+#     0.000355720520019531,
+#     "[object][remove] failed to open the target object: <Users>",
+#     [
+#       [
+#         "command_object_remove",
+#         "proc_object.c",
+#         116
+#       ]
+#     ]
+#   ],
+#   false
+# ]
+object_exist Users
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-Here is an example to recreate all index columns
-(\fBBigramLexicon.site_title\fP and \fBRegexpLexicon.site_title\fP) of
-\fBSite.title\fP data column:
+You can remove a broken object by \fB\-\-force yes\fP:
 .sp
 Execution example:
 .INDENT 0.0
@@ -19809,32 +20760,44 @@ Execution example:
 .sp
 .nf
 .ft C
-table_create Site TABLE_HASH_KEY ShortText
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create Site title COLUMN_SCALAR ShortText
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-table_create BigramLexicon TABLE_PAT_KEY ShortText \e
-  \-\-default_tokenizer TokenBigram \e
-  \-\-normalizer NormalizerAuto
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create BigramLexicon site_title COLUMN_INDEX|WITH_POSITION \e
-  Site title
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-table_create RegexpLexicon TABLE_PAT_KEY ShortText \e
-  \-\-default_tokenizer TokenRegexp \e
-  \-\-normalizer NormalizerAuto
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create RegexpLexicon site_title COLUMN_INDEX|WITH_POSITION \e
-  Site title
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-reindex Site.title
-# [[0, 1337566253.89858, 0.000355720520019531], true]
+object_remove Users \-\-force yes
+# [
+#   [
+#     \-65,
+#     1337566253.89858,
+#     0.000355720520019531,
+#     "[io][open] file size is too small: <7>(required: >= 64): </tmp/groonga\-databases/commands_object_remove.0000100>",
+#     [
+#       [
+#         "grn_io_open",
+#         "io.c",
+#         565
+#       ]
+#     ]
+#   ],
+#   false
+# ]
+object_exist Users
+# [[0, 1337566253.89858, 0.000355720520019531], false]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-Here is an example to recreate an index column (\fBTimestamp.index\fP):
+\fB\-\-force yes\fP means you enable "force mode". You can remove a broken
+object in "force mode".
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS Required parameters
+.sp
+There is only one required parameters.
+.SS \fBname\fP
+.sp
+Specifies the object name to be removed.
+.sp
+If you want to remove a column, use \fBTABLE_NAME.COLUMN_NAME\fP format
+like the following:
 .sp
 Execution example:
 .INDENT 0.0
@@ -19846,92 +20809,79 @@ table_create Logs TABLE_NO_KEY
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 column_create Logs timestamp COLUMN_SCALAR Time
 # [[0, 1337566253.89858, 0.000355720520019531], true]
-table_create Timestamp TABLE_PAT_KEY Time
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-column_create Timestamp logs_timestamp COLUMN_INDEX  Logs timestamp
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-reindex Timestamp.logs_timestamp
+object_remove Logs.timestamp
 # [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
-.SS Parameters
 .sp
-This section describes all parameters.
-.SS \fBtarget_name\fP
+\fBLogs\fP is table name and \fBtimestamp\fP is column name in
+\fBLogs.timestamp\fP\&.
+.SS Optional parameters
 .sp
-Specifies the name of table or column.
+There is one optional parameter.
+.SS \fBforce\fP
 .sp
-If you don\(aqt specify it, database is used for the target object.
+Specifies whether removing the object in "force mode".
 .sp
-The default is none. It means that the target object is database.
+You can\(aqt remove a broken object by default. But you can remove a
+broken object in "force mode".
+.sp
+\fBforce\fP value must be \fByes\fP or \fBno\fP\&. \fByes\fP means that "force
+mode" is enabled. \fBno\fP means that "force mode" is disabled.
+.sp
+The default value is \fBno\fP\&. It means that "force mode" is disabled by
+default.
 .SS Return value
 .sp
-\fBreindex\fP command returns whether recreation is succeeded or not:
+The command returns \fBtrue\fP as body when the command removed the
+specified object without any error. For example:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[HEADER, SUCCEEDED_OR_NOT]
+[HEADER, true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-\fBHEADER\fP
+The command returns \fBfalse\fP as body when the command gets any
+errors. For example:
 .INDENT 0.0
 .INDENT 3.5
-See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
-.UNINDENT
-.UNINDENT
 .sp
-\fBSUCCEEDED_OR_NOT\fP
-.INDENT 0.0
-.INDENT 3.5
-If command succeeded, it returns true, otherwise it returns false on
-error.
+.nf
+.ft C
+[HEADER, false]
+.ft P
+.fi
 .UNINDENT
 .UNINDENT
-.SS \fBrequest_cancel\fP
-.SS Summary
 .sp
-\fBNOTE:\fP
-.INDENT 0.0
-.INDENT 3.5
-This command is an experimental feature.
-.UNINDENT
-.UNINDENT
+See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
 .sp
-New in version 4.0.9.
+Note that \fBfalse\fP doesn\(aqt mean that "the command can\(aqt remove the
+object". If you enable "force mode", the command removes the object
+even if the object is broken. In the case, the object is removed and
+\fBfalse\fP is returned as body.
+.SS \fBplugin_register\fP
 .sp
-\fBrequest_cancel\fP command cancels a running request.
+New in version 5.0.1.
+.SS Summary
 .sp
-There are some limitations:
-.INDENT 0.0
-.INDENT 3.5
-.INDENT 0.0
-.IP \(bu 2
-Request ID must be managed by user. (You need to assign unique key
-for each request.)
-.IP \(bu 2
-Cancel request may be ignored. (You can send \fBrequest_cancel\fP
-command multiple times for the same request ID.)
-.IP \(bu 2
-Only multithreading type Groonga server is supported. (You can use
-with \fB/reference/executables/groonga\fP based server but can\(aqt
-use with \fB/reference/executables/groonga\-httpd\fP\&.)
-.UNINDENT
-.UNINDENT
-.UNINDENT
+\fBplugin_register\fP command registers a plugin. You need to register a plugin
+before you use a plugin.
 .sp
-See \fB/reference/command/request_id\fP about request ID.
+You need just one \fBplugin_register\fP command for a plugin in the same
+database because registered plugin information is written into the
+database.  When you restart your \fBgroonga\fP process, \fBgroonga\fP
+process loads all registered plugins without \fBplugin_register\fP command.
 .sp
-If request is canceled, the canceled request has \fB\-5\fP
-(\fBGRN_INTERRUPTED_FUNCTION_CALL\fP) as
-\fB/reference/command/return_code\fP\&.
+You can unregister a registered plugin by \fBplugin_unregister\fP\&.
 .SS Syntax
 .sp
 This command takes only one required parameter:
@@ -19940,144 +20890,71 @@ This command takes only one required parameter:
 .sp
 .nf
 .ft C
-request_cancel id
+plugin_register name
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .SS Usage
 .sp
-Here is an example of \fBrequest_cancel\fP command:
-.INDENT 0.0
-.INDENT 3.5
-.sp
-.nf
-.ft C
-$ curl \(aqhttp://localhost:10041/d/select?table=LargeTable&filter=true&request_id=unique\-id\-1\(aq &
-# The above "select" takes a long time...
-# Point: "request_id=unique\-id\-1"
-$ curl \(aqhttp://localhost:10041/d/request_cancel?id=unique\-id\-1\(aq
-[[...], {"id": "unique\-id\-1", "canceled": true}]
-# Point: "id=unique\-id\-1"
-.ft P
-.fi
-.UNINDENT
-.UNINDENT
-.sp
-Assume that the first \fBselect\fP command takes a long
-time. \fBunique\-id\-1\fP request ID is assigned to the \fBselect\fP command
-by \fBrequest_id=unique\-id\-1\fP parameter.
-.sp
-The second \fBrequest_cancel\fP command passes \fBid=unique\-id\-1\fP
-parameter. \fBunique\-id\-1\fP is the same request ID passed in \fBselect\fP
-command.
-.sp
-The \fBselect\fP command may not be canceled immediately. And the cancel
-request may be ignored.
-.sp
-You can send cancel request for the same request ID multiple times. If
-the target request is canceled or finished, \fB"canceled"\fP value is
-changed to \fBfalse\fP from \fBtrue\fP in return value:
-.INDENT 0.0
-.INDENT 3.5
-.sp
-.nf
-.ft C
-$ curl \(aqhttp://localhost:10041/d/request_cancel?id=unique\-id\-1\(aq
-[[...], {"id": "unique\-id\-1", "canceled": true}]
-# "select" is still running... ("canceled" is "true")
-$ curl \(aqhttp://localhost:10041/d/request_cancel?id=unique\-id\-1\(aq
-[[...], {"id": "unique\-id\-1", "canceled": true}]
-# "select" is still running... ("canceled" is "true")
-$ curl \(aqhttp://localhost:10041/d/request_cancel?id=unique\-id\-1\(aq
-[[...], {"id": "unique\-id\-1", "canceled": false}]
-# "select" is canceled or finished. ("canceled" is "false")
-.ft P
-.fi
-.UNINDENT
-.UNINDENT
+Here is a sample that registers \fBQueryExpanderTSV\fP query expander
+that is included in
+\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
 .sp
-If the \fBselect\fP command is canceled, response of the \fBselect\fP
-command has \fB\-5\fP (\fBGRN_INTERRUPTED_FUNCTION_CALL\fP) as
-\fB/reference/command/return_code\fP:
+Execution example:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-$ curl \(aqhttp://localhost:10041/d/select?table=LargeTable&filter=true&request_id=unique\-id\-1\(aq &
-[[\-5, ...], ...]
+plugin_register query_expanders/tsv
+# [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
-.SS Parameters
-.sp
-This section describes parameters of \fBrequest_cancel\fP\&.
-.SS Required parameter
 .sp
-There is required parameter, \fBid\fP\&.
-.SS \fBid\fP
+You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB\&.so\fP).
+They are completed automatically.
 .sp
-Specifies the ID for the target request.
+You can specify absolute path such as \fBplugin_register
+/usr/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
 .SS Return value
 .sp
-\fBrequest_cancel\fP command returns the result of the cancel request:
+\fBplugin_register\fP returns \fBtrue\fP as body on success such as:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[
-  HEADER,
-  {
-    "id":       ID,
-    "canceled": CANCEL_REQUEST_IS_ACCEPTED_OR_NOT
-  }
-]
+[HEADER, true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-\fBHEADER\fP
-.INDENT 0.0
-.INDENT 3.5
-See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
-.UNINDENT
-.UNINDENT
+If \fBplugin_register\fP fails, error details are in \fBHEADER\fP\&.
 .sp
-\fBID\fP
+See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
+.SS See also
 .INDENT 0.0
-.INDENT 3.5
-The ID of the target request.
-.UNINDENT
+.IP \(bu 2
+\fBplugin_unregister\fP
 .UNINDENT
+.SS \fBplugin_unregister\fP
 .sp
-\fBCANCEL_REQUEST_IS_ACCEPTED_OR_NOT\fP
+\fBNOTE:\fP
 .INDENT 0.0
 .INDENT 3.5
-If the cancel request is accepted, this is \fBtrue\fP, otherwise this
-is \fBfalse\fP\&.
-.sp
-Note that "cancel request is accepted" doesn\(aqt means that "the
-target request is canceled". It just means "cancel request is
-notified to the target request but the cancel request may be ignored
-by the target request".
-.sp
-If request assigned with the request ID doesn\(aqt exist, this is
-\fBfalse\fP\&.
-.UNINDENT
+This command is an experimental feature.
 .UNINDENT
-.SS See also
-.INDENT 0.0
-.IP \(bu 2
-\fB/reference/command/request_id\fP
 .UNINDENT
-.SS \fBruby_eval\fP
+.sp
+New in version 5.0.1.
 .SS Summary
 .sp
-\fBruby_eval\fP command evaluates Ruby script and returns the result.
+\fBplugin_unregister\fP command unregisters a plugin.
 .SS Syntax
 .sp
 This command takes only one required parameter:
@@ -20086,16 +20963,16 @@ This command takes only one required parameter:
 .sp
 .nf
 .ft C
-ruby_eval script
+plugin_unregister name
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .SS Usage
 .sp
-You can execute any scripts which mruby supports by calling \fBruby_eval\fP\&.
-.sp
-Here is an example that just calculate \fB1 + 2\fP as Ruby script.
+Here is a sample that unregisters \fBQueryExpanderTSV\fP query expander
+that is included in
+\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
 .sp
 Execution example:
 .INDENT 0.0
@@ -20103,115 +20980,343 @@ Execution example:
 .sp
 .nf
 .ft C
-register ruby/eval
+plugin_unregister query_expanders/tsv
 # [[0, 1337566253.89858, 0.000355720520019531], true]
-ruby_eval "1 + 2"
-# [[0, 1337566253.89858, 0.000355720520019531], {"value": 3}]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-Register \fBruby/eval\fP plugin to use \fBruby_eval\fP command in advance.
-.sp
-Note that \fBruby_eval\fP is implemented as an experimental plugin,
-and the specification may be changed in the future.
-.SS Parameters
-.sp
-This section describes all parameters.
-.SS \fBscript\fP
+You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB\&.so\fP).
+They are completed automatically.
 .sp
-Specifies the Ruby script which you want to evaluate.
+You can specify absolute path such as \fBplugin_unregister
+/usr/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
 .SS Return value
 .sp
-\fBruby_eval\fP returns the evaluated result with metadata such as
-exception information (Including metadata isn\(aqt implemented yet):
+\fBplugin_unregister\fP returns \fBtrue\fP as body on success such as:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[HEADER, {"value": EVALUATED_VALUE}]
+[HEADER, true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .sp
-\fBHEADER\fP
-.INDENT 0.0
-.INDENT 3.5
-See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
-.UNINDENT
-.UNINDENT
+If \fBplugin_unregister\fP fails, error details are in \fBHEADER\fP\&.
 .sp
-\fBEVALUATED_VALUE\fP
+See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
+.SS See also
 .INDENT 0.0
-.INDENT 3.5
-\fBEVALUATED_VALUE\fP is the evaludated value of \fBruby_script\fP\&.
-.sp
-\fBruby_eval\fP supports only a number for evaluated value for now.
-Supported types will be increased in the future.
-.UNINDENT
+.IP \(bu 2
+\fBplugin_register\fP
 .UNINDENT
-.SS See also
-.SS \fBruby_load\fP
+.SS \fBquit\fP
 .SS Summary
 .sp
-\fBruby_load\fP command loads specified Ruby script.
-.SS Syntax
+quit \- セッション終了
 .sp
-This command takes only one required parameter:
+Groonga組込コマンドの一つであるquitについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+.sp
+quitは、groongaプロセスとのセッションを終了します。クライアントプロセスならばgroongaプロセスとの接続を切ります。
+.SS Syntax
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-ruby_load path
+quit
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
 .SS Usage
-.sp
-You can load any script file which mruby supports by calling \fBruby_load\fP\&.
-.sp
-Here is an example that just load \fBexpression.rb\fP as Ruby script.
-.sp
-Execution example:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-register ruby/load
-# [[0, 1337566253.89858, 0.000355720520019531], true]
-ruby_load "expression.rb"
-# [[0, 1337566253.89858, 0.000355720520019531], {"value": null}]
+quit
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Parameters
+.sp
+ありません。
+.SS Return value
+.sp
+ありません。
+.SS \fBrange_filter\fP
+.SS Summary
+.sp
+TODO: write me
+.SS Syntax
+.SS Usage
+.SS Return value
+.SS See also
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/commands/select\fP
+.UNINDENT
+.SS \fBregister\fP
+.sp
+Deprecated since version 5.0.1: Use \fBplugin_register\fP instead.
+.SS Summary
+.sp
+\fBregister\fP command registers a plugin. You need to register a plugin
+before you use a plugin.
+.sp
+You need just one \fBregister\fP command for a plugin in the same
+database because registered plugin information is written into the
+database.  When you restart your \fBgroonga\fP process, \fBgroonga\fP
+process loads all registered plugins without \fBregister\fP command.
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+Registered plugins can be removed since Groonga 5.0.1. Use
+\fBplugin_unregister\fP in such a case.
+.UNINDENT
+.UNINDENT
+.SS Syntax
+.sp
+This command takes only one required parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+register path
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+Here is a sample that registers \fBQueryExpanderTSV\fP query expander
+that is included in
+\fB${PREFIX}/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+register query_expanders/tsv
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+You can omit \fB${PREFIX}/lib/groonga/plugins/\fP and suffix (\fB\&.so\fP).
+They are completed automatically.
+.sp
+You can specify absolute path such as \fBregister
+/usr/lib/groonga/plugins/query_expanders/tsv.so\fP\&.
+.SS Return value
+.sp
+\fBregister\fP 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 \fBregister\fP fails, error details are in \fBHEADER\fP\&.
+.sp
+See \fB/reference/command/output_format\fP for \fBHEADER\fP\&.
+.SS See also
+.INDENT 0.0
+.IP \(bu 2
+\fBplugin_register\fP
+.IP \(bu 2
+\fBplugin_unregister\fP
+.UNINDENT
+.SS \fBreindex\fP
+.SS Summary
+.sp
+New in version 5.1.0.
+.sp
+\fBreindex\fP command recreates one or more index columns.
+.sp
+If you specify a database as target object, all index columns are
+recreated.
+.sp
+If you specify a table as target object, all index columns in the
+table are recreated.
+.sp
+If you specify a data column as target object, all index columns for
+the data column are recreated.
+.sp
+If you specify an index column as target object, the index column is
+recreated.
+.sp
+This command is useful when your index column is broken. The target
+object is one of database, table and column.
+.sp
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+You can\(aqt use target index columns while \fBreindex\fP command is
+running. If you use the same database from multiple processes, all
+processes except running \fBreindex\fP should reopen the
+database. You can use \fBdatabase_unmap\fP for reopening database.
+.UNINDENT
+.UNINDENT
+.SS Syntax
+.sp
+This command takes only one optional parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+reindex [target_name=null]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If \fBtarget_name\fP parameters is omitted, database is used for the
+target object. It means that all index columns in the database are
+recreated.
+.SS Usage
+.sp
+Here is an example to recreate all index columns in the database:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+reindex
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example to recreate all index columns
+(\fBLexicon.entry_key\fP and \fBLexicon.entry_body\fP) in \fBLexicon\fP
+table:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Entry TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Entry body COLUMN_SCALAR Text
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_create Lexicon TABLE_PAT_KEY ShortText \e
+  \-\-default_tokenizer TokenBigram \e
+  \-\-normalizer NormalizerAuto
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Lexicon entry_key COLUMN_INDEX|WITH_POSITION \e
+  Entry _key
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Lexicon entry_body COLUMN_INDEX|WITH_POSITION \e
+  Entry body
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+reindex Lexicon
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example to recreate all index columns
+(\fBBigramLexicon.site_title\fP and \fBRegexpLexicon.site_title\fP) of
+\fBSite.title\fP data column:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Site TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Site title COLUMN_SCALAR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_create BigramLexicon TABLE_PAT_KEY ShortText \e
+  \-\-default_tokenizer TokenBigram \e
+  \-\-normalizer NormalizerAuto
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create BigramLexicon site_title COLUMN_INDEX|WITH_POSITION \e
+  Site title
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_create RegexpLexicon TABLE_PAT_KEY ShortText \e
+  \-\-default_tokenizer TokenRegexp \e
+  \-\-normalizer NormalizerAuto
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create RegexpLexicon site_title COLUMN_INDEX|WITH_POSITION \e
+  Site title
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+reindex Site.title
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an example to recreate an index column (\fBTimestamp.index\fP):
+.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 timestamp COLUMN_SCALAR Time
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+table_create Timestamp TABLE_PAT_KEY Time
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Timestamp logs_timestamp COLUMN_INDEX  Logs timestamp
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+reindex Timestamp.logs_timestamp
+# [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
 .UNINDENT
 .UNINDENT
-.sp
-Register \fBruby/load\fP plugin to use \fBruby_load\fP command in advance.
-.sp
-Note that \fBruby_load\fP is implemented as an experimental plugin,
-and the specification may be changed in the future.
 .SS Parameters
 .sp
 This section describes all parameters.
-.SS \fBpath\fP
+.SS \fBtarget_name\fP
 .sp
-Specifies the Ruby script path which you want to load.
+Specifies the name of table or column.
+.sp
+If you don\(aqt specify it, database is used for the target object.
+.sp
+The default is none. It means that the target object is database.
 .SS Return value
 .sp
-\fBruby_load\fP returns the loaded result with metadata such as
-exception information (Including metadata isn\(aqt implemented yet):
+\fBreindex\fP command returns whether recreation is succeeded or not:
 .INDENT 0.0
 .INDENT 3.5
 .sp
 .nf
 .ft C
-[HEADER, {"value": LOADED_VALUE}]
+[HEADER, SUCCEEDED_OR_NOT]
 .ft P
 .fi
 .UNINDENT
@@ -20224,17 +21329,1654 @@ See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
 .UNINDENT
 .UNINDENT
 .sp
-\fBLOADED_VALUE\fP
+\fBSUCCEEDED_OR_NOT\fP
 .INDENT 0.0
 .INDENT 3.5
-\fBLOADED_VALUE\fP is the loaded value of ruby script.
+If command succeeded, it returns true, otherwise it returns false on
+error.
+.UNINDENT
+.UNINDENT
+.SS \fBrequest_cancel\fP
+.SS Summary
 .sp
-\fBruby_load\fP just return \fBnull\fP as \fBLOADED_VALUE\fP for now, it will be supported in the future.
+\fBNOTE:\fP
+.INDENT 0.0
+.INDENT 3.5
+This command is an experimental feature.
+.UNINDENT
+.UNINDENT
+.sp
+New in version 4.0.9.
+.sp
+\fBrequest_cancel\fP command cancels a running request.
+.sp
+There are some limitations:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+Request ID must be managed by user. (You need to assign unique key
+for each request.)
+.IP \(bu 2
+Cancel request may be ignored. (You can send \fBrequest_cancel\fP
+command multiple times for the same request ID.)
+.IP \(bu 2
+Only multithreading type Groonga server is supported. (You can use
+with \fB/reference/executables/groonga\fP based server but can\(aqt
+use with \fB/reference/executables/groonga\-httpd\fP\&.)
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+See \fB/reference/command/request_id\fP about request ID.
+.sp
+If request is canceled, the canceled request has \fB\-5\fP
+(\fBGRN_INTERRUPTED_FUNCTION_CALL\fP) as
+\fB/reference/command/return_code\fP\&.
+.SS Syntax
+.sp
+This command takes only one required parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+request_cancel id
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+Here is an example of \fBrequest_cancel\fP command:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ curl \(aqhttp://localhost:10041/d/select?table=LargeTable&filter=true&request_id=unique\-id\-1\(aq &
+# The above "select" takes a long time...
+# Point: "request_id=unique\-id\-1"
+$ curl \(aqhttp://localhost:10041/d/request_cancel?id=unique\-id\-1\(aq
+[[...], {"id": "unique\-id\-1", "canceled": true}]
+# Point: "id=unique\-id\-1"
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Assume that the first \fBselect\fP command takes a long
+time. \fBunique\-id\-1\fP request ID is assigned to the \fBselect\fP command
+by \fBrequest_id=unique\-id\-1\fP parameter.
+.sp
+The second \fBrequest_cancel\fP command passes \fBid=unique\-id\-1\fP
+parameter. \fBunique\-id\-1\fP is the same request ID passed in \fBselect\fP
+command.
+.sp
+The \fBselect\fP command may not be canceled immediately. And the cancel
+request may be ignored.
+.sp
+You can send cancel request for the same request ID multiple times. If
+the target request is canceled or finished, \fB"canceled"\fP value is
+changed to \fBfalse\fP from \fBtrue\fP in return value:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ curl \(aqhttp://localhost:10041/d/request_cancel?id=unique\-id\-1\(aq
+[[...], {"id": "unique\-id\-1", "canceled": true}]
+# "select" is still running... ("canceled" is "true")
+$ curl \(aqhttp://localhost:10041/d/request_cancel?id=unique\-id\-1\(aq
+[[...], {"id": "unique\-id\-1", "canceled": true}]
+# "select" is still running... ("canceled" is "true")
+$ curl \(aqhttp://localhost:10041/d/request_cancel?id=unique\-id\-1\(aq
+[[...], {"id": "unique\-id\-1", "canceled": false}]
+# "select" is canceled or finished. ("canceled" is "false")
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+If the \fBselect\fP command is canceled, response of the \fBselect\fP
+command has \fB\-5\fP (\fBGRN_INTERRUPTED_FUNCTION_CALL\fP) as
+\fB/reference/command/return_code\fP:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+$ curl \(aqhttp://localhost:10041/d/select?table=LargeTable&filter=true&request_id=unique\-id\-1\(aq &
+[[\-5, ...], ...]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Parameters
+.sp
+This section describes parameters of \fBrequest_cancel\fP\&.
+.SS Required parameter
+.sp
+There is required parameter, \fBid\fP\&.
+.SS \fBid\fP
+.sp
+Specifies the ID for the target request.
+.SS Return value
+.sp
+\fBrequest_cancel\fP command returns the result of the cancel request:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[
+  HEADER,
+  {
+    "id":       ID,
+    "canceled": CANCEL_REQUEST_IS_ACCEPTED_OR_NOT
+  }
+]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBHEADER\fP
+.INDENT 0.0
+.INDENT 3.5
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
+.UNINDENT
+.UNINDENT
+.sp
+\fBID\fP
+.INDENT 0.0
+.INDENT 3.5
+The ID of the target request.
+.UNINDENT
+.UNINDENT
+.sp
+\fBCANCEL_REQUEST_IS_ACCEPTED_OR_NOT\fP
+.INDENT 0.0
+.INDENT 3.5
+If the cancel request is accepted, this is \fBtrue\fP, otherwise this
+is \fBfalse\fP\&.
+.sp
+Note that "cancel request is accepted" doesn\(aqt means that "the
+target request is canceled". It just means "cancel request is
+notified to the target request but the cancel request may be ignored
+by the target request".
+.sp
+If request assigned with the request ID doesn\(aqt exist, this is
+\fBfalse\fP\&.
 .UNINDENT
 .UNINDENT
 .SS See also
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/command/request_id\fP
+.UNINDENT
+.SS \fBruby_eval\fP
+.SS Summary
 .sp
-\fB/reference/commands/ruby_eval\fP
+\fBruby_eval\fP command evaluates Ruby script and returns the result.
+.SS Syntax
+.sp
+This command takes only one required parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+ruby_eval script
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+You can execute any scripts which mruby supports by calling \fBruby_eval\fP\&.
+.sp
+Here is an example that just calculate \fB1 + 2\fP as Ruby script.
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+register ruby/eval
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+ruby_eval "1 + 2"
+# [[0, 1337566253.89858, 0.000355720520019531], {"value": 3}]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Register \fBruby/eval\fP plugin to use \fBruby_eval\fP command in advance.
+.sp
+Note that \fBruby_eval\fP is implemented as an experimental plugin,
+and the specification may be changed in the future.
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS \fBscript\fP
+.sp
+Specifies the Ruby script which you want to evaluate.
+.SS Return value
+.sp
+\fBruby_eval\fP returns the evaluated result with metadata such as
+exception information (Including metadata isn\(aqt implemented yet):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, {"value": EVALUATED_VALUE}]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBHEADER\fP
+.INDENT 0.0
+.INDENT 3.5
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
+.UNINDENT
+.UNINDENT
+.sp
+\fBEVALUATED_VALUE\fP
+.INDENT 0.0
+.INDENT 3.5
+\fBEVALUATED_VALUE\fP is the evaludated value of \fBruby_script\fP\&.
+.sp
+\fBruby_eval\fP supports only a number for evaluated value for now.
+Supported types will be increased in the future.
+.UNINDENT
+.UNINDENT
+.SS See also
+.SS \fBruby_load\fP
+.SS Summary
+.sp
+\fBruby_load\fP command loads specified Ruby script.
+.SS Syntax
+.sp
+This command takes only one required parameter:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+ruby_load path
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+You can load any script file which mruby supports by calling \fBruby_load\fP\&.
+.sp
+Here is an example that just load \fBexpression.rb\fP as Ruby script.
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+register ruby/load
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+ruby_load "expression.rb"
+# [[0, 1337566253.89858, 0.000355720520019531], {"value": null}]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Register \fBruby/load\fP plugin to use \fBruby_load\fP command in advance.
+.sp
+Note that \fBruby_load\fP is implemented as an experimental plugin,
+and the specification may be changed in the future.
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS \fBpath\fP
+.sp
+Specifies the Ruby script path which you want to load.
+.SS Return value
+.sp
+\fBruby_load\fP returns the loaded result with metadata such as
+exception information (Including metadata isn\(aqt implemented yet):
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, {"value": LOADED_VALUE}]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+\fBHEADER\fP
+.INDENT 0.0
+.INDENT 3.5
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
+.UNINDENT
+.UNINDENT
+.sp
+\fBLOADED_VALUE\fP
+.INDENT 0.0
+.INDENT 3.5
+\fBLOADED_VALUE\fP is the loaded value of ruby script.
+.sp
+\fBruby_load\fP just return \fBnull\fP as \fBLOADED_VALUE\fP for now, it will be supported in the future.
+.UNINDENT
+.UNINDENT
+.SS See also
+.sp
+\fB/reference/commands/ruby_eval\fP
+.SS \fBschema\fP
+.SS Summary
+.sp
+New in version 5.0.9.
+.sp
+\fBschema\fP command returns schema in the database.
+.sp
+This command is useful when you want to inspect the database. For
+example, visualizing the database, creating GUI for the database and
+so on.
+.SS Syntax
+.sp
+This command takes no parameters:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+schema
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS Usage
+.sp
+Here is an example schema to show example output:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Memos TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Memos content 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 memos_content_index \e
+  COLUMN_INDEX|WITH_POSITION \e
+  Memos content
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here is an output of \fBschema\fP command against this example schema:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+schema
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   {
+#     "tables": {
+#       "Terms": {
+#         "normalizer": {
+#           "name": "NormalizerAuto"
+#         },
+#         "name": "Terms",
+#         "tokenizer": {
+#           "name": "TokenBigram"
+#         },
+#         "command": {
+#           "command_line": "table_create \-\-name Terms \-\-flags TABLE_PAT_KEY \-\-key_type ShortText \-\-default_tokenizer TokenBigram \-\-normalizer NormalizerAuto",
+#           "name": "table_create",
+#           "arguments": {
+#             "key_type": "ShortText",
+#             "default_tokenizer": "TokenBigram",
+#             "normalizer": "NormalizerAuto",
+#             "flags": "TABLE_PAT_KEY",
+#             "name": "Terms"
+#           }
+#         },
+#         "indexes": [],
+#         "key_type": {
+#           "type": "type",
+#           "name": "ShortText"
+#         },
+#         "value_type": null,
+#         "token_filters": [],
+#         "type": "patricia trie",
+#         "columns": {
+#           "memos_content_index": {
+#             "name": "memos_content_index",
+#             "weight": false,
+#             "section": false,
+#             "compress": null,
+#             "command": {
+#               "command_line": "column_create \-\-table Terms \-\-name memos_content_index \-\-flags COLUMN_INDEX|WITH_POSITION \-\-type Memos \-\-sources content",
+#               "name": "column_create",
+#               "arguments": {
+#                 "table": "Terms",
+#                 "flags": "COLUMN_INDEX|WITH_POSITION",
+#                 "name": "memos_content_index",
+#                 "sources": "content",
+#                 "type": "Memos"
+#               }
+#             },
+#             "indexes": [],
+#             "sources": [
+#               {
+#                 "table": "Memos",
+#                 "name": "content",
+#                 "full_name": "Memos.content"
+#               }
+#             ],
+#             "value_type": {
+#               "type": "reference",
+#               "name": "Memos"
+#             },
+#             "full_name": "Terms.memos_content_index",
+#             "position": true,
+#             "table": "Terms",
+#             "type": "index"
+#           }
+#         }
+#       },
+#       "Memos": {
+#         "normalizer": null,
+#         "name": "Memos",
+#         "tokenizer": null,
+#         "command": {
+#           "command_line": "table_create \-\-name Memos \-\-flags TABLE_HASH_KEY \-\-key_type ShortText",
+#           "name": "table_create",
+#           "arguments": {
+#             "key_type": "ShortText",
+#             "flags": "TABLE_HASH_KEY",
+#             "name": "Memos"
+#           }
+#         },
+#         "indexes": [],
+#         "key_type": {
+#           "type": "type",
+#           "name": "ShortText"
+#         },
+#         "value_type": null,
+#         "token_filters": [],
+#         "type": "hash table",
+#         "columns": {
+#           "content": {
+#             "name": "content",
+#             "weight": false,
+#             "section": false,
+#             "compress": null,
+#             "command": {
+#               "command_line": "column_create \-\-table Memos \-\-name content \-\-flags COLUMN_SCALAR \-\-type Text",
+#               "name": "column_create",
+#               "arguments": {
+#                 "table": "Memos",
+#                 "flags": "COLUMN_SCALAR",
+#                 "name": "content",
+#                 "type": "Text"
+#               }
+#             },
+#             "indexes": [
+#               {
+#                 "table": "Terms",
+#                 "section": 0,
+#                 "name": "memos_content_index",
+#                 "full_name": "Terms.memos_content_index"
+#               }
+#             ],
+#             "sources": [],
+#             "value_type": {
+#               "type": "type",
+#               "name": "Text"
+#             },
+#             "full_name": "Memos.content",
+#             "position": false,
+#             "table": "Memos",
+#             "type": "scalar"
+#           }
+#         }
+#       }
+#     },
+#     "normalizers": {
+#       "NormalizerNFKC51": {
+#         "name": "NormalizerNFKC51"
+#       },
+#       "NormalizerAuto": {
+#         "name": "NormalizerAuto"
+#       }
+#     },
+#     "token_filters": {},
+#     "tokenizers": {
+#       "TokenBigramSplitSymbolAlphaDigit": {
+#         "name": "TokenBigramSplitSymbolAlphaDigit"
+#       },
+#       "TokenRegexp": {
+#         "name": "TokenRegexp"
+#       },
+#       "TokenBigramIgnoreBlankSplitSymbolAlphaDigit": {
+#         "name": "TokenBigramIgnoreBlankSplitSymbolAlphaDigit"
+#       },
+#       "TokenBigram": {
+#         "name": "TokenBigram"
+#       },
+#       "TokenDelimit": {
+#         "name": "TokenDelimit"
+#       },
+#       "TokenUnigram": {
+#         "name": "TokenUnigram"
+#       },
+#       "TokenBigramSplitSymbol": {
+#         "name": "TokenBigramSplitSymbol"
+#       },
+#       "TokenDelimitNull": {
+#         "name": "TokenDelimitNull"
+#       },
+#       "TokenBigramIgnoreBlankSplitSymbolAlpha": {
+#         "name": "TokenBigramIgnoreBlankSplitSymbolAlpha"
+#       },
+#       "TokenBigramSplitSymbolAlpha": {
+#         "name": "TokenBigramSplitSymbolAlpha"
+#       },
+#       "TokenTrigram": {
+#         "name": "TokenTrigram"
+#       },
+#       "TokenMecab": {
+#         "name": "TokenMecab"
+#       },
+#       "TokenBigramIgnoreBlankSplitSymbol": {
+#         "name": "TokenBigramIgnoreBlankSplitSymbol"
+#       },
+#       "TokenBigramIgnoreBlank": {
+#         "name": "TokenBigramIgnoreBlank"
+#       }
+#     },
+#     "plugins": {},
+#     "types": {
+#       "UInt64": {
+#         "can_be_key_type": true,
+#         "name": "UInt64",
+#         "can_be_value_type": true,
+#         "size": 8
+#       },
+#       "Int32": {
+#         "can_be_key_type": true,
+#         "name": "Int32",
+#         "can_be_value_type": true,
+#         "size": 4
+#       },
+#       "Int16": {
+#         "can_be_key_type": true,
+#         "name": "Int16",
+#         "can_be_value_type": true,
+#         "size": 2
+#       },
+#       "LongText": {
+#         "can_be_key_type": false,
+#         "name": "LongText",
+#         "can_be_value_type": false,
+#         "size": 2147483648
+#       },
+#       "TokyoGeoPoint": {
+#         "can_be_key_type": true,
+#         "name": "TokyoGeoPoint",
+#         "can_be_value_type": true,
+#         "size": 8
+#       },
+#       "Text": {
+#         "can_be_key_type": false,
+#         "name": "Text",
+#         "can_be_value_type": false,
+#         "size": 65536
+#       },
+#       "ShortText": {
+#         "can_be_key_type": true,
+#         "name": "ShortText",
+#         "can_be_value_type": false,
+#         "size": 4096
+#       },
+#       "Float": {
+#         "can_be_key_type": true,
+#         "name": "Float",
+#         "can_be_value_type": true,
+#         "size": 8
+#       },
+#       "UInt8": {
+#         "can_be_key_type": true,
+#         "name": "UInt8",
+#         "can_be_value_type": true,
+#         "size": 1
+#       },
+#       "UInt32": {
+#         "can_be_key_type": true,
+#         "name": "UInt32",
+#         "can_be_value_type": true,
+#         "size": 4
+#       },
+#       "Object": {
+#         "can_be_key_type": true,
+#         "name": "Object",
+#         "can_be_value_type": true,
+#         "size": 8
+#       },
+#       "UInt16": {
+#         "can_be_key_type": true,
+#         "name": "UInt16",
+#         "can_be_value_type": true,
+#         "size": 2
+#       },
+#       "Int64": {
+#         "can_be_key_type": true,
+#         "name": "Int64",
+#         "can_be_value_type": true,
+#         "size": 8
+#       },
+#       "Time": {
+#         "can_be_key_type": true,
+#         "name": "Time",
+#         "can_be_value_type": true,
+#         "size": 8
+#       },
+#       "Bool": {
+#         "can_be_key_type": true,
+#         "name": "Bool",
+#         "can_be_value_type": true,
+#         "size": 1
+#       },
+#       "WGS84GeoPoint": {
+#         "can_be_key_type": true,
+#         "name": "WGS84GeoPoint",
+#         "can_be_value_type": true,
+#         "size": 8
+#       },
+#       "Int8": {
+#         "can_be_key_type": true,
+#         "name": "Int8",
+#         "can_be_value_type": true,
+#         "size": 1
+#       }
+#     }
+#   }
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.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
+\fBschema\fP command returns schema in the database:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+[HEADER, SCHEMA]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBHEADER\fP
+.sp
+See \fB/reference/command/output_format\fP about \fBHEADER\fP\&.
+.SS \fBSCHEMA\fP
+.sp
+\fBSCHEMA\fP is an object that consists of the following information:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "plugins":       PLUGINS,
+  "types":         TYPES,
+  "tokenizers":    TOKENIZERS,
+  "normalizers":   NORMALIZERS,
+  "token_filters": TOKEN_FITLERS,
+  "tables":        TABLES
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBPLUGINS\fP
+.sp
+\fBPLUGINS\fP is an object. Its key is plugin name and its value is
+plugin detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "PLUGIN_NAME_1": PLUGIN_1,
+  "PLUGIN_NAME_2": PLUGIN_2,
+  ...
+  "PLUGIN_NAME_n": PLUGIN_n
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBPLUGIN\fP
+.sp
+\fBPLUGIN\fP is an object that describes plugin detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "name": PLUGIN_NAME
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBPLUGIN\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The plugin name. It\(aqs used in \fBplugin_register\fP\&.
+T}
+_
+.TE
+.SS \fBTYPES\fP
+.sp
+\fBTYPES\fP is an object. Its key is type name and its value is
+type detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "TYPE_NAME_1": TYPE_1,
+  "TYPE_NAME_2": TYPE_2,
+  ...
+  "TYPE_NAME_n": TYPE_n
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBTYPE\fP
+.sp
+\fBTYPE\fP is an object that describes type detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "name": TYPE_NAME,
+  "size": SIZE_OF_ONE_VALUE_IN_BYTE,
+  "can_be_key_type": BOOLEAN,
+  "can_be_value_type": BOOLEAN
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBTYPE\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The type name.
+T}
+_
+T{
+\fBsize\fP
+T}	T{
+The number of bytes of one value.
+T}
+_
+T{
+\fBcan_be_key_type\fP
+T}	T{
+\fBtrue\fP when the type can be used for table key, \fBfalse\fP
+otherwise.
+T}
+_
+T{
+\fBcan_be_value_type\fP
+T}	T{
+\fBtrue\fP when the type can be used for table value, \fBfalse\fP
+otherwise.
+T}
+_
+.TE
+.SS \fBTOKENIZERS\fP
+.sp
+\fBTOKENIZERS\fP is an object. Its key is tokenizer name and its value
+is tokenizer detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "TOKENIZER_NAME_1": TOKENIZER_1,
+  "TOKENIZER_NAME_2": TOKENIZER_2,
+  ...
+  "TOKENIZER_NAME_n": TOKENIZER_n
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBTOKENIZER\fP
+.sp
+\fBTOKENIZER\fP is an object that describes tokenizer detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "name": TOKENIZER_NAME
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBTOKENIZER\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The tokenizer name. It\(aqs used for
+table\-create\-default\-tokenizer\&.
+T}
+_
+.TE
+.SS \fBNORMALIZERS\fP
+.sp
+\fBNORMALIZERS\fP is an object. Its key is normalizer name and its value
+is normalizer detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "NORMALIZER_NAME_1": NORMALIZER_1,
+  "NORMALIZER_NAME_2": NORMALIZER_2,
+  ...
+  "NORMALIZER_NAME_n": NORMALIZER_n
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBNORMALIZER\fP
+.sp
+\fBNORMALIZER\fP is an object that describes normalizer detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "name": NORMALIZER_NAME
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBNORMALIZER\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The normalizer name. It\(aqs used for
+table\-create\-normalizer\&.
+T}
+_
+.TE
+.SS \fBTOKEN_FILTERS\fP
+.sp
+\fBTOKEN_FILTERS\fP is an object. Its key is token filter name and its value
+is token filter detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "TOKEN_FILTER_NAME_1": TOKEN_FILTER_1,
+  "TOKEN_FILTER_NAME_2": TOKEN_FILTER_2,
+  ...
+  "TOKEN_FILTER_NAME_n": TOKEN_FILTER_n
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBTOKEN_FILTER\fP
+.sp
+\fBTOKEN_FILTER\fP is an object that describes token filter detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "name": TOKEN_FILTER_NAME
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBTOKEN_FILTER\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The token filter name. It\(aqs used for
+table\-create\-token\-filters\&.
+T}
+_
+.TE
+.SS \fBTABLES\fP
+.sp
+\fBTABLES\fP is an object. Its key is table name and its value
+is table detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "TABLE_NAME_1": TABLE_1,
+  "TABLE_NAME_2": TABLE_2,
+  ...
+  "TABLE_NAME_n": TABLE_n
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS \fBTABLE\fP
+.sp
+\fBTABLE\fP is an object that describes table detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "name": TABLE_NAME
+  "type": TYPE,
+  "key_type": KEY_TYPE,
+  "value_type": VALUE_TYPE,
+  "tokenizer": TOKENIZER,
+  "normalizer": NORMALIZER,
+  "token_filters": [
+    TOKEN_FILTER_1,
+    TOKEN_FILTER_2,
+    ...,
+    TOKEN_FILTER_n,
+  ],
+  "indexes": [
+    INDEX_1,
+    INDEX_2,
+    ...,
+    INDEX_n
+  ],
+  "command": COMMAND,
+  "columns": {
+    "COLUMN_NAME_1": COLUMN_1,
+    "COLUMN_NAME_2": COLUMN_2,
+    ...,
+    "COLUMN_NAME_3": COLUMN_3,
+  }
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBTABLE\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The table name.
+T}
+_
+T{
+\fBtype\fP
+T}	T{
+The table type.
+.sp
+This is one of the followings:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBarray\fP: table\-no\-key
+.IP \(bu 2
+\fBhash\fP: table\-hash\-key
+.IP \(bu 2
+\fBpatricia trie\fP: table\-pat\-key
+.IP \(bu 2
+\fBdouble array trie\fP: table\-dat\-key
+.UNINDENT
+.UNINDENT
+.UNINDENT
+T}
+_
+T{
+\fBkey_type\fP
+T}	T{
+The type of the table\(aqs key.
+.sp
+If the table type is \fBarray\fP, this is \fBnull\fP\&.
+.sp
+If the table type isn\(aqt \fBarray\fP, this is an object
+that has the following properties:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBname\fP: The type name.
+.IP \(bu 2
+\fBtype\fP: \fBreference\fP if the type is an table, \fBtype\fP
+otherwise.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+T}
+_
+T{
+\fBvalue_type\fP
+T}	T{
+The type of the table\(aqs value.
+.sp
+If the table doesn\(aqt use value, this is \fBnull\fP\&.
+.sp
+If the table uses value, this is an object that has the
+following properties:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBname\fP: The type name.
+.IP \(bu 2
+\fBtype\fP: \fBreference\fP if the type is an table, \fBtype\fP
+otherwise.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+T}
+_
+T{
+\fBtokenizer\fP
+T}	T{
+The tokenizer of the table. It\(aqs specified by
+table\-create\-default\-tokenizer\&.
+.sp
+If the table doesn\(aqt use tokenizer, this is \fBnull\fP\&.
+.sp
+If the table uses tokenizer, this is an object that has the
+following properties:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBname\fP: The tokenizer name.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+T}
+_
+T{
+\fBnormalizer\fP
+T}	T{
+The normalizer of the table. It\(aqs specified by
+table\-create\-normalizer\&.
+.sp
+If the table doesn\(aqt use normalizer, this is \fBnull\fP\&.
+.sp
+If the table uses normalizer, this is an object that has the
+following properties:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBname\fP: The normalizer name.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+T}
+_
+T{
+\fBtoken_filters\fP
+T}	T{
+The token filters of the table. It\(aqs specified by
+table\-create\-token\-filters\&.
+.sp
+This is an array of an object. The object has the following
+properties:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBname\fP: The token filter name.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+T}
+_
+T{
+\fBindexes\fP
+T}	T{
+The indexes of the table\(aqs key.
+.sp
+This is an array of \fI\%INDEX\fP\&.
+T}
+_
+T{
+\fBcommand\fP
+T}	T{
+The Groonga command information to create the table.
+.sp
+This is \fI\%COMMAND\fP\&.
+T}
+_
+T{
+\fBcolumns\fP
+T}	T{
+The columns of the table.
+.sp
+This is an object that its key is a column name and its value
+is \fI\%COLUMN\fP\&.
+T}
+_
+.TE
+.SS \fBINDEX\fP
+.sp
+\fBINDEX\fP is an object that describes index detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "full_name": INDEX_COLUMN_NAME_WITH_TABLE_NAME,
+  "table":     TABLE_NAME,
+  "name":      INDEX_COLUMN_NAME,
+  "section":   SECTION
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBINDEX\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBfull_name\fP
+T}	T{
+The index column name with table name.
+.sp
+For example, \fBTerms.index\fP\&.
+T}
+_
+T{
+\fBtable\fP
+T}	T{
+The table name of the index column.
+.sp
+For example, \fBTerms\fP\&.
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The index column name.
+.sp
+For example, \fBindex\fP\&.
+T}
+_
+T{
+\fBsection\fP
+T}	T{
+The section number in the index column for the table\(aqs key.
+.sp
+If the index column isn\(aqt multiple column index, this is \fB0\fP\&.
+T}
+_
+.TE
+.SS \fBCOMMAND\fP
+.sp
+\fBCOMMAND\fP is an object that describes how to create the table or
+column:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "name": COMMAND_NAME,
+  "arguments": {
+    "KEY_1": "VALUE_1",
+    "KEY_2": "VALUE_2",
+    ...,
+    "KEY_n": "VALUE_n"
+  },
+  "command_line": COMMAND_LINE
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBCOMMAND\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The Groonga command name to create the table or column.
+T}
+_
+T{
+\fBarguments\fP
+T}	T{
+The arguments of the Groonga command to create the
+table or column.
+.sp
+This is an object that its key is argument name and its value
+is argument value.
+T}
+_
+T{
+\fBcommand_line\fP
+T}	T{
+The Groonga command line to create the table or column.
+.sp
+This is a string that can be evaluated by Groonga.
+T}
+_
+.TE
+.SS \fBCOLUMN\fP
+.sp
+\fBCOLUMN\fP is an object that describes column detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "name": COLUMN_NAME,
+  "table": TABLE_NAME,
+  "full_name": COLUMN_NAME_WITH_TABLE,
+  "type": TYPE,
+  "value_type": VALUE_TYPE,
+  "compress": COMPRESS,
+  "section": SECTION,
+  "weight": WEIGHT,
+  "compress": COMPRESS,
+  "section": BOOLEAN,
+  "weight": BOOLEAN,
+  "position": BOOLEAN,
+  "sources": [
+    SOURCE_1,
+    SOURCE_2,
+    ...,
+    SOURCE_n
+  ],
+  "indexes": [
+    INDEX_1,
+    INDEX_2,
+    ...,
+    INDEX_n
+  ],
+  "command": COMMAND
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBCOLUMN\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The column name.
+.sp
+For example, \fBage\fP\&.
+T}
+_
+T{
+\fBtable\fP
+T}	T{
+The table name of the column.
+.sp
+For example, \fBUsers\fP\&.
+T}
+_
+T{
+\fBfull_name\fP
+T}	T{
+The column name with table name.
+.sp
+For example, \fBUsers.age\fP\&.
+T}
+_
+T{
+\fBtype\fP
+T}	T{
+The column type.
+.sp
+This is one of the followings:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBscalar\fP: \fB/reference/columns/scalar\fP
+.IP \(bu 2
+\fBvector\fP: \fB/reference/columns/vector\fP
+.IP \(bu 2
+\fBindex\fP: \fB/reference/columns/index\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+T}
+_
+T{
+\fBvalue_type\fP
+T}	T{
+The type of the column\(aqs value.
+.sp
+This is an object that has the following properties:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBname\fP: The type name.
+.IP \(bu 2
+\fBtype\fP: \fBreference\fP if the type is an table, \fBtype\fP
+otherwise.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+T}
+_
+T{
+\fBcompress\fP
+T}	T{
+The compression method of the column.
+.sp
+If the column doesn\(aqt use any compression methods, this is
+\fBnull\fP\&.
+.sp
+If the column uses a compression method, this is one of the
+followings:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBzlib\fP: The column uses zlib to compress column value.
+.IP \(bu 2
+\fBlz4\fP: The column uses LZ4 to compress column value.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+T}
+_
+T{
+\fBsection\fP
+T}	T{
+Whether the column can store section information or not.
+.sp
+\fBtrue\fP if the column is created with \fBWITH_SECTION\fP flag,
+\fBfalse\fP otherwise.
+.sp
+Normally, if the column isn\(aqt an index column, this is \fBfalse\fP\&.
+T}
+_
+T{
+\fBweight\fP
+T}	T{
+Whether the column can store weight information or not.
+.sp
+\fBtrue\fP if the column is created with \fBWITH_WEIGHT\fP flag,
+\fBfalse\fP otherwise.
+T}
+_
+T{
+\fBposition\fP
+T}	T{
+Whether the column can store position information or not.
+.sp
+\fBtrue\fP if the column is created with \fBWITH_POSITION\fP flag,
+\fBfalse\fP otherwise.
+.sp
+Normally, if the column isn\(aqt an index column, this is \fBfalse\fP\&.
+T}
+_
+T{
+\fBsources\fP
+T}	T{
+The source columns of the index column.
+.sp
+This is an array of \fI\%SOURCE\fP\&.
+.sp
+Normally, if the column isn\(aqt an index column, this is an
+empty array.
+T}
+_
+T{
+\fBindexes\fP
+T}	T{
+The indexes of the column.
+.sp
+This is an array of \fI\%INDEX\fP\&.
+T}
+_
+T{
+\fBcommand\fP
+T}	T{
+The Groonga command information to create the column.
+.sp
+This is \fI\%COMMAND\fP\&.
+T}
+_
+.TE
+.SS \fBSOURCE\fP
+.sp
+\fBSOURCE\fP is an object that describes source detail:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+{
+  "name":      COLUMN_NAME,
+  "table":     TABLE_NAME,
+  "full_name": COLUMN_NAME_WITH_TABLE_NAME
+}
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are properties of \fBSOURCE\fP:
+.TS
+center;
+|l|l|.
+_
+T{
+Name
+T}	T{
+Description
+T}
+_
+T{
+\fBname\fP
+T}	T{
+The source column name.
+.sp
+For example, \fBcontent\fP\&.
+.sp
+This may be a \fB_key\fP pseudo column.
+T}
+_
+T{
+\fBtable\fP
+T}	T{
+The table name of the source column.
+.sp
+For example, \fBMemos\fP\&.
+T}
+_
+T{
+\fBfull_name\fP
+T}	T{
+The source column name with table name.
+.sp
+For example, \fBMemos.content\fP\&.
+T}
+_
+.TE
+.SS See also
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBtable_create\fP
+.IP \(bu 2
+\fBcolumn_create\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS \fBselect\fP
 .SS Summary
 .sp
@@ -31902,7 +34644,7 @@ Bigram tokenize method isn\(aqt good for precision because you can find
 texts that includes query in word. For example, you can find \fBworld\fP
 by \fBor\fP\&. This is more sensitive for ASCII only languages rather than
 non\-ASCII languages. \fBTokenBigram\fP has solution for this problem
-described in the bellow.
+described in the below.
 .sp
 \fBTokenBigram\fP behavior is different when it\(aqs worked with any
 \fB/reference/normalizers\fP\&.
@@ -34766,7 +37508,7 @@ operations in \fB/reference/grn_expr/query_syntax\fP\&. You can use
 \fB/reference/commands/select\fP\&.
 .sp
 \fB/reference/grn_expr/script_syntax\fP is ECMAScript like
-syntax. You can use all condition expresssions and set operations in
+syntax. You can use all condition expressions and set operations in
 \fB/reference/grn_expr/script_syntax\fP\&. You can use
 \fB/reference/grn_expr/script_syntax\fP with \fBfilter\fP option and
 \fBscorer\fP option in \fB/reference/commands/select\fP\&.
@@ -43302,7 +46044,7 @@ Here are use cases for Groonga\(aqs geolocation search:
 .IP \(bu 2
 You list McDonald\(aqs around a station.
 .IP \(bu 2
-You list KFS around the current location sort by distance
+You list KFC around the current location sort by distance
 from the current location in ascending order with distance.
 .UNINDENT
 .sp
@@ -43403,6 +46145,434 @@ Normally, you can get converted results as expected.
 .UNINDENT
 .UNINDENT
 .UNINDENT
+.SS Configuration
+.sp
+New in version 5.1.2.
+.sp
+Groonga can manage configuration items in each database. These
+configuration items are persistent. It means that these configuration
+items are usable after a Groonga process exits.
+.SS Summary
+.sp
+You can change some Groonga behaviors such as \fB/spec/search\fP by
+some ways such as request parameter
+(select\-match\-escalation\-threshold) and build parameter
+(install\-configure\-with\-match\-escalation\-threshold).
+.sp
+Configuration is one of these ways. You can change some Groonga
+behaviors per database by configuration.
+.sp
+A configuration item consists of key and value. Both of key and value
+are string. The max key size is 4KiB. The max value size is 4091B (=
+4KiB \- 5B).
+.sp
+You can set a configuration item by
+\fB/reference/commands/config_set\fP\&.
+.sp
+You can get a configuration item by
+\fB/reference/commands/config_get\fP\&.
+.sp
+You can delete a configuration item by
+\fB/reference/commands/config_delete\fP\&.
+.sp
+You can confirm all configuration items by
+\fB/reference/commands/dump\fP\&.
+.SS Commands
+.SS Alias
+.sp
+New in version 5.1.2.
+.sp
+You can refer a table and column by multiple names by using alias
+feature.
+.SS Summary
+.sp
+The alias feature is useful for the following cases:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+You want to rename a table but you can\(aqt change some Groonga
+clients that uses the current table name.
+.IP \(bu 2
+You want to change column type without downtime.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.sp
+In the former case, some Groonga clients can use the current table
+name after you rename a table. Because the alias feature maps the
+current table name to the renamed new table name.
+.sp
+In the latter case, all Groonga clients access the column by aliased
+name such as \fBaliased_column\fP\&. \fBaliased_column\fP refers
+\fBcurrent_column\fP\&. You create a new column \fBnew_column\fP with new
+type and copy data from \fBcurrent_column\fP by
+\fB/reference/commands/column_copy\fP\&. You change \fBaliased_column\fP
+to refer \fBnew_column\fP from \fBcurrent_column\fP\&. Now, all Groonga
+clients access \fBnew_column\fP by \fBaliased_column\fP without stopping
+search requests.
+.SS Usage
+.sp
+You manage alias to real name mapping by a normal table and a normal
+column.
+.sp
+You can use any table type except table\-no\-key for the
+table. table\-hash\-key is recommended because exact key match
+search is only used for the alias feature. table\-hash\-key is
+the fastest table type for exact key match search.
+.sp
+The column must be \fB/reference/columns/scalar\fP and type is
+\fBShortText\fP\&. You can also use \fBText\fP and \fBLongText\fP types but
+they are meaningless. Because the max table/column name size is
+4KiB. \fBShortText\fP can store 4KiB data.
+.sp
+Here are example definitions of table and column for managing aliases:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Aliases TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Aliases real_name COLUMN_SCALAR ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+You need to register the table and column by \fBconfiguration\fP\&.
+The alias feature uses \fBalias.column\fP configuration item. You can
+register the table and column by the following
+\fB/reference/commands/config_set\fP:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+config_set alias.column Aliases.real_name
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Here are schema and data to show how to use alias:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+table_create Users TABLE_HASH_KEY ShortText
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+column_create Users age COLUMN_SCALAR UInt8
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+load \-\-table Users
+[
+{"_key": "alice", "age": 14},
+{"_key": "bob",   "age": 29}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 2]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+You can use \fBUsers.age\fP in \fB/reference/commands/select\fP:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+select Users \-\-filter \(aqage < 20\(aq
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         1
+#       ],
+#       [
+#         [
+#           "_id",
+#           "UInt32"
+#         ],
+#         [
+#           "_key",
+#           "ShortText"
+#         ],
+#         [
+#           "age",
+#           "UInt8"
+#         ]
+#       ],
+#       [
+#         1,
+#         "alice",
+#         14
+#       ]
+#     ]
+#   ]
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+You can\(aqt use \fBUsers.age\fP when you rename \fBUsers.age\fP to
+\fBUsers.years\fP by \fB/reference/commands/column_rename\fP:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+column_rename Users age years
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+select Users \-\-filter \(aqage < 20\(aq
+# [
+#   [
+#     \-63,
+#     1337566253.89858,
+#     0.000355720520019531,
+#     "Syntax error: <age| |< 20>",
+#     [
+#       [
+#         "yy_syntax_error",
+#         "grn_ecmascript.lemon",
+#         34
+#       ]
+#     ]
+#   ],
+#   []
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+But you can use \fBUsers.age\fP by registering \fBUsers.age\fP to
+\fBUsers.years\fP mapping to \fBAliases\fP\&.
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+load \-\-table Aliases
+[
+{"_key": "Users.age", "real_name": "Users.years"}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 1]
+select Users \-\-filter \(aqage < 20\(aq
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         1
+#       ],
+#       [
+#         [
+#           "_id",
+#           "UInt32"
+#         ],
+#         [
+#           "_key",
+#           "ShortText"
+#         ],
+#         [
+#           "years",
+#           "UInt8"
+#         ]
+#       ],
+#       [
+#         1,
+#         "alice",
+#         14
+#       ]
+#     ]
+#   ]
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Now, you can use \fBUsers.age\fP as alias of \fBUsers.years\fP\&.
+.SS How to resolve alias
+.sp
+This section describes how to resolve alias.
+.sp
+Groonga uses the alias feature when nonexistent object name (table
+name, column name, command name, function name and so on) is
+referred. It means that you can\(aqt override existing object (table,
+column, command, function and so on) by the alias feature.
+.sp
+For example, alias isn\(aqt resolved in the following example because
+\fBUsers.years\fP exists:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+column_rename Users years years_old
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+select Users \-\-filter \(aqage < 20\(aq
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         1
+#       ],
+#       [
+#         [
+#           "_id",
+#           "UInt32"
+#         ],
+#         [
+#           "_key",
+#           "ShortText"
+#         ],
+#         [
+#           "years_old",
+#           "UInt8"
+#         ]
+#       ],
+#       [
+#         1,
+#         "alice",
+#         14
+#       ]
+#     ]
+#   ]
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.sp
+Alias is resolved recursively. If you rename \fBUsers.years\fP to
+\fBUsers.years_old\fP and you refer \fBUsers.age\fP, Groonga replaces
+\fBUsers.age\fP with \fBUsers.years\fP and then \fBUsers.years\fP with
+\fBUsers.years_old\fP\&. Because \fBAliases\fP table has the following
+records:
+.TS
+center;
+|l|l|.
+_
+T{
+\fB_key\fP
+T}	T{
+\fBreal_name\fP
+T}
+_
+T{
+\fBUsers.age\fP
+T}	T{
+\fBUsers.years\fP
+T}
+_
+T{
+\fBUsers.years\fP
+T}	T{
+\fBUsers.years_old\fP
+T}
+_
+.TE
+.sp
+Here is an example to \fBUsers.age\fP is resolved recursively:
+.sp
+Execution example:
+.INDENT 0.0
+.INDENT 3.5
+.sp
+.nf
+.ft C
+column_rename Users years years_old
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+select Users \-\-filter \(aqage < 20\(aq
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         1
+#       ],
+#       [
+#         [
+#           "_id",
+#           "UInt32"
+#         ],
+#         [
+#           "_key",
+#           "ShortText"
+#         ],
+#         [
+#           "years_old",
+#           "UInt8"
+#         ]
+#       ],
+#       [
+#         1,
+#         "alice",
+#         14
+#       ]
+#     ]
+#   ]
+# ]
+.ft P
+.fi
+.UNINDENT
+.UNINDENT
+.SS See also
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/configuration\fP
+.IP \(bu 2
+\fB/reference/commands/config_set\fP
+.IP \(bu 2
+\fB/reference/commands/table_create\fP
+.IP \(bu 2
+\fB/reference/commands/column_create\fP
+.IP \(bu 2
+\fB/reference/commands/select\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
 .SS Suggest
 .sp
 Groonga has the suggest feature. This section describes how to use it and how it works.
@@ -46367,7 +49537,7 @@ Groonga. If you don\(aqt have MessagePack library, you can\(aqt use this type.
 .SS Summary
 .sp
 \fI\%grn_ctx\fP is the most important object. \fI\%grn_ctx\fP
-keeps the current infomation such as:
+keeps the current information such as:
 .INDENT 0.0
 .IP \(bu 2
 The last occurred error.
@@ -47211,7 +50381,7 @@ It estimates number of records in the rectangle specified by top_left_point para
 .INDENT 0.0
 .TP
 .B grn_obj *grn_geo_cursor_open_in_rectangle(grn_ctx\fI\ *ctx\fP, grn_obj\fI\ *index\fP, grn_obj\fI\ *top_left_point\fP, grn_obj\fI\ *bottom_right_point\fP, int\fI\ offset\fP, int\fI\ limit\fP)
-It opens a cursor to get records in the rectangle specfied by top_left_point parameter and bottom_right_point parameter.
+It opens a cursor to get records in the rectangle specified by top_left_point parameter and bottom_right_point parameter.
 .INDENT 7.0
 .TP
 .B Parameters
@@ -51600,7 +54770,7 @@ rpmパッケージのビルドに必要なパッケージをダウンロード
 .sp
 これにより、GroongaやMySQLのRPM/SRPMパッケージなどがカレントディレクトリ以下へとダウンロードされます。
 .sp
-windowsパッケージのビルドに必要なパッケージをダウンロードするには以下のコマンドを実行します。:
+Windowsパッケージのビルドに必要なパッケージをダウンロードするには以下のコマンドを実行します。:
 .INDENT 0.0
 .INDENT 3.5
 .sp
@@ -52437,6 +55607,6 @@ search
 .SH AUTHOR
 Groonga Project
 .SH COPYRIGHT
-2009-2015, Brazil, Inc
+2009-2016, Brazil, Inc
 .\" Generated by docutils manpage writer.
 .