rroonga 2.1.0-x86-mingw32 → 2.1.1-x86-mingw32

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

@@ -1,4 +1,4 @@
-.TH "GROONGA" "1" "December 27, 2012" "2.1.0" "groonga"
+.TH "GROONGA" "1" "December 29, 2012" "2.1.1" "groonga"
 .SH NAME
 groonga \- groonga documentation
 .
@@ -1489,10 +1489,10 @@ status
 #     "max_command_version": 2,
 #     "n_queries": 0,
 #     "cache_hit_rate": 0.0,
-#     "version": "2.0.5",
-#     "alloc_count": 142,
+#     "version": "2.1.0",
+#     "alloc_count": 152,
 #     "command_version": 1,
-#     "starttime": 1343713486,
+#     "starttime": 1356678603,
 #     "default_command_version": 1
 #   }
 # ]
@@ -1553,7 +1553,7 @@ A \fB/reference/commands/table_create\fP command creates a new table.
 .sp
 In most cases, a table has a primary key which must be specified with its data type and index type.
 .sp
-There are various data types such as integers, strings, etc. See also \fB/reference/type\fP for more details. The index type determines the search performance and the availability of prefix searches. The details will be described later.
+There are various data types such as integers, strings, etc. See also \fB/reference/types\fP for more details. The index type determines the search performance and the availability of prefix searches. The details will be described later.
 .sp
 Let\(aqs create a table. The following example creates a table with a primary key. The \fIname\fP parameter specifies the name of the table. The \fIflags\fP parameter specifies the index type for the primary key. The \fIkey_type\fP parameter specifies the data type of the primary key.
 .sp
@@ -2721,7 +2721,7 @@ Groonga servers don\(aqt support user authentication. Everyone can view and modi
 Groonga is a full text search engine but also serves as a column\-oriented data store. Groonga supports various data types, such as numeric types, string types, date and time type, longitude and latitude types, etc. This tutorial shows a list of data types and explains how to use them.
 .SS Overview
 .sp
-The basic data types of groonga are roughly divided into 5 groups \-\-\- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see \fB/reference/type\fP.
+The basic data types of groonga are roughly divided into 5 groups \-\-\- boolean type, numeric types, string types, date/time type and longitude/latitude types. The numeric types are further divided according to whether integer or floating point number, signed or unsigned and the number of bits allocated to each integer. The string types are further divided according to the maximum length. The longitude/latitude types are further divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP.
 .sp
 In addition, groonga supports reference types and vector types. Reference types are designed for accessing other tables. Vector types are designed for storing a variable number of values in one element.
 .sp
@@ -2795,7 +2795,7 @@ select \-\-table ToyBox \-\-output_columns _key,is_animal
 .fi
 .SS Numeric types
 .sp
-The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see \fB/reference/type\fP. The default value of the numeric types is 0.
+The numeric types are divided into integer types and a floating point number type. The integer types are further divided into the signed integer types and unsigned integer types. In addition, you can choose the number of bits allocated to each integer. For more details, see \fB/reference/types\fP. The default value of the numeric types is 0.
 .sp
 The following example creates an Int8 column and a Float column, and then updates existing records. The \fB/reference/commands/load\fP command updates the weight column as expected. On the other hand, the price column values are different from the specified values because 15.9 is not an integer and 200 is too large. 15.9 is converted to 15 by removing the fractional part. 200 causes an overflow and the result becomes \-56. Note that the result of an overflow/underflow is undefined.
 .sp
@@ -2862,7 +2862,7 @@ select \-\-table ToyBox \-\-output_columns _key,price,weight
 .fi
 .SS String types
 .sp
-The string types are divided according to the maximum length. For more details, see \fB/reference/type\fP. The default value is the zero\-length string.
+The string types are divided according to the maximum length. For more details, see \fB/reference/types\fP. The default value is the zero\-length string.
 .sp
 The following example creates a ShortText column and updates existing records. The third record has the default value because not updated.
 .sp
@@ -2976,7 +2976,7 @@ select \-\-table ToyBox \-\-output_columns _key,time
 .fi
 .SS Longitude and latitude types
 .sp
-The longitude and latitude types are divided according to the geographic coordinate system. For more details, see \fB/reference/type\fP. To represent a longitude and latitude, groonga uses a string formatted as follows:
+The longitude and latitude types are divided according to the geographic coordinate system. For more details, see \fB/reference/types\fP. To represent a longitude and latitude, groonga uses a string formatted as follows:
 .INDENT 0.0
 .IP \(bu 2
 "longitude x latitude" in milliseconds (e.g.: "128452975x503157902")
@@ -7798,7 +7798,7 @@ http {
 .fi
 .SS Custom command version
 .sp
-Groonga has \fB/reference/command_version\fP mechanism. It is for
+Groonga has \fB/reference/command/command_version\fP mechanism. It is for
 upgrading groonga commands with backward compatibility.
 .sp
 \fBgroonga\fP can change the default command veresion by
@@ -8530,6 +8530,17 @@ groongaコマンドを通してデータベースを操作する命令をコマ
 形式1でコマンドを実行する場合は、定義された順番で値を指定しなければならず、途中の引数の値を省略することはできません。形式2でコマンドを実行する場合は、「\-\-引数名」のように引数の名前を明示しなければならない代わりに、任意の順番で引数を指定することが可能で、途中の引数の指定を省略することもできます。
 .sp
 標準入力からコマンド文字列を与える場合は、コマンド名と引数名と値は、空白( )で区切ります。空白や、記号「"\(aq()」のうちいずれかを含む値を指定したい場合は、シングルクォート(\(aq)かダブルクォート(")で値を囲みます。値として指定する文字列の中では、改行文字は\(aqn\(aqに置き換えて指定します。また、引用符に使用した文字を値の中で指定する場合には、その文字の前にバックスラッシュ(\(aq\(aq) を指定します。バックスラッシュ文字自身を値として指定する場合には、その前にバックスラッシュを指定します。
+.sp
+You can write command list with continuous line which is represented by \(aq\e\(aq character.:
+.sp
+.nf
+.ft C
+table_create \-\-name Terms \e
+             \-\-flags TABLE_PAT_KEY \e
+             \-\-key_type ShortText \e
+             \-\-default_tokenizer TokenBigram
+.ft P
+.fi
 .SS 組み込みコマンド
 .sp
 以下のコマンドは組み込みコマンドとして予め定義されています。
@@ -8705,14 +8716,14 @@ Execution example:
     0.000355720520019531
   ],
   {
-    "uptime": 1,
+    "uptime": 0,
     "max_command_version": 2,
     "n_queries": 0,
     "cache_hit_rate": 0.0,
-    "version": "2.0.5",
-    "alloc_count": 142,
+    "version": "2.1.0",
+    "alloc_count": 152,
     "command_version": 1,
-    "starttime": 1343713471,
+    "starttime": 1356678595,
     "default_command_version": 1
   }
 ]
@@ -8916,7 +8927,7 @@ GETメソッドのみが使用可能です。
 .sp
 output_typeにはjson, tsv, xmlが指定可能です。
 .sp
-command_versionはコマンドの仕様の互換性を指定します。詳細は \fB/reference/command_version\fP を参照してください。
+command_versionはコマンドの仕様の互換性を指定します。詳細は \fB/reference/command/command_version\fP を参照してください。
 .SS 返値
 .sp
 output_typeの指定に従って、コマンドの実行結果を出力します。
@@ -10965,7 +10976,7 @@ You can specify absolute path such as \fBregister
 If \fBregister\fP fails, error details are in \fBHEADER\fP.
 .sp
 See \fB/reference/command/output_format\fP for \fBHEADER\fP.
-.SS select
+.SS \fBselect\fP
 .SS Summary
 .sp
 \fBselect\fP searches records that are matched to specified conditions
@@ -13477,14 +13488,14 @@ status
 #     0.000355720520019531
 #   ],
 #   {
-#     "uptime": 23,
+#     "uptime": 6,
 #     "max_command_version": 2,
 #     "n_queries": 30,
 #     "cache_hit_rate": 0.0,
-#     "version": "2.0.5",
-#     "alloc_count": 278,
+#     "version": "2.1.0",
+#     "alloc_count": 280,
 #     "command_version": 1,
-#     "starttime": 1343713421,
+#     "starttime": 1356678580,
 #     "default_command_version": 1
 #   }
 # ]
@@ -14005,139 +14016,327 @@ suggest \-\-table item_query \-\-column kana \-\-types complete|correct|suggest
 .IP \(bu 2
 \fB/reference/executables/groonga\-suggest\-create\-dataset\fP
 .UNINDENT
-.SS table_create
-.SS 名前
+.SS \fBtable_create\fP
+.SS Summary
 .sp
-table_create \- テーブルの追加
-.SS 書式
+\fBtable_create\fP creates a new table in the current database. You need
+to create one or more tables to store and search data.
+.SS Syntax
+.sp
+\fBtable_create\fP has many parameters. The required parameter is only
+\fBname\fP and otehrs are optional:
 .sp
 .nf
 .ft C
-table_create name [flags [key_type [value_type [default_tokenizer]]]]
+table_create name
+             [flags=TABLE_HASH_KEY]
+             [key_type=null]
+             [value_type=null]
+             [default_tokenizer=null]
+             [normalizer=null]
 .ft P
 .fi
-.SS 説明
+.SS Usage
 .sp
-groonga組込コマンドの一つであるtable_createについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
+\fBtable_create\fP command creates a new persistent table. See
+\fB/reference/tables\fP for table details.
+.SS Create data store table
 .sp
-table_createコマンドは、使用しているデータベースに対してテーブルを追加します。groongaには名前付きテーブルと名前なしテーブル、永続テーブルと一時テーブルがありますが、table_createコマンドでは、名前付きの永続テーブルのみが作成できます。テーブルはレコードの集合であり、全てのレコードは一意なIDを持ちます。IDはレコードを追加した順序に従って自動的に付与されます。
+You can use all table types for data store table. See
+\fB/reference/tables\fP for all table types.
 .sp
-テーブルにカラムを追加する時にはcolumn_createコマンドを使用します。また、テーブルを作成した時点でいくつかの疑似カラムが使用可能になっています。
-.SS 引数
+Table type is specified as \fBTABLE_${TYPE}\fP to \fBflags\fP parameter.
 .sp
-\fBname\fP
-.INDENT 0.0
-.INDENT 3.5
-作成するテーブルの名前を指定します。nameはデータベース内で一意な、未定義の名前でなければなりません。組込型名・組込コマンド名・組込関数名は予約済みであり、テーブル名には 使用できません。また、ピリオド(\(aq.\(aq), コロン(\(aq:\(aq)を含む名前のテーブルは作成できません。
-.UNINDENT
-.UNINDENT
+Here is an example to create \fBTABLE_NO_KEY\fP table:
 .sp
-\fBflags\fP
-.INDENT 0.0
-.INDENT 3.5
-作成するテーブルの属性を示す数値か、パイプ(\(aq|\(aq)で組み合わせたシンボル名を指定します。(デフォルト値は0(="TABLE_HASH_KEY"))
-.INDENT 0.0
-.INDENT 3.5
-.INDENT 0.0
-.TP
-.B 0, \fBTABLE_HASH_KEY\fP
-主キー値をハッシュ表で管理するテーブルを作成します。ハッシュ表を使用したテーブルでは、主キー値に完全一致するレコードを非常に高速に検索することができます。
-.TP
-.B 1, \fBTABLE_PAT_KEY\fP
-主キー値をパトリシア木で管理するテーブルを作成します。パトリシア木を使用したテーブルでは、主キー値に完全一致するレコードを検索することができるとともに、前方一致するレコード、および最長共通接頭辞となるレコードを高速に検索することができます。また、キー値の昇降順でレコードを取り出したり、キー値の範囲での検索を行うことができます。また、flagsの値に64を加えることによって、後方一致検索も可能となります。
-.TP
-.B 2, \fBTABLE_DAT_KEY\fP
-主キー値をダブル配列で管理するテーブルを作成します。ダブル配列を使用したテーブルでは、主キー値に完全一致するレコードを高速に検索することができるとともに、前方一致するレコード、および最長共通接頭辞となるレコードを検索することができます。また、キー値の昇降順でレコードを取り出したり、キー値の範囲での検索を行うことができます。
-.TP
-.B 3, \fBTABLE_NO_KEY\fP
-主キーを持たないテーブルを作成します。各レコードはIDのみによって特定することができます。
-.TP
-.B 4, \fBTABLE_VIEW\fP
-複数のテーブルをまとめて操作するための仮想的なテーブル(view)を作成します。
-.TP
-.B 64, \fBKEY_WITH_SIS\fP
-語彙表となるパトリシア木型のテーブルにおいて、後方一致検索を可能とします。
-.TP
-.B 128, \fBKEY_NORMALIZE\fP
-ハッシュ表型か、パトリシア木型のテーブルにおいて、主キー値を正規化した上で登録します。この値が指定されたテーブルではたとえば、主キー値\(aqabc\(aqと\(aqABC\(aq は同一のレコードに対応するものとみなされます。
-.UNINDENT
-.UNINDENT
-.UNINDENT
-.UNINDENT
-.UNINDENT
+Execution example:
 .sp
-\fBkey_type\fP
-.INDENT 0.0
-.INDENT 3.5
-主キー値の型を指定します。主キー値を持つテーブルに限り有効です。型にはgroongaの組込型か、同一データベースに定義済みのユーザ定義型、定義済みのテーブルを指定することができます。
-.UNINDENT
-.UNINDENT
+.nf
+.ft C
+table_create Logs TABLE_NO_KEY
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
 .sp
-\fBvalue_type\fP
-.INDENT 0.0
-.INDENT 3.5
-値の型を指定します。tableの値には固定長の型のみが指定できます。(可変長の値が必要な場合は別途カラムを作成します) 型にはgroongaの組込型か、同一データベースに定義済みのユーザ定義型、またはテーブルを指定することができます。(デフォルトはvalueなし)
-.UNINDENT
-.UNINDENT
+The \fBtable_create\fP command creates a table that is named \fBLogs\fP
+and is \fBTABLE_NO_KEY\fP type.
 .sp
-\fBdefault_tokenizer\fP
-.INDENT 0.0
-.INDENT 3.5
-作成するテーブルを語彙表として使用する場合、文字列を分割するトークナイザを指定します。
+If your records aren\(aqt searched by key, \fBTABLE_NO_KEY\fP type table is
+suitable. Because \fBTABLE_NO_KEY\fP doesn\(aqt support key but it is fast
+and small table. Storing logs into groonga database is the case.
 .sp
-組込のトークナイザとして、以下が準備されています。
+If your records are searched by key or referenced by one or more
+columns, \fBTABLE_NO_KEY\fP type isn\(aqt suitable. Lexicon for fulltext
+search is the case.
+.SS Create lexicon table
+.sp
+You can use all table types except \fBTABLE_NO_KEY\fP for lexicon table.
+Lexicon table needs key support but \fBTABLE_NO_KEY\fP doesn\(aqt support
+key.
+.sp
+Here is an example to create \fBTABLE_PAT_KEY\fP table:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create Lexicon TABLE_PAT_KEY ShortText \-\-default_tokenizer TokenBigram \-\-normalizer NormalizerAuto
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.sp
+The \fBtable_create\fP command creates the following table:
 .INDENT 0.0
-.TP
-.B \fBTokenDelimit\fP
-空白で区切られた文字列をトークンとする
-.TP
-.B \fBTokenUnigram\fP
-unigram(1文字を1トークンとする)
-.TP
-.B \fBTokenBigram\fP
-bigram(2文字の文字列要素をトークンとする)
-.TP
-.B \fBTokenTrigram\fP
-trigram(3文字の文字列要素をトークンとする)
-.TP
-.B \fBTokenMecab\fP
-形態素解析器mecabで解析した形態素をトークンとする。(mecabを組み込んだ場合のみ有効)
+.IP \(bu 2
+The table is named \fBLexicon\fP.
+.IP \(bu 2
+The table is \fBTABLE_PAT_KEY\fP type table.
+.IP \(bu 2
+The table\(aqs key is \fBShortText\fP type.
+.IP \(bu 2
+The table uses \fBTokenBigram\fP tokenizer to extract tokens from a
+normalized text.
+.IP \(bu 2
+The table uses \fBNormalizerAuto\fP normalizer to normalize a text.
 .UNINDENT
 .sp
-トークナイザが指定されなかった場合は、対象の文字列を分割せずに語彙表に登録します。
-.UNINDENT
-.UNINDENT
-.SS 返値
-.SS json形式
+\fBTABLE_PAT_KEY\fP is suitable table type for lexicon table. Lexicon
+table is used for fulltext search.
+.sp
+In fulltext search, predictive search may be used for fuzzy
+search. Predictive search is supported by \fBTABLE_PAT_KEY\fP and
+\fBTABLE_DAT_KEY\fP.
+.sp
+Lexicon table has many keys because a fulltext target text has many
+tokens. Table that has many keys should consider table size because
+large table requires large memory. Requiring large memory causes disk
+I/O. It blocks fast search. So table size is important for a table
+that has many keys. \fBTABLE_PAT_KEY\fP is less table size than
+\fBTABLE_DAT_KEY\fP.
+.sp
+Because of the above reasons, \fBTABLE_PAT_KEY\fP is suitable table type
+for lexicon table.
+.SS Create tag index table
+.sp
+You can use all table types except \fBTABLE_NO_KEY\fP for tag index
+table. Tag index table needs key support but \fBTABLE_NO_KEY\fP doesn\(aqt
+support key.
+.sp
+Here is an example to create \fBTABLE_HASH_KEY\fP table:
+.sp
+Execution example:
 .sp
 .nf
 .ft C
-[成功かどうかのフラグ]
-
-\(ga\(ga成功かどうかのフラグ\(ga\(ga
-
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
+table_create Ages TABLE_DAT_KEY UInt32
+# [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
-.SS 例
 .sp
-ShortText型の主キーを持つハッシュ表型のテーブル、Entryを作成します。:
+The \fBtable_create\fP command creates a table that is named \fBTags\fP,
+is \fBTABLE_HASH_KEY\fP type and has \fBShortText\fP type key.
+.sp
+\fBTABLE_HASH_KEY\fP or \fBTABLE_DAT_KEY\fP are suitable table types for
+tag index table.
+.sp
+If you need only exact match tag search feature, \fBTABLE_HASH_KEY\fP is
+suitable. It is the common case.
+.sp
+If you also need predictive tag search feature (for example, searching
+\fB"groonga"\fP by \fB"gr"\fP keyword.), \fBTABLE_DAT_KEY\fP is suitable.
+\fBTABLE_DAT_KEY\fP is large table size but it is not important because
+the number of tags will not be large.
+.SS Create range index table
+.sp
+You can use \fBTABLE_PAT_KEY\fP and \fBTABLE_DAT_KEY\fP table types for
+range index table. Range index table needs range search support but
+\fBTABLE_NO_KEY\fP and \fBTABLE_HASH_KEY\fP don\(aqt support it.
+.sp
+Here is an example to create \fBTABLE_DAT_KEY\fP table:
+.sp
+Execution example:
 .sp
 .nf
 .ft C
-table_create Entry \-\-key_type ShortText
-[true]
+table_create Ages TABLE_DAT_KEY UInt32
+# [[0, 1337566253.89858, 0.000355720520019531], true]
 .ft P
 .fi
 .sp
-ShortText型の主キーを持つパトリシア木型のテーブル、Termを作成します。主キー値は正規化して管理します。また、このテーブルを語彙表とする転置索引を作成する場合には、バイグラムの索引を作成します。:
+The \fBtable_create\fP command creates a table that is named \fBAges\fP,
+is \fBTABLE_DAT_KEY\fP type and has \fBUInt32\fP type key.
+.sp
+\fBTABLE_PAT_KEY\fP and \fBTABLE_DAT_KEY\fP are suitable table types for
+range index table.
+.sp
+If you don\(aqt have many indexed items, \fBTABLE_DAT_KEY\fP is
+suitable. Index for age is the case in the above example. Index for
+age will have only 0\-100 items because human doesn\(aqt live so long.
+.sp
+If you have many indexed items, \fBTABLE_PAT_KEY\fP is suitable. Because
+\fBTABLE_PAT_KEY\fP is smaller than \fBTABLE_DAT_KEY\fP.
+.SS Parameters
+.sp
+This section describes all parameters.
+.SS \fBname\fP
+.sp
+It specifies a table name to be created. \fBname\fP must be specified.
+.sp
+Here are available characters:
+.INDENT 0.0
+.IP \(bu 2
+\fB0\fP .. \fB9\fP (digit)
+.IP \(bu 2
+\fBa\fP .. \fBz\fP (alphabet, lower case)
+.IP \(bu 2
+\fBA\fP .. \fBZ\fP (alphabet, upper case)
+.IP \(bu 2
+\fB#\fP (hash)
+.IP \(bu 2
+\fB@\fP (at mark)
+.IP \(bu 2
+\fB\-\fP (hyphen)
+.IP \(bu 2
+\fB_\fP (underscore) (NOTE: Underscore can\(aqt be used as the first
+character.)
+.UNINDENT
+.sp
+You need to create a name with one or more the above chracters. Note
+that you cannot use \fB_\fP as the first charcter such as
+\fB_name\fP.
+.SS \fBflags\fP
+.sp
+It specifies a table type and table customize options.
+.sp
+Here are available flags:
+.TS
+center;
+|l|l|.
+_
+T{
+flags
+T}	T{
+description
+T}
+_
+T{
+\fBTABLE_NO_KEY\fP
+T}	T{
+Array table.
+T}
+_
+T{
+\fBTABLE_HASH_HEY\fP
+T}	T{
+Hash table.
+T}
+_
+T{
+\fBTABLE_PAT_KEY\fP
+T}	T{
+Patricia trie.
+T}
+_
+T{
+\fBTABLE_DAT_KEY\fP
+T}	T{
+Double Array trie.
+T}
+_
+T{
+\fBKEY_WITH_SIS\fP
+T}	T{
+Enable Semi Infinite String.
+Require \fBTABLE_PAT_KEY\fP.
+T}
+_
+.TE
+.IP Note
+Since groonga 2.1.0 \fBKEY_NORMALIZE\fP flag is deprecated. Use
+\fBnormalizer\fP option with \fBNormalizerAuto\fP instead.
+.RE
+.sp
+You must specify one of \fBTABLE_${TYPE}\fP flags. You cannot specify two
+or more \fBTABLE_${TYPE}\fP flags. For example,
+\fBTABLE_NO_KEY|TABLE_HASH_KEY\fP is invalid.
+.sp
+You can combine flags with \fB|\fP (vertical bar) such as
+\fBTABLE_PAT_KEY|KEY_WITH_SIS\fP.
+.sp
+See \fB/reference/tables\fP for difference between table types.
+.sp
+The default flags are \fBTABLE_HASH_KEY\fP.
+.SS \fBkey_type\fP
+.sp
+It specifies key type.
+.sp
+If you specify \fBTABLE_HASH_KEY\fP, \fBTABLE_PAT_KEY\fP or
+\fBTABLE_DAT_KEY\fP as \fBflags\fP parameter, you need to specify
+\fBkey_type\fP option.
+.sp
+See \fB/reference/types\fP for all types.
+.sp
+The default value is none.
+.SS \fBvalue_type\fP
+.sp
+It specifies value type.
+.sp
+You can use value when you specify \fBTABLE_NO_KEY\fP,
+\fBTABLE_HASH_KEY\fP or \fBTABLE_PAT_KEY\fP as \fBflags\fP parameter. Value
+type must be a fixed size type. For example, \fBUInt32\fP can be used
+but \fBShortText\fP cannot be used. Use columns instead of value.
+.sp
+The default value is none.
+.SS \fBdefault_tokenizer\fP
+.sp
+It specifies the default tokenizer that is used on searching and data
+loading.
+.sp
+You cannot use \fBdefault_tokenizer\fP with \fBTABLE_NO_KEY\fP because
+\fBTABLE_NO_KEY\fP cannot be used for index.
+.sp
+You must specify \fBdefault_tokenizer\fP for a table that is used for
+fulltext search index.
+.sp
+See \fB/reference/tokenizers\fP for all tokenizers
+.sp
+The default value is none.
+.SS \fBnormalizer\fP
+.sp
+It specifies a normalizer that is used to normalize key.
+.sp
+You cannot use \fBnormalizer\fP with \fBTABLE_NO_KEY\fP because
+\fBTABLE_NO_KEY\fP doesn\(aqt support key.
+.sp
+See \fB/reference/normalizers\fP for all normalizsers.
+.sp
+The default value is none.
+.SS Return value
+.sp
+\fBtable_create\fP returns \fBtrue\fP as body on success such as:
 .sp
 .nf
 .ft C
-table_create Term \-\-flags TABLE_PAT_KEY|KEY_NORMALIZE \-\-key_type ShortText \-\-default_tokenizer TokenBigram
-[true]
+[HEADER, true]
 .ft P
 .fi
+.sp
+If \fBtable_create\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
+\fB/reference/tables\fP
+.IP \(bu 2
+\fB/reference/commands/column_create\fP
+.IP \(bu 2
+\fB/reference/tokenizers\fP
+.IP \(bu 2
+\fB/reference/normalizers\fP
+.IP \(bu 2
+\fB/reference/command/output_format\fP
+.UNINDENT
 .SS table_list
 .SS 名前
 .sp
@@ -14269,63 +14468,55 @@ table_list
 #       [
 #         "range",
 #         "ShortText"
+#       ],
+#       [
+#         "default_tokenizer",
+#         "ShortText"
+#       ],
+#       [
+#         "normalizer",
+#         "ShortText"
 #       ]
 #     ],
 #     [
 #       259,
-#       "bigram",
-#       "/tmp/groonga\-databases/suggest.0000103",
-#       "TABLE_PAT_KEY|KEY_NORMALIZE|PERSISTENT",
-#       "ShortText",
-#       "null"
-#     ],
-#     [
-#       278,
-#       "event_query",
-#       "/tmp/groonga\-databases/suggest.0000116",
-#       "TABLE_NO_KEY|PERSISTENT",
-#       "null",
-#       "null"
+#       "Ages",
+#       "/tmp/groonga\-databases/commands_table_create.0000103",
+#       "TABLE_DAT_KEY|PERSISTENT",
+#       "UInt32",
+#       null,
+#       null,
+#       null
 #     ],
 #     [
-#       258,
-#       "event_type",
-#       "/tmp/groonga\-databases/suggest.0000102",
-#       "TABLE_HASH_KEY|PERSISTENT",
+#       257,
+#       "Lexicon",
+#       "/tmp/groonga\-databases/commands_table_create.0000101",
+#       "TABLE_PAT_KEY|PERSISTENT",
 #       "ShortText",
-#       "null"
+#       null,
+#       "TokenBigram",
+#       "NormalizerAuto"
 #     ],
 #     [
-#       261,
-#       "item_query",
-#       "/tmp/groonga\-databases/suggest.0000105",
-#       "TABLE_PAT_KEY|KEY_NORMALIZE|PERSISTENT",
-#       "ShortText",
-#       "null"
-#     ],
-#     [
-#       260,
-#       "kana",
-#       "/tmp/groonga\-databases/suggest.0000104",
-#       "TABLE_PAT_KEY|KEY_NORMALIZE|PERSISTENT",
-#       "ShortText",
-#       "null"
-#     ],
-#     [
-#       270,
-#       "pair_query",
-#       "/tmp/groonga\-databases/suggest.000010E",
-#       "TABLE_HASH_KEY|PERSISTENT",
-#       "UInt64",
-#       "null"
+#       256,
+#       "Logs",
+#       "/tmp/groonga\-databases/commands_table_create.0000100",
+#       "TABLE_NO_KEY|PERSISTENT",
+#       null,
+#       null,
+#       null,
+#       null
 #     ],
 #     [
-#       277,
-#       "sequence_query",
-#       "/tmp/groonga\-databases/suggest.0000115",
+#       258,
+#       "Tags",
+#       "/tmp/groonga\-databases/commands_table_create.0000102",
 #       "TABLE_HASH_KEY|PERSISTENT",
 #       "ShortText",
-#       "null"
+#       null,
+#       null,
+#       null
 #     ]
 #   ]
 # ]
@@ -14586,6 +14777,444 @@ groongaのカラムは、ある型のベクターを保存することができ
 脚注
 .IP [1] 5
 Object型はv1.2でサポートされます。
+.SS Tables
+.SS Summary
+.sp
+Table in groonga manages relation between ID and key. Groonga provides
+four table types. They are \fBTABLE_NO_KEY\fP, \fBTABLE_HASH_KEY\fP,
+\fBTABLE_PAT_KEY\fP and \fBTABLE_DAT_KEY\fP.
+.sp
+All table except \fBTABLE_NO_KEY\fP provides both fast ID search by key
+and fast key search by ID. \fBTABLE_NO_KEY\fP doesn\(aqt support
+key. \fBTABLE_NO_KEY\fP only manages ID. So \fBTABLE_NO_KEY\fP doesn\(aqt
+provides ID search and key search.
+.SS Characteristics
+.sp
+Here is a chracteristic table of all tables in groonga. (\fBTABLE_\fP
+prefix is omitted in the table.)
+.TS
+center;
+|l|l|l|l|l|.
+_
+T{
+T}	T{
+\fBNO_KEY\fP
+T}	T{
+\fBHASH_KEY\fP
+T}	T{
+\fBPAT_KEY\fP
+T}	T{
+\fBDAT_KEY\fP
+T}
+_
+T{
+Data
+structure
+T}	T{
+Array
+T}	T{
+Hash table
+T}	T{
+Patricia
+trie
+T}	T{
+Double
+array
+trie
+T}
+_
+T{
+ID
+support
+T}	T{
+o
+T}	T{
+o
+T}	T{
+o
+T}	T{
+o
+T}
+_
+T{
+Key
+support
+T}	T{
+x
+T}	T{
+o
+T}	T{
+o
+T}	T{
+o
+T}
+_
+T{
+Value
+support
+T}	T{
+o
+T}	T{
+o
+T}	T{
+o
+T}	T{
+x
+T}
+_
+T{
+Key \-> ID
+speed
+(o \-> fast)
+(x \-> slow)
+T}	T{
+.INDENT 0.0
+.IP \(bu 2
+.UNINDENT
+T}	T{
+oo
+T}	T{
+x
+T}	T{
+o
+T}
+_
+T{
+Update
+speed
+(o \-> fast)
+(x \-> slow)
+T}	T{
+ooo
+T}	T{
+o
+T}	T{
+o
+T}	T{
+x
+T}
+_
+T{
+Size
+(o \-> small)
+(x \-> large)
+T}	T{
+ooo
+T}	T{
+o
+T}	T{
+oo
+T}	T{
+x
+T}
+_
+T{
+Key
+update
+T}	T{
+.INDENT 0.0
+.IP \(bu 2
+.UNINDENT
+T}	T{
+x
+T}	T{
+x
+T}	T{
+o
+T}
+_
+T{
+Common
+prefix
+search
+T}	T{
+.INDENT 0.0
+.IP \(bu 2
+.UNINDENT
+T}	T{
+x
+T}	T{
+o
+T}	T{
+o
+T}
+_
+T{
+Predictive
+search
+T}	T{
+.INDENT 0.0
+.IP \(bu 2
+.UNINDENT
+T}	T{
+x
+T}	T{
+o
+T}	T{
+o
+T}
+_
+T{
+Range
+search
+T}	T{
+.INDENT 0.0
+.IP \(bu 2
+.UNINDENT
+T}	T{
+x
+T}	T{
+o
+T}	T{
+o
+T}
+_
+.TE
+.SS \fBTABLE_NO_KEY\fP
+.sp
+\fBTABLE_NO_KEY\fP is very fast and very small but it doesn\(aqt support
+key. \fBTABLE_NO_KEY\fP is a only table that doesn\(aqt support key.
+.sp
+You cannot use \fBTABLE_NO_KEY\fP for lexicon for fulltext search
+because lexicon stores tokens as key. \fBTABLE_NO_KEY\fP is useful for
+no key records such as log.
+.SS \fBTABLE_HASH_KEY\fP
+.sp
+\fBTABLE_HASH_KEY\fP is fast but it doesn\(aqt support advanced search
+functions such as common prefix search and predictive search.
+.sp
+\fBTABLE_HASH_KEY\fP is useful for index for exact search such as tag
+search.
+.SS \fBTABLE_PAT_KEY\fP
+.sp
+\fBTABLE_PAT_KEY\fP is small and supports advanced search functions.
+.sp
+\fBTABLE_PAT_KEY\fP is useful for lexicon for fulltext search and
+index for range search.
+.SS \fBTABLE_DAT_KEY\fP
+.sp
+\fBTABLE_DAT_KEY\fP is fast and supports key update but it is large. It
+is not suitable for storing many records. \fBTABLE_DAT_KEY\fP is a only
+table that supports key update.
+.sp
+\fBTABLE_DAT_KEY\fP is used in groonga database. Groonga database needs
+to convert object name such as \fBShortText\fP, \fBTokenBigram\fP and
+table names to object ID. And groonga database needs to rename object
+name. Those features are implemented by \fBTABLE_DAT_KEY\fP. The number
+of objects is small. So large data size demerit of \fBTABLE_DAT_KEY\fP
+can be ignored.
+.SS Record ID
+.sp
+Record ID is assigned automatically. You cannot assign record ID.
+.sp
+Record ID of deleted record may be reused.
+.sp
+Valid record ID range is between 1 and 268435455. (1 and 268435455 are
+valid IDs.)
+.SS Persistent table and temporary table
+.sp
+Table is persistent table or temporary table.
+.SS Persistent table
+.sp
+Persistent table is named and registered to database. Records in
+persistent table aren\(aqt deleted after closing table or
+database.
+.sp
+Persistent table can be created by
+\fB/reference/commands/table_create\fP command.
+.SS Temporary table
+.sp
+Temporary table is anonymous. Records in temporary table are deleted
+after closing table. Temporary table is used to store search result,
+sort result, group (drilldown) result and so on. \fBTABLE_HASH_KEY\fP is
+used for search result and group result. \fBTABLE_NO_KEY\fP is used for
+sort result.
+.SS Limitations
+.sp
+The max number of records is 268435455. You cannot add 268435456 or
+more records in a table.
+.sp
+The max number of a key size is 4096byte. You cannot use 4097byte or
+larger key. You can use column instead of key for 4097byte or larger
+size data. \fBText\fP and \fBLargeText\fP types supports 4097byte or
+larger size data.
+.sp
+The max number of total key size is 4GiB. You need to split a table,
+split a database (sharding) or reduce each key size to handle 4GiB or
+more larger total key size.
+.SS See also
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/commands/table_create\fP
+.UNINDENT
+.SS Normalizers
+.SS Summary
+.sp
+Groonga has normalizer module. It is used when tokenizing text and
+storing table key. For example, \fBA\fP and \fBa\fP are processed as the
+same character after normalization.
+.sp
+Normalizer module can be added as a plugin. You can customize text
+normalization by registering your normalizer plugins to groonga.
+.sp
+A normalizer module is attached to a table. A table can have zero or
+one normalizer module. You can attach a normalizer module to a table
+by \fItable\-create\-normalizer\fP option in
+\fB/reference/commands/table_create\fP.
+.sp
+Here is an example \fBtable_create\fP that uses \fBNormalizerAuto\fP
+normalizer module:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create Dictionary TABLE_HASH_KEY ShortText \-\-normalizer NormalizerAuto
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.IP Note
+Groonga 2.0.9 or earlier doesn\(aqt have \fB\-\-normalizer\fP option in
+\fBtable_create\fP. \fBKEY_NORMALIZE\fP flag was used instead.
+.sp
+You can open an old database by groonga 2.1.0 or later. An old
+database means that the database is created by groonga 2.0.9 or
+earlier. But you cannot open the opened old database by groonga
+2.0.9 or earlier. Once you open the old database by groonga 2.1.0
+or later, \fBKEY_NORMALIZE\fP flag information in the old database is
+converted to normalizer information. So groogna 2.0.9 or earlier
+cannot find \fBKEY_NORMALIZE\fP flag information in the opened old
+database.
+.RE
+.sp
+Keys of a table that has a normalizer module are normalized:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+load \-\-table Dictionary
+[
+{"_key": "Apple"},
+{"_key": "black"},
+{"_key": "COLOR"}
+]
+# [[0, 1337566253.89858, 0.000355720520019531], 3]
+select Dictionary
+# [
+#   [
+#     0,
+#     1337566253.89858,
+#     0.000355720520019531
+#   ],
+#   [
+#     [
+#       [
+#         3
+#       ],
+#       [
+#         [
+#           "_id",
+#           "UInt32"
+#         ],
+#         [
+#           "_key",
+#           "ShortText"
+#         ]
+#       ],
+#       [
+#         1,
+#         "apple"
+#       ],
+#       [
+#         2,
+#         "black"
+#       ],
+#       [
+#         3,
+#         "color"
+#       ]
+#     ]
+#   ]
+# ]
+.ft P
+.fi
+.sp
+\fBNormalizerAuto\fP normalizer normalizes a text as a downcased text.
+For example, \fB"Apple"\fP is normalized to \fB"apple"\fP, \fB"black"\fP is
+normalized to \fB"blank"\fP and \fB"COLOR"\fP is normalized to
+\fB"color"\fP.
+.sp
+If a table is a lexicon for fulltext search, tokenized tokens are
+normalized. Because tokens are stored as table keys. Table keys are
+normalized as described above.
+.SS Built\-in normalizers
+.sp
+Here is a list of built\-in\-normalizers:
+.INDENT 0.0
+.INDENT 3.5
+.INDENT 0.0
+.IP \(bu 2
+\fBNormalizerAuto\fP
+.IP \(bu 2
+\fBNormalizerNFKC51\fP
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.SS \fBNormalizerAuto\fP
+.sp
+Normally you should use \fBNormalizerAuto\fP
+normalizer. \fBNormalizerAuto\fP was the normalizer for groonga 2.0.9 or
+earlier. \fBKEY_NORMALIZE\fP flag in \fBtable_create\fP on groonga 2.0.9
+or earlier equals to \fB\-\-normalizer NormalizerAuto\fP option in
+\fBtable\fP on groonga 2.1.0 or later.
+.sp
+\fBNormalizerAuto\fP supports all encoding. It uses Unicode NFKC
+(Normalization Form Compatibility Composition) for UTF\-8 encoding
+text. It uses encoding specific original normalization for other
+encodings. The results of those original normalization are similar to
+NFKC.
+.sp
+For example, half\-width katakana (such as U+FF76 HALFWIDTH KATAKANA
+LETTER KA) + half\-width katakana voiced sound mark (U+FF9E HALFWIDTH
+KATAKANA VOICED SOUND MARK) is normalized to full\-width katakana with
+voiced sound mark (U+30AC KATAKANA LETTER GA). The former is two
+chracters but the latter is one character.
+.sp
+Here is an example that uses \fBNormalizerAuto\fP normalizer:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create NormalLexicon TABLE_HASH_KEY ShortText \-\-normalizer NormalizerAuto
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.SS \fBNormalizerNFKC51\fP
+.sp
+\fBNormalizerNFKC51\fP normalizes texts by Unicode NFKC (Normalization
+Form Compatibility Composition) for Unicode version 5.1. It supports
+only UTF\-8 encoding.
+.sp
+Normally you don\(aqt need to use \fBNormalizerNFKC51\fP explicitly. You can
+use \fBNormalizerAuto\fP instead.
+.sp
+Here is an example that uses \fBNormalizerNFKC51\fP normalizer:
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+table_create NFKC51Lexicon TABLE_HASH_KEY ShortText \-\-normalizer NormalizerNFKC51
+# [[0, 1337566253.89858, 0.000355720520019531], true]
+.ft P
+.fi
+.SS See also
+.INDENT 0.0
+.IP \(bu 2
+\fB/reference/commands/table_create\fP
+.UNINDENT
 .SS Tokenizers
 .sp
 TODO: Write me.
@@ -16600,7 +17229,7 @@ Its syntax is \fBname(arugment1, argument2, ...)\fP.
 \fBname(argument1, argument2, ...)\fP calls a function that is named
 \fBname\fP with arguments \fBargument1\fP, \fBargument2\fP and \fB...\fP.
 .sp
-See \fB/reference/functions/\fP for available functin list.
+See \fB/reference/function\fP for available functin list.
 .sp
 Here is a simple exmaple.
 .sp
@@ -18459,7 +19088,7 @@ you want to calculate the value of distance between two points.
 .sp
 You can specify the value of GeoPoint type. [1]
 .sp
-See \fB/reference/type\fP about GeoPoint.
+See \fB/reference/types\fP about GeoPoint.
 .SS \fBpoint2\fP
 .sp
 It specifies the end point that
@@ -18468,7 +19097,7 @@ you want to calculate the value of distance between two points.
 You can specify the value of GeoPoint type or
 the string indicating the coordinate.
 .sp
-See \fB/reference/type\fP about GeoPoint and the coordinate.
+See \fB/reference/types\fP about GeoPoint and the coordinate.
 .SS Optional parameter
 .sp
 There is a optional parameter, \fBapproximate_type\fP.