rroonga 2.0.0-x86-mingw32 → 2.0.1-x86-mingw32

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

@@ -1,4 +1,4 @@
-.TH "GROONGA" "1" "February 28, 2012" "2.0.0" "groonga"
+.TH "GROONGA" "1" "March 29, 2012" "2.0.0" "groonga"
 .SH NAME
 groonga \- groonga documentation
 .
@@ -106,6 +106,16 @@ Install:
 .ft P
 .fi
 .sp
+If you want to use \fI\%MeCab\fP as a tokenizer. please install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.sp
+.nf
+.ft C
+% sudo aptitude \-V \-D \-y install groonga\-tokenizer\-mecab
+.ft P
+.fi
+.sp
 There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
 .sp
 Install groonga\-munin\-plugins package:
@@ -136,6 +146,18 @@ Install:
 .ft P
 .fi
 .sp
+If you want to use \fI\%MeCab\fP as a tokenizer. please install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.sp
+.nf
+.ft C
+% sudo aptitude \-V \-D \-y install groonga\-tokenizer\-mecab
+.ft P
+.fi
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
+.sp
 Install groonga\-munin\-plugins package:
 .sp
 .nf
@@ -164,6 +186,18 @@ Install:
 .ft P
 .fi
 .sp
+If you want to use \fI\%MeCab\fP as a tokenizer. please install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.sp
+.nf
+.ft C
+% sudo aptitude \-V \-D \-y install groonga\-tokenizer\-mecab
+.ft P
+.fi
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
+.sp
 Install groonga\-munin\-plugins package:
 .sp
 .nf
@@ -196,6 +230,18 @@ Install:
 .ft P
 .fi
 .sp
+If you want to use \fI\%MeCab\fP as a tokenizer. please install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-tokenizer\-mecab
+.ft P
+.fi
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
+.sp
 Install groonga\-munin\-plugins package:
 .sp
 .nf
@@ -228,6 +274,18 @@ Install:
 .ft P
 .fi
 .sp
+If you want to use \fI\%MeCab\fP as a tokenizer. please install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-tokenizer\-mecab
+.ft P
+.fi
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
+.sp
 Install groonga\-munin\-plugins package:
 .sp
 .nf
@@ -260,6 +318,18 @@ Install:
 .ft P
 .fi
 .sp
+If you want to use \fI\%MeCab\fP as a tokenizer. please install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.sp
+.nf
+.ft C
+% sudo apt\-get \-y install groonga\-tokenizer\-mecab
+.ft P
+.fi
+.sp
+There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
+.sp
 Install groonga\-munin\-plugins package:
 .sp
 .nf
@@ -279,11 +349,21 @@ Install:
 .ft P
 .fi
 .sp
+If you want to use \fI\%MeCab\fP as a tokenizer. please install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.sp
+.nf
+.ft C
+% sudo yum install \-y groonga\-tokenizer\-mecab
+.ft P
+.fi
+.sp
 There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
 .IP Note
-Groonga\-munin\-plugins package requires munin\-node package that isn\(aqt included in the official CentOS repository. You need to enable \fI\%RPMforge\fP repository or \fI\%EPEL\fP repository to install it by yum.
+Groonga\-munin\-plugins package requires munin\-node package that isn\(aqt included in the official CentOS repository. You need to enable \fI\%Repoforge (RPMforge)\fP repository or \fI\%EPEL\fP repository to install it by yum.
 .sp
-Enable RPMforge repository on i386 environment:
+Enable Repoforge (RPMforge) repository on i386 environment:
 .sp
 .nf
 .ft C
@@ -291,7 +371,7 @@ Enable RPMforge repository on i386 environment:
 .ft P
 .fi
 .sp
-Enable RPMforge repository on x86_64 environment:
+Enable Repoforge (RPMforge) repository on x86_64 environment:
 .sp
 .nf
 .ft C
@@ -328,11 +408,21 @@ Install:
 .ft P
 .fi
 .sp
+If you want to use \fI\%MeCab\fP as a tokenizer. please install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.sp
+.nf
+.ft C
+% sudo yum install \-y groonga\-tokenizer\-mecab
+.ft P
+.fi
+.sp
 There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
 .IP Note
-Groonga\-munin\-plugins package requires munin\-node package that isn\(aqt included in the official CentOS repository. You need to enable \fI\%RPMforge\fP repository or \fI\%EPEL\fP repository to install it by yum.
+Groonga\-munin\-plugins package requires munin\-node package that isn\(aqt included in the official CentOS repository. You need to enable \fI\%Repoforge (RPMforge)\fP repository or \fI\%EPEL\fP repository to install it by yum.
 .sp
-Enable RPMforge repository on i686 environment:
+Enable Repoforge (RPMforge) repository on i686 environment:
 .sp
 .nf
 .ft C
@@ -340,7 +430,7 @@ Enable RPMforge repository on i686 environment:
 .ft P
 .fi
 .sp
-Enable RPMforge repository on x86_64 environment:
+Enable Repoforge (RPMforge) repository on x86_64 environment:
 .sp
 .nf
 .ft C
@@ -377,6 +467,16 @@ Install:
 .ft P
 .fi
 .sp
+If you want to use \fI\%MeCab\fP as a tokenizer. please install groonga\-tokenizer\-mecab package.
+.sp
+Install groonga\-tokenizer\-mecab package:
+.sp
+.nf
+.ft C
+% sudo yum install \-y groonga\-tokenizer\-mecab
+.ft P
+.fi
+.sp
 There is a package that provides \fI\%Munin\fP plugins. If you want to monitor groonga status by Munin, please install groonga\-munin\-plugins package.
 .sp
 Install groonga\-munin\-plugins package:
@@ -428,9 +528,9 @@ Install:
 .ft P
 .fi
 .sp
-The "prefix" option specifies the path to install groonga. If you don\(aqt specify the install path, "/usr/local" is used. Please specify "/usr" if you are not familiar with environment variables such as LD_LIBRARY_PATH.
+The \fI\-\-prefix\fP option specifies the path to install groonga. If you don\(aqt specify the install path, "/usr/local" is used. Please specify "/usr" if you are not familiar with environment variables such as LD_LIBRARY_PATH.
 .sp
-There are some \fI\%Munin\fP plugins in groonga package. You need to pass \fI\-\-with\-munin\-plugins\fP option to install them.
+There are some \fI\%Munin\fP plugins in groonga package. You need to specify \fI\-\-with\-munin\-plugins\fP option if you want to install them.
 .SH COMMUNITY
 .sp
 There are some places for sharing groonga information.
@@ -440,68 +540,70 @@ We welcome you to join our community.
 There are mailing lists for discussion about groonga.
 .INDENT 0.0
 .TP
-.B For English speaker
+.B For English speakers
 \fI\%groonga-talk@lists.sourceforge.net\fP
 .TP
-.B For Japanese speaker
+.B For Japanese speakers
 \fI\%groonga-dev@lists.sourceforge.jp\fP
 .UNINDENT
 .SH TUTORIAL
 .SS Basic operations
 .sp
-The groonga package provides a C library (libgroonga) and a command line tool (groonga). This tutorial explains how to use the groonga command, with which you can create/operate databases, start a server, establish a connection with a server, etc.
+A groonga package provides a C library (libgroonga) and a command line tool (groonga). This tutorial explains how to use the command line tool, with which you can create/operate databases, start a server, establish a connection with a server, etc.
 .SS Create a database
 .sp
-You can create a new database with the following command.
+The first step to using groonga is to create a new database. The following shows how to do it.
 .sp
 Form:
 .sp
 .nf
 .ft C
-groonga \-n DB_PATH_NAME
+groonga \-n DB_PATH
 .ft P
 .fi
 .sp
-The \(aq\-n\(aq option specifies to create a new database. DB_PATH_NAME specifies the path of the new database. Note that this command fails if the specified path already exists.
+The \fI\-n\fP option specifies to create a new database and DB_PATH specifies the path of the new database. Actually, a database consists of a series of files and DB_PATH specifies the file which will be the entrance to the new database. DB_PATH also specifies the path prefix for other files. Note that database creation fails if DB_PATH points to an existing file.
 .sp
-This command creates a database and then enters into interactive mode in which groonga prompts you to enter commands for operating that database. You can terminate this mode with Ctrl\-d.
+This command creates a new database and then enters into interactive mode in which groonga prompts you to enter commands for operating that database. You can terminate this mode with Ctrl\-d.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-% groonga \-n /tmp/tutorial.db
-> Ctrl\-d
-%
+% groonga \-n /tmp/groonga\-databases/introduction.db
 .ft P
 .fi
+.sp
+After this database creation, you can find a series of files in /tmp/groonga\-databases.
 .SS Operate a database
 .sp
+The following shows how to operate an existing database.
+.sp
 Form:
 .sp
 .nf
 .ft C
-groonga DB_PATH_NAME [COMMAND]
+groonga DB_PATH [COMMAND]
 .ft P
 .fi
 .sp
-DB_PATH_NAME specifies the path of a target database.
+DB_PATH specifies the path of a target database. This command fails if the specified database does not exist.
 .sp
-If COMMAND is specified, groonga executes COMMAND and returns the result. Otherwise, groonga starts in interactive mode that reads commands from the standard input and execute them one by one. This tutorial focuses on the interactive mode.
+If COMMAND is specified, groonga executes COMMAND and returns the result. Otherwise, groonga starts in interactive mode that reads commands from the standard input and executes them one by one. This tutorial focuses on the interactive mode.
 .sp
-Let\(aqs try to see the status of a groonga process by using a \fB/commands/status\fP command.
+Let\(aqs see the status of a groonga process by using a \fB/commands/status\fP command.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-% groonga \-n /tmp/groonga\-databases/introduction.db
+% groonga /tmp/groonga\-databases/introduction.db
 > status
-[[0,1322616280.40348,0.000158121],{"alloc_count":127,"starttime":1322616279,"uptime":1,"version":"1.2.8\-9\-gbf05b82","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
+[[0,1332484898.47079,0.000113010406494141],{"alloc_count":151,"starttime":1332484898,"uptime":0,"version":"2.0.0\-250\-g5a3cf19","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
 .ft P
 .fi
 .sp
-As shown in the above example, a command basically returns a JSON array. The first element contains an error code, execution time, etc. The second element is the result of an operation.
+As shown in the above example, a command returns a JSON array. The first element contains an error code, execution time, etc. The second element is the result of an operation.
 .SS Command format
 .sp
 Commands for operating a database accept arguments as follows:
@@ -551,273 +653,304 @@ inserts records to a table.
 .UNINDENT
 .SS Create a table
 .sp
-A \fB/commands/table_create\fP command creates a table.
+A \fB/commands/table_create\fP command creates a new table.
 .sp
-In most cases, a table of groonga has a primary key which must be specified with its data type and index type.
+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, floating\-point numbers, etc. The index type determines the search performance and the availability of prefix searches. We will explain the details later.
+There are various data types such as integers, strings, etc. See also \fB/type\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 \(aqSite\(aq table which has a primary key of ShortText. In this example, the index type is HASH.
+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
 Execution example:
 .sp
 .nf
 .ft C
 > table_create \-\-name Site \-\-flags TABLE_HASH_KEY \-\-key_type ShortText
-[[0,1322616280.60791,0.01234375],true]
+[[0,1332484898.674,0.0103404521942139],true]
 .ft P
 .fi
+.sp
+The second element of the result indicates that the operation succeeded.
 .SS View a table
 .sp
-A \fB/commands/select\fP command shows contents of table.
+A \fB/commands/select\fP command can enumerate records in a table.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
 > select \-\-table Site
-[[0,1322616280.82196,0.000451873],[[[0],[["_id","UInt32"],["_key","ShortText"]]]]]
+[[0,1332484898.88587,0.000526189804077148],[[[0],[["_id","UInt32"],["_key","ShortText"]]]]]
 .ft P
 .fi
 .sp
-When only a table is specified, the \(aqselect\(aq command returns the first (at most) 10 records of that table. "[0]" in the result shows the number of records in the \(aqSite\(aq table. The next array is a list of columns. ["_id","Uint32"] is a column of UInt32, named "_id". ["_key","ShortText"] is a column of ShortText, named "_key".
+When only a table name is specified with a \fItable\fP parameter, a \fB/commands/select\fP command returns the first (at most) 10 records in the table. [0] in the result shows the number of records in the table. The next array is a list of columns. ["_id","Uint32"] is a column of UInt32, named _id. ["_key","ShortText"] is a column of ShortText, named _key.
 .sp
-The above two columns, \(aq_id\(aq and \(aq_key\(aq, are the necessary columns. The \(aq_id\(aq column stores IDs those are automatically allocated by groonga. The \(aq_key\(aq column is associated with the primary key. You are not allowed to rename these columns.
+The above two columns, _id and _key, are the necessary columns. The _id column stores IDs those are automatically allocated by groonga. The _key column is associated with the primary key. You are not allowed to rename these columns.
 .SS Create a column
 .sp
-A \fB/commands/column_create\fP command adds a column to a table.
+A \fB/commands/column_create\fP command creates a new column.
 .sp
-Let\(aqs add a column of ShortText to store titles. You may give a descriptive name \(aqtitle\(aq to the column.
+Let\(aqs add a column. The following example adds a column to the Site table. The \fItable\fP parameter specifies the target table. The \fIname\fP parameter specifies the name of the column. The \fItype\fP parameter specifies the data type of the column.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> column_create \-\-table Site \-\-name title \-\-flags COLUMN_SCALAR \-\-type ShortText
-[[0,1317212712.91734,0.077833747],true]
+> column_create \-\-table Site \-\-name title \-\-type ShortText
+[[0,1332484899.08879,0.00948214530944824],true]
 > select \-\-table Site
-[[0,1317212713.19572,0.000121119],[[[0],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]]]]]
+[[0,1332484899.29974,0.000299215316772461],[[[0],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]]]]]
 .ft P
 .fi
+.SS Load records
 .sp
-The COLUMN_SCALAR flag specifies to add a regular column.
-.SS Create a lexicon table for full text searches
-.sp
-Let\(aqs go on to how to make a full text search.
-.sp
-Groonga uses an inverted index to provide fast full text search. So, the first step is to create a lexicon table which stores an inverted index, also known as postings lists. The primary key of this table is associated with a vocabulary made up of index terms and each record stores postings lists for one index term.
+A \fB/commands/load\fP command loads JSON\-formatted records into a table.
 .sp
-The following shows a command which creates a lexicon table named \(aqTerms\(aq. The data type of its primary key is ShortText.
+The following example loads nine records into the Site table.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> table_create \-\-name Terms \-\-flags TABLE_PAT_KEY|KEY_NORMALIZE \-\-key_type ShortText \-\-default_tokenizer TokenBigram
-[[0,1317212713.39679,0.092312046],true]
+> load \-\-table Site
+> [
+> {"_key":"http://example.org/","title":"This is test record 1!"},
+> {"_key":"http://example.net/","title":"test record 2."},
+> {"_key":"http://example.com/","title":"test test record three."},
+> {"_key":"http://example.net/afr","title":"test record four."},
+> {"_key":"http://example.org/aba","title":"test test test record five."},
+> {"_key":"http://example.com/rab","title":"test test test test record six."},
+> {"_key":"http://example.net/atv","title":"test test test record seven."},
+> {"_key":"http://example.org/gat","title":"test test record eight."},
+> {"_key":"http://example.com/vdw","title":"test test record nine."},
+> ]
+[[0,1332484899.50234,2.20460820198059],9]
 .ft P
 .fi
 .sp
-The table_create command takes many parameters but you don\(aqt need to understand all of them. Please skip the next paragraph if you are not interested in how it works.
-.sp
-The \(aqTABLE_PAT_KEY\(aq flag specifies to store index terms in a patricia trie. The \(aqKEY_NORMALIZE\(aq flag specifies to normalize index terms. In this example, both flags are validated by using a \(aq|\(aq. The \(aqdefault_tokenizer\(aq parameter specifies a method for tokenizing text. This example specifies \(aqTokenBigram\(aq that is generally called \(aqN\-gram\(aq.
-.SS Create an index column for full text search
-.sp
-The second step is to create an index column, which allows you to search records from its associated column. That is to say this step specifies which column needs an index.
+The second element of the result indicates how many records were successfully loaded. In this case, all the records are successfully loaded.
 .sp
-Let\(aqs create an index column for the \(aqtitle\(aq column in the \(aqSite\(aq table.
+Let\(aqs make sure that these records are correctly stored.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> column_create \-\-table Terms \-\-name blog_title \-\-flags COLUMN_INDEX|WITH_POSITION \-\-type Site \-\-source title
-[[0,1317212713.68994,0.19739078],true]
+> select \-\-table Site
+[[0,1332484901.90868,0.000381231307983398],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"],[2,"http://example.net/","test record 2."],[3,"http://example.com/","test test record three."],[4,"http://example.net/afr","test record four."],[5,"http://example.org/aba","test test test record five."],[6,"http://example.com/rab","test test test test record six."],[7,"http://example.net/atv","test test test record seven."],[8,"http://example.org/gat","test test record eight."],[9,"http://example.com/vdw","test test record nine."]]]]
 .ft P
 .fi
+.SS Get a record
 .sp
-This command creates an index column \(aqblog_title\(aq in the \(aqTerms\(aq table. The \(aq\-\-type\(aq option specifies a target table and the \(aq\-\-source\(aq option specifies a target column. Then, the \(aqCOLUMN_INDEX\(aq flag specifies to create an index column and the \(aqWITH_POSITION\(aq flag specifies to create a full inverted index, which contains the positions of each index term. This combination \(aqCOLUMN_INDEX|WITH_POSITION\(aq is recommended for the general purpose.
-.SS Load data
+A \fB/commands/select\fP command can search records in a table.
 .sp
-A \fB/commands/load\fP command loads JSON\-formatted records into a table.
+If a search condition is specified with a \fIquery\fP parameter, a \fB/commands/select\fP command searches records matching the search condition and returns the matched records.
 .sp
-The following adds nine records to the \(aqSite\(aq table.
+Let\(aqs get a record having a specified record ID. The following example gets the first record in the Site table. More precisely, the \fIquery\fP parameter specifies a record whose _id column stores 1.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> load \-\-table Site
-> [
-> {"_key":"http://example.org/","title":"This is test record 1!"},
-> {"_key":"http://example.net/","title":"test record 2."},
-> {"_key":"http://example.com/","title":"test test record three."},
-> {"_key":"http://example.net/afr","title":"test record four."},
-> {"_key":"http://example.org/aba","title":"test test test record five."},
-> {"_key":"http://example.com/rab","title":"test test test test record six."},
-> {"_key":"http://example.net/atv","title":"test test test record seven."},
-> {"_key":"http://example.org/gat","title":"test test record eight."},
-> {"_key":"http://example.com/vdw","title":"test test record nine."},
-> ]
-[[0,1317212714.08816,2.203527402],9]
+> select \-\-table Site \-\-query _id:1
+[[0,1332484902.11683,0.000809431076049805],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
 .ft P
 .fi
 .sp
-Let\(aqs make sure that these records are correctly stored.
+Next, let\(aqs get a record having a specified key. The following example gets the record whose primary key is "\fI\%http://example.org/\fP". More precisely, the \fIquery\fP parameter specifies a record whose _key column stores "\fI\%http://example.org/\fP".
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> select \-\-table Site
-[[0,1317212716.49285,0.000270908],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"],[2,"http://example.net/","test record 2."],[3,"http://example.com/","test test record three."],[4,"http://example.net/afr","test record four."],[5,"http://example.org/aba","test test test record five."],[6,"http://example.com/rab","test test test test record six."],[7,"http://example.net/atv","test test test record seven."],[8,"http://example.org/gat","test test record eight."],[9,"http://example.com/vdw","test test record nine."]]]]
+> select \-\-table Site \-\-query \(aq_key:"http://example.org/"\(aq
+[[0,1332484902.32106,0.000850200653076172],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
 .ft P
 .fi
-.SS Search data
+.SS Create a lexicon table for full text search
+.sp
+Let\(aqs go on to how to make full text search.
 .sp
-Before a full text search, let\(aqs try to search data by \(aq_id\(aq and \(aq_key\(aq. These columns work as unique keys.
+Groonga uses an inverted index to provide fast full text search. So, the first step is to create a lexicon table which stores an inverted index, also known as postings lists. The primary key of this table is associated with a vocabulary made up of index terms and each record stores postings lists for one index term.
 .sp
-You can search records by using a \(aqselect\(aq command with a \(aqquery\(aq parameter.
+The following shows a command which creates a lexicon table named Terms. The data type of its primary key is ShortText.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> select \-\-table Site \-\-query _id:1
-[[0,1317212716.69871,0.000308514],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
+> table_create \-\-name Terms \-\-flags TABLE_PAT_KEY|KEY_NORMALIZE \-\-key_type ShortText \-\-default_tokenizer TokenBigram
+[[0,1332484902.52532,0.00777173042297363],true]
 .ft P
 .fi
 .sp
-\(aq_id:1\(aq specifies to search a record whose ID is 1.
+The \fB/commands/table_create\fP command takes many parameters but you don\(aqt need to understand all of them. Please skip the next paragraph if you are not interested in how it works.
+.sp
+The TABLE_PAT_KEY flag specifies to store index terms in a patricia trie. The KEY_NORMALIZE flag specifies to normalize index terms. In this example, both flags are validated by using a \(aq|\(aq. The \fIdefault_tokenizer\fP parameter specifies the method for tokenizing text. This example uses TokenBigram that is generally called N\-gram.
+.SS Create an index column for full text search
+.sp
+The second step is to create an index column, which allows you to search records from its associated column. That is to say this step specifies which column needs an index.
 .sp
-Next, let\(aqs search a record by a primary key.
+Let\(aqs create an index column. The following example creates an index column for a column in the Site table.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> select \-\-table Site \-\-query "_key:\e"http://example.org/\e""
-[[0,1317212716.9005,0.000478343],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
+> column_create \-\-table Terms \-\-name blog_title \-\-flags COLUMN_INDEX|WITH_POSITION \-\-type Site \-\-source title
+[[0,1332484902.73511,0.0202178955078125],true]
 .ft P
 .fi
 .sp
-\(aq_key:"\fI\%http://example.org/\fP"\(aq specifies to search a record whose primary key is "\fI\%http://example.org/\fP".
+The \fItable\fP parameter specifies the index table and the \fIname\fP parameter specifies the index column. The \fItype\fP parameter specifies the target table and the \fIsource\fP parameter specifies the target column. The COLUMN_INDEX flag specifies to create an index column and the WITH_POSITION flag specifies to create a full inverted index, which contains the positions of each index term. This combination, COLUMN_INDEX|WITH_POSITION, is recommended for the general purpose.
+.IP Note
+You can create a lexicon table and index columns before/during/after loading records. If a target column already has records, groonga creates an inverted index in a static manner. In contrast, if you load records into an already indexed column, groonga updates the inverted index in a dynamic manner.
+.RE
 .SS Full text search
 .sp
-It\(aqs time to make a full text search. You can make a full text search query with the same \(aqquery\(aq parameter.
+It\(aqs time. You can make full text search with a \fB/commands/select\fP command.
+.sp
+A query for full text search is specified with a \fIquery\fP parameter. The following example searches records whose "title" column contains "this". The \(aq@\(aq specifies to make full text search. Note that a lower case query matches upper case and capitalized terms in a record if KEY_NORMALIZE was specified when creating a lexcon table.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
 > select \-\-table Site \-\-query title:@this
-[[0,1317212717.10303,0.000581287],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
+[[0,1332484902.95678,0.000878334045410156],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
 .ft P
 .fi
 .sp
-This command searches records whose \(aqtitle\(aq column contains a string \(aqthis\(aq. In this case, only one record matches this query. Note that the lower case query \(aqthis\(aq matches a capitalized \(aqThis\(aq in the 1st record because \(aqKEY_NORMALIZE\(aq was specified in lexicon column creation.
+In this example, the first record matches the query because its title contains "This", that is the capitalized form of the query.
 .sp
-The \(aqselect\(aq command has an optional parameter \(aqmatch_columns\(aq. This parameter specifies default target columns and it is used when target columns are not specified in a query.[1]_
+A \fB/commands/select\fP command accepts an optional parameter, named \fImatch_columns\fP, that specifies the default target columns. This parameter is used if target columns are not specified in a query. [1]
 .sp
-A combination of \(aq\-\-match_columns title\(aq and \(aq\-\-query this\(aq brings you the same result that \(aq\-\-query title:@this\(aq does.
+The combination of "\fI\-\-match_columns\fP title" and "\fI\-\-query\fP this" brings you the same result that "\fI\-\-query\fP title:@this" does.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
 > select \-\-table Site \-\-match_columns title \-\-query this
-[[0,1317212717.30596,0.000716439],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
+[[0,1332484903.16096,0.000757932662963867],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
 .ft P
 .fi
 .SS Specify output columns
 .sp
-An \(aqoutput_columns\(aq parameter in a \(aqselect\(aq command specifies columns to be shown in the search result. If you want to specify more than one columns, please separate column names by commas (,).
+An \fIoutput_columns\fP parameter of a \fB/commands/select\fP command specifies columns to appear in the search result. If you want to specify more than one columns, please separate column names by commas (\(aq,\(aq).
 .sp
 Execution example:
 .sp
 .nf
 .ft C
 > select \-\-table Site \-\-output_columns _key,title,_score \-\-query title:@test
-[[0,1317212717.50916,0.00060758],[[[9],[["_key","ShortText"],["title","ShortText"],["_score","Int32"]],["http://example.org/","This is test record 1!",1],["http://example.net/","test record 2.",1],["http://example.com/","test test record three.",2],["http://example.net/afr","test record four.",1],["http://example.org/aba","test test test record five.",3],["http://example.com/rab","test test test test record six.",4],["http://example.net/atv","test test test record seven.",3],["http://example.org/gat","test test record eight.",2],["http://example.com/vdw","test test record nine.",2]]]]
+[[0,1332484903.36506,0.000709056854248047],[[[9],[["_key","ShortText"],["title","ShortText"],["_score","Int32"]],["http://example.org/","This is test record 1!",1],["http://example.net/","test record 2.",1],["http://example.com/","test test record three.",2],["http://example.net/afr","test record four.",1],["http://example.org/aba","test test test record five.",3],["http://example.com/rab","test test test test record six.",4],["http://example.net/atv","test test test record seven.",3],["http://example.org/gat","test test record eight.",2],["http://example.com/vdw","test test record nine.",2]]]]
 .ft P
 .fi
 .sp
-This command specifies three output columns including the \(aq_score\(aq column, which stores the relevance score of each record.
+This example specifies three output columns including the _score column, which stores the relevance score of each record.
 .SS Specify output ranges
 .sp
-A \(aqselect\(aq command returns a part of its search result if \(aqoffset\(aq and/or \(aqlimit\(aq parameters are specified. These parameters are useful to paginate a search result, a widely\-used interface which shows a search result on a page by page basis.
+A \fB/commands/select\fP command returns a part of its search result if \fIoffset\fP and/or \fIlimit\fP parameters are specified. These parameters are useful to paginate a search result, a widely\-used interface which shows a search result on a page by page basis.
 .sp
-An \(aqoffset\(aq parameter specifies the starting point and a \(aqlimit\(aq parameter specifies the maximum number of records to be returned. If you need the first record in a search result, the offset parameter must be 0 or omitted.
+An \fIoffset\fP parameter specifies the starting point and a \fIlimit\fP parameter specifies the maximum number of records to be returned. If you need the first record in a search result, the offset parameter must be 0 or omitted.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
 > select \-\-table Site \-\-offset 0 \-\-limit 3
-[[0,1317212717.71574,0.000238544],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"],[2,"http://example.net/","test record 2."],[3,"http://example.com/","test test record three."]]]]
+[[0,1332484903.57505,0.000303268432617188],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"],[2,"http://example.net/","test record 2."],[3,"http://example.com/","test test record three."]]]]
 > select \-\-table Site \-\-offset 3 \-\-limit 3
-[[0,1317212717.91925,0.00023617],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[4,"http://example.net/afr","test record four."],[5,"http://example.org/aba","test test test record five."],[6,"http://example.com/rab","test test test test record six."]]]]
+[[0,1332484903.77936,0.000320196151733398],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[4,"http://example.net/afr","test record four."],[5,"http://example.org/aba","test test test record five."],[6,"http://example.com/rab","test test test test record six."]]]]
 > select \-\-table Site \-\-offset 7 \-\-limit 3
-[[0,1317212718.12219,0.00019999],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[8,"http://example.org/gat","test test record eight."],[9,"http://example.com/vdw","test test record nine."]]]]
+[[0,1332484903.98409,0.000294685363769531],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[8,"http://example.org/gat","test test record eight."],[9,"http://example.com/vdw","test test record nine."]]]]
 .ft P
 .fi
-.SS Sort
+.SS Sort a search result
+.sp
+A \fB/commands/select\fP command sorts its result when used with a \fIsortby\fP parameter.
 .sp
-A \(aqselect\(aq command sorts its result when used with a \(aqsortby\(aq parameter.
+A \fIsortby\fP parameter specifies a column as a sorting creteria. A search result is arranged in ascending order of the column values. If you want to sort a search result in reverse order, please add a leading hyphen (\(aq\-\(aq) to the column name in a parameter.
 .sp
-A \(aqsortby\(aq parameter specifies a column as a sorting creteria. A search result is arranged in ascending order of the column values. If you want to sort a search result in reverse order, please add a leading hyphen (\-) to the column name of a parameter.
+The following example shows records in the Site table in reverse order.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
 > select \-\-table Site \-\-sortby \-_id
-[[0,1317212718.32565,0.000385755],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[9,"http://example.com/vdw","test test record nine."],[8,"http://example.org/gat","test test record eight."],[7,"http://example.net/atv","test test test record seven."],[6,"http://example.com/rab","test test test test record six."],[5,"http://example.org/aba","test test test record five."],[4,"http://example.net/afr","test record four."],[3,"http://example.com/","test test record three."],[2,"http://example.net/","test record 2."],[1,"http://example.org/","This is test record 1!"]]]]
+[[0,1332484904.18805,0.000293493270874023],[[[9],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[9,"http://example.com/vdw","test test record nine."],[8,"http://example.org/gat","test test record eight."],[7,"http://example.net/atv","test test test record seven."],[6,"http://example.com/rab","test test test test record six."],[5,"http://example.org/aba","test test test record five."],[4,"http://example.net/afr","test record four."],[3,"http://example.com/","test test record three."],[2,"http://example.net/","test record 2."],[1,"http://example.org/","This is test record 1!"]]]]
 .ft P
 .fi
 .sp
-You can use the \(aq_score\(aq column as a sorting criteria for ranking a search result.
+The next example uses the _score column as the sorting criteria for ranking the search result. The result is sorted in relevance order.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> select \-\-table Site \-\-query title:@test \-\-output_columns _id,_score,title \-\-sortby _score
-[[0,1317212718.5331,0.000667311],[[[9],[["_id","UInt32"],["_score","Int32"],["title","ShortText"]],[1,1,"This is test record 1!"],[2,1,"test record 2."],[4,1,"test record four."],[3,2,"test test record three."],[9,2,"test test record nine."],[8,2,"test test record eight."],[7,3,"test test test record seven."],[5,3,"test test test record five."],[6,4,"test test test test record six."]]]]
+> select \-\-table Site \-\-query title:@test \-\-output_columns _id,_score,title \-\-sortby \-_score
+[[0,1332484904.39402,0.000802755355834961],[[[9],[["_id","UInt32"],["_score","Int32"],["title","ShortText"]],[6,4,"test test test test record six."],[5,3,"test test test record five."],[7,3,"test test test record seven."],[8,2,"test test record eight."],[3,2,"test test record three."],[9,2,"test test record nine."],[1,1,"This is test record 1!"],[4,1,"test record four."],[2,1,"test record 2."]]]]
 .ft P
 .fi
 .sp
-If you want to specify more than one columns, please separate column names by commas. In such a case, a search result is sorted in order of the column values in the first column, and then records having the same values in the first column are sorted in order of the second column values.
+If you want to specify more than one columns, please separate column names by commas (\(aq,\(aq). In such a case, a search result is sorted in order of the values in the first column, and then records having the same values in the first column are sorted in order of the second column values.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> select \-\-table Site \-\-query title:@test \-\-output_columns _id,_score,title \-\-sortby _score,_id
-[[0,1317212718.73819,0.00069225],[[[9],[["_id","UInt32"],["_score","Int32"],["title","ShortText"]],[1,1,"This is test record 1!"],[2,1,"test record 2."],[4,1,"test record four."],[3,2,"test test record three."],[8,2,"test test record eight."],[9,2,"test test record nine."],[5,3,"test test test record five."],[7,3,"test test test record seven."],[6,4,"test test test test record six."]]]]
+> select \-\-table Site \-\-query title:@test \-\-output_columns _id,_score,title \-\-sortby \-_score,_id
+[[0,1332484904.60132,0.000498056411743164],[[[9],[["_id","UInt32"],["_score","Int32"],["title","ShortText"]],[6,4,"test test test test record six."],[5,3,"test test test record five."],[7,3,"test test test record seven."],[3,2,"test test record three."],[8,2,"test test record eight."],[9,2,"test test record nine."],[1,1,"This is test record 1!"],[2,1,"test record 2."],[4,1,"test record four."]]]]
 .ft P
 .fi
 footnote
 .IP [1] 5
-Currently, a \(aqmatch_columns\(aq parameter is available iff there exists an inverted index for full text search. A \(aqmatch_columns\(aq parameter for a regular column is not supported.
-.SS How to use groonga with network
+Currently, a \fImatch_columns\fP parameter is available iff there exists an inverted index for full text search. A \fImatch_columns\fP parameter for a regular column is not supported.
+.SS Remote access
 .sp
-You can use groonga with network. When you run groonga by using the groonga original protocol or HTTP, groonga accepts connection for network.
-.SS Connect with groonga\(aqs original protocol
-.SS Run groonga daemon
+You can use groonga as a server which allows remote access. Groonga supports the original protocol (gqtp), the memcached binary protocol and HTTP.
+.SS Groonga query transfer protocol (gqtp)
+.SS How to run a gqtp server
+.sp
+Groonga has a special protocol, named groonga query transfer ptorotocl (gqtp), for remote access to a database. The following form shows how to run groonga as a gqtp server.
 .sp
 Form:
 .sp
 .nf
 .ft C
-groonga [\-p PORT_NUMBER] \-d DB_PATH_NAME
+groonga [\-p PORT_NUMBER] \-s DB_PATH
 .ft P
 .fi
 .sp
-The DB_PATH_NAME is set the full\-path of existing database.
-With this form, you can run groonga as a daemon and connect by
-with groonga original protocol on PORT_NUMBER.
-(The port number is 10041 when you don\(aqt specify PORT_NUMBER.)
+The \fI\-s\fP option specifies to run groonga as a server. DB_PATH specifies the path of the existing database to be hosted. The \fI\-p\fP option and its argument, PORT_NUMBER, specify the port number of the server. The default port number is 10041, which is used when you don\(aqt specify PORT_NUMBER.
+.sp
+The following command runs a server that listens on the default port number. The server accepts operations to the specified database.
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+% groonga \-s /tmp/groonga\-databases/introduction.db
+Ctrl\-c
+%
+.ft P
+.fi
+.SS How to run a gqtp daemon
+.sp
+You can also run a gqtp server as a daemon by using the \fI\-d\fP option, instead of the \fI\-s\fP option.
+.sp
+Form:
+.sp
+.nf
+.ft C
+groonga [\-p PORT_NUMBER] \-d DB_PATH
+.ft P
+.fi
+.sp
+A groonga daemon prints its process ID as follows. In this example, the process ID is 12345. Then, the daemon opens a specified database and accepts operations to that database.
 .sp
 Execution example:
 .sp
@@ -828,9 +961,9 @@ Execution example:
 %
 .ft P
 .fi
+.SS How to run a gqtp client
 .sp
-Groonga shows its process ID on daemon mode.
-.SS Connect to groonga server
+You can run groonga as a gqtp client as follows:
 .sp
 Form:
 .sp
@@ -840,11 +973,7 @@ groonga [\-p PORT_NUMBER] \-c [HOST_NAME_OR_IP_ADDRESS]
 .ft P
 .fi
 .sp
-This command connects to groonga server running at specified HOST_NAME_OR_IP_ADDRESS.
-.sp
-When you don\(aqt specify HOST_NAME_OR_IP_ADDRESS, this command connects to groonga server running at localhost. When you don\(aqt specify PORT_NUMBER, 10041 is used.
-.sp
-Groonga runs in interactive mode after connect to groonga server successfully. Groonga reads command from standard input and evaluates it repeatedly.
+This command establishes a connection with a gqtp server and then enters into interactive mode. HOST_NAME_OR_IP_ADDRESS specifies the hostname or the IP address of the server. If not specifed, groonga uses the default hostname "localhost". The \fI\-p\fP option and its argument, PORT_NUMBER, specify the port number of the server. If not specified, groonga uses the default port number 10041.
 .sp
 Execution example:
 .sp
@@ -852,14 +981,16 @@ Execution example:
 .ft C
 % groonga \-c
 > status
-[[0,1317212813.13814,0.000102148],{"alloc_count":184,"starttime":1317212806,"uptime":7,"version":"1.2.5\-84\-g5c190df","n_queries":14,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
+[[0,1332486613.4953,9.918212890625e\-05],{"alloc_count":130,"starttime":1332486613,"uptime":0,"version":"2.0.0\-250\-g5a3cf19","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
 > ctrl\-d
 %
 .ft P
 .fi
-.SS Terminate groonga daemon
 .sp
-You can terminate groonga daemon with shutdown command.
+In interactive mode, groonga reads commands from the standard input and executes them one by one.
+.SS How to terminate a gqtp server
+.sp
+You can terminate a gqtp server with a \fB/commands/shutdown\fP command.
 .sp
 Execution example:
 .sp
@@ -870,128 +1001,260 @@ Execution example:
 %
 .ft P
 .fi
-.SS Connect with HTTP
+.SS Memcached binary protocol
+.sp
+Groonga supports the memcached binary protocol. The following form shows how to run groonga as a memcached binary protocol server daemon.
+.sp
+Form:
+.sp
+.nf
+.ft C
+groonga [\-p PORT_NUMBER] \-d \-\-protocol memcached DB_PATH
+.ft P
+.fi
+.sp
+The \fI\-\-protocol\fP option and its argument specify the protocol of the server. "memcached" specifies to use the memcached binary protocol.
+.SS Hypertext transfer protocol (HTTP)
+.SS How to run an HTTP server
 .sp
-You need to run groonga in HTTP protocol mode when you want to use groonga via HTTP.
+Groonga supports the hypertext transfer protocol (HTTP). The following form shows how to run groonga as an HTTP server daemon.
 .sp
 Form:
 .sp
 .nf
 .ft C
-groonga [\-p PORT_NUMBER] \-d \-\-protocol http DB_PATH_NAME
+groonga [\-p PORT_NUMBER] \-d \-\-protocol http DB_PATH
 .ft P
 .fi
 .sp
-\fI\-\-protocol\fP option specifies a protocol of groonga server. \fIhttp\fP means that groonga accepts connections via HTTP.
-.SS Administration tool based on HTML
+The \fI\-\-protocol\fP option and its argument specify the protocol of the server. "http" specifies to use HTTP.
+.sp
+The following command runs an HTTP server that listens on the port number 80.
+.sp
+Execution example:
 .sp
-You can access administration tool based on HTML at \fIhttp://[HOST_NAME_OR_IP_ADDRESS]:[PORT_NUMBER]/\fP after the above command is ran. Your browser must enable JavaScript.
-.SS Run command with HTTP
+.nf
+.ft C
+% groonga \-p 80 \-d \-\-protocol http /tmp/groonga\-databases/introduction.db
+%
+.ft P
+.fi
+.SS How to send a command to an HTTP server
 .sp
-You can run command at \fI/d/COMMAND_NAME\fP when groonga is ran in HTTP protocol mode.
+You can send a command to an HTTP server by sending a GET request to /d/COMMAND_NAME. Command parameters can be passed as parameters of the GET request. The format is "?NAME_1=VALUE_1&NAME_2=VALUE_2&...".
 .sp
-Command options are passed as HTTP\(aqs GET parameters. They are in \fI?OPTION=VALUE&OPTION=VALUE&...\fP form.
+The following example shows how to send commands to an HTTP server.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-http://[IPまたはホスト名]:[ポート番号]/d/status
-実行される処理：
+http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/d/status
+Executed command:
 > status
-[[0,1317212813.33982,0.000109691],{"alloc_count":184,"starttime":1317212806,"uptime":7,"version":"1.2.5\-84\-g5c190df","n_queries":14,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
+[[0,1332486613.69917,0.000123739242553711],{"alloc_count":131,"starttime":1332486613,"uptime":0,"version":"2.0.0\-250\-g5a3cf19","n_queries":0,"cache_hit_rate":0.0,"command_version":1,"default_command_version":1,"max_command_version":2}]
 
-http://[IPまたはホスト名]:[ポート番号]/d/select?table=Site&query=title:@this
-実行される処理：
+http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/d/select?table=Site&query=title:@this
+Executed command:
 > select \-\-table Site \-\-query title:@this
-[[0,1317212813.54112,6.7993e\-05],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
+[[0,1332486613.90319,0.00245404243469238],[[[1],[["_id","UInt32"],["_key","ShortText"],["title","ShortText"]],[1,"http://example.org/","This is test record 1!"]]]]
 .ft P
 .fi
-.SS Security
+.SS Administration tool (HTTP)
 .sp
-Network service of groonga doesn\(aqt support authentication. Everyone can view and modify the database. We recommend that you restrict client accesses by IP address. You can use iptables or any similar tool for it.
-.SS さまざまな種類をもったデータの保存
+An HTTP server of groonga provides a browser based administration tool that makes database management easy. After starting an HTTP server, you can use the administration tool by accessing \fI\%http://HOST_NAME_OR_IP_ADDRESS[:PORT_NUMBER]/\fP. Note that Javascript must be enabled for the tool to work properly.
+.SS Security issues
 .sp
-groongaでは、さまざまなデータを格納させることが出来ます。
-.SS データ型
+Groonga servers don\(aqt support user authentication. Everyone can view and modify databases hosted by groonga servers. You are recommended to restrict IP addresses that can access groonga servers. You can use iptables or similar for this purpose.
+.SS Various data types
 .sp
-groongaでは、数値（整数・小数）や文字列や時刻や経緯度などの情報を格納することができます。
+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
-ここでは、Int32型のカラムに整数を格納、Float型のカラムに浮動小数点の小数を、ShortText型のカラムに文字列を、Time型のカラムに時間を格納する例を示します。経緯度の格納については、のちのチュートリアルで触れます。
+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/type\fP.
 .sp
-その他のデータ型の一覧は、 \fB/type\fP を参照してください。
+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
+First, let\(aqs create a table for this tutorial.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
-> table_create \-\-name Type \-\-flags TABLE_HASH_KEY \-\-key_type ShortText
-[[0,1322616293.7274,0.012551106],true]
-> column_create \-\-table Type \-\-name number \-\-type Int32
-[[0,1322616293.94115,0.008619605],true]
-> column_create \-\-table Type \-\-name float \-\-type Float
-[[0,1322616294.15095,0.004959989],true]
-> column_create \-\-table Type \-\-name string \-\-type ShortText
-[[0,1322616294.35693,0.005551818],true]
-> column_create \-\-table Type \-\-name time \-\-type Time
-[[0,1322616294.56333,0.006356953],true]
-> load \-\-table Type
-> [{"_key":"sample","number":12345,"float":42.195,"string":"GROONGA","time":1234567890.12}]
-[[0,1322616294.77086,0.202357708],1]
-> select \-\-table Type
-[[0,1322616295.1744,0.000340057],[[[1],[["_id","UInt32"],["_key","ShortText"],["float","Float"],["number","Int32"],["string","ShortText"],["time","Time"]],[1,"sample",42.195,12345,"GROONGA",1234567890.12]]]]
+> table_create \-\-name ToyBox \-\-flags TABLE_HASH_KEY \-\-key_type ShortText
+[[0,1332498286.03578,0.00542259216308594],true]
 .ft P
 .fi
-.SS テーブル型
+.SS Boolean type
+.sp
+The boolean type is used to store true or false. To create a boolean type column, specify Bool to the \fItype\fP parameter of \fB/commands/column_create\fP command. The default value of the boolean type is false.
 .sp
-table_createで作成したテーブルを、カラムの型として使うことが出来ます。
+The following example creates a boolean type column and adds three records. Note that the third record has the default value because no value is specified.
 .sp
-また、output_columnsにおいて「.」を区切りとして、参照先のテーブルに存在するカラムを指定すると、指定したカラムの値を表示することができます。
+Execution example:
+.sp
+.nf
+.ft C
+> column_create \-\-table ToyBox \-\-name is_animal \-\-type Bool
+[[0,1332498286.2427,0.00578594207763672],true]
+> load \-\-table ToyBox
+> [
+> {"_key":"Monkey","is_animal":true}
+> {"_key":"Flower","is_animal":false}
+> {"_key":"Block"}
+> ]
+[[0,1332498286.44978,1.00197458267212],3]
+> select \-\-table ToyBox \-\-output_columns _key,is_animal
+[[0,1332498287.65257,0.000472545623779297],[[[3],[["_key","ShortText"],["is_animal","Bool"]],["Monkey",true],["Flower",false],["Block",false]]]]
+.ft P
+.fi
+.SS Numeric types
 .sp
-ここでは、先のチュートリアルで作成したSiteテーブルに手を加え、どのサイトをリンクしているのかを保存してみましょう。
+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/type\fP. The default value of the numeric types is 0.
 .sp
-他のテーブルを参照するカラムにデータを入力する場合には、参照先のテーブルの_keyカラムの値を代入する必要があります。
+The following example creates an Int8 column and a Float column, and then updates existing records. The \fB/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
+Execution example:
+.sp
+.nf
+.ft C
+> column_create \-\-table ToyBox \-\-name price \-\-type Int8
+[[0,1332498287.85609,0.00574946403503418],true]
+> column_create \-\-table ToyBox \-\-name weight \-\-type Float
+[[0,1332498288.06304,0.00493621826171875],true]
+> load \-\-table ToyBox
+> [
+> {"_key":"Monkey","price":15.9}
+> {"_key":"Flower","price":200,"weight":0.13}
+> {"_key":"Block","weight":25.7}
+> ]
+[[0,1332498288.26924,1.00213837623596],3]
+> select \-\-table ToyBox \-\-output_columns _key,price,weight
+[[0,1332498289.47254,0.000308036804199219],[[[3],[["_key","ShortText"],["price","Int8"],["weight","Float"]],["Monkey",15,0.0],["Flower",\-56,0.13],["Block",0,25.7]]]]
+.ft P
+.fi
+.SS String types
+.sp
+The string types are divided according to the maximum length. For more details, see \fB/type\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
+Execution example:
+.sp
+.nf
+.ft C
+> column_create \-\-table ToyBox \-\-name name \-\-type ShortText
+[[0,1332498289.67627,0.00676369667053223],true]
+> load \-\-table ToyBox
+> [
+> {"_key":"Monkey","name":"Grease"}
+> {"_key":"Flower","name":"Rose"}
+> ]
+[[0,1332498289.88434,0.801783800125122],2]
+> select \-\-table ToyBox \-\-output_columns _key,name
+[[0,1332498290.88724,0.000265598297119141],[[[3],[["_key","ShortText"],["name","ShortText"]],["Monkey","Grease"],["Flower","Rose"],["Block",""]]]]
+.ft P
+.fi
+.SS Date and time type
+.sp
+The date and time type of groonga is Time. Actually, a Time column stores a date and time as the number of microseconds since the Epoch, 1970\-01\-01 00:00:00. A Time value can represent a date and time before the Epoch because the actual data type is a signed integer. Note that \fB/commands/load\fP and :doc:
+.nf
+\(ga
+.fi
+/commands/select commands use a decimal number to represent a data and time in seconds. The default value is 0.0, which means the Epoch.
+.sp
+The following example creates a Time column and updates existing records. The first record has the default value because not updated.
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+> column_create \-\-table ToyBox \-\-name time \-\-type Time
+[[0,1332498291.0906,0.00631809234619141],true]
+> load \-\-table ToyBox
+> [
+> {"_key":"Flower","time":1234567890.1234569999}
+> {"_key":"Block","time":\-1234567890}
+> ]
+[[0,1332498291.29814,0.801807641983032],2]
+> select \-\-table ToyBox \-\-output_columns _key,time
+[[0,1332498292.30117,0.000299692153930664],[[[3],[["_key","ShortText"],["time","Time"]],["Monkey",0.0],["Flower",1234567890.12346],["Block",\-1234567890.0]]]]
+.ft P
+.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/type\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")
+.IP \(bu 2
+"longitude x latitude" in degrees (e.g.: "35.6813819x139.7660839")
+.UNINDENT
+.sp
+A number with/without a decimal point represents a longitude or latitude in milliseconds/degrees respectively. Note that a combination of a number with a decimal point and a number without a decimal point (e.g. 35.1x139) must not be used. A comma (\(aq,\(aq) is also available as a delimiter. The default value is "0x0".
+.sp
+The following example creates a WGS84GeoPoint column and updates existing records. The second record has the default value because not updated.
+.sp
+Execution example:
+.sp
+.nf
+.ft C
+> column_create \-\-table ToyBox \-\-name location \-\-type WGS84GeoPoint
+[[0,1332498292.50467,0.0079643726348877],true]
+> load \-\-table ToyBox
+> [
+> {"_key":"Monkey","location":"128452975x503157902"}
+> {"_key":"Block","location":"35.6813819x139.7660839"}
+> ]
+[[0,1332498292.71385,0.801813840866089],2]
+> select \-\-table ToyBox \-\-output_columns _key,location
+[[0,1332498293.71678,0.000298976898193359],[[[3],[["_key","ShortText"],["location","WGS84GeoPoint"]],["Monkey","128452975x503157902"],["Flower","0x0"],["Block","128452975x503157902"]]]]
+.ft P
+.fi
+.SS Reference types
+.sp
+Groonga supports a reference column, which stores references to records in its associated table. In practice, a reference column stores the IDs of the referred records in the associated table and enables access to those records.
+.sp
+You can specify a column in the associated table to the \fIoutput_columns\fP parameter of a \fB/commands/select\fP command. The format is "Src.Dest" where Src is the name of the reference column and Dest is the name of the target column. If only the reference column is specified, it is handled as "Src._key". Note that if a reference does not point to a valid record, a \fB/commands/select\fP command outputs the default value of the target column.
+.sp
+The following example adds a reference column to the Site table that was created in the previous tutorial. The new column, named link, is designed for storing links among records in the Site table.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
 > column_create \-\-table Site \-\-name link \-\-type Site
-[[0,1322616295.37864,0.005674045],true]
+[[0,1332498293.92066,0.00589966773986816],true]
 > load \-\-table Site
 > [{"_key":"http://example.org/","link":"http://example.net/"}]
-[[0,1322616295.5854,0.200879317],1]
+[[0,1332498294.1274,0.201014280319214],1]
 > select \-\-table Site \-\-output_columns _key,title,link._key,link.title \-\-query title:@this
-[[0,1322616295.98732,0.000872177],[[[1],[["_key","ShortText"],["title","ShortText"],["link._key","ShortText"],["link.title","ShortText"]],["http://example.org/","This is test record 1!","http://example.net/","test record 2."]]]]
+[[0,1332498294.52959,0.00171041488647461],[[[1],[["_key","ShortText"],["title","ShortText"],["link._key","ShortText"],["link.title","ShortText"]],["http://example.org/","This is test record 1!","http://example.net/","test record 2."]]]]
 .ft P
 .fi
 .sp
-このように、linkカラムに他のサイトへの参照を保存することができました。また、参照先の_keyとtitleカラムの内容を表示することができました。
-.SS ベクターカラム
-.sp
-column_createコマンドでカラムを作成するとき、\-\-flagsオプションでCOLUMN_VECTORフラグを指定すると、複数の値を配列で格納できるカラムが作成されます。
+The \fItype\fP parameter of the \fB/commands/column_create\fP command specifies the table to be associated with the reference column. In this example, the reference column is associated with the own table. Then, the \fB/commands/load\fP command registers a link from "\fI\%http://example.org\fP" to "\fI\%http://example.net\fP". Note that a reference column requires the primary key, not the ID, of the record to be referred to. After that, the link is confirmed by the \fB/commands/select\fP command. In this case, the primary key and the title of the referred record are output because link._key and link.title are specified to the \fIoutput_columns\fP parameter.
+.SS Vector types
 .sp
-テーブル型で配列を格納するカラムは、1対多の参照関係を表すのに有効です。
+Groonga supports a vector column, in which each element can store a variable number of values. To create a vector column, specify the COLUMN_VECTOR flag to the \fIflags\fP parameter of a \fB/commands/column_create\fP command. A vector column is useful to represent a many\-to\-many relationship.
 .sp
-テーブル型のチュートリアルでは、Siteテーブルに手を加え、どのサイトをリンクしているのかを保存しました。しかし、通常は1つのサイトから多くのサイトにリンクが張られています。複数のリンク情報を格納するために、複数の参照関係を保存するカラムを作成してみましょう。
-.sp
-他のテーブルを参照するベクターカラムにデータを入力する場合には、参照先のテーブルの_keyカラムの値の「配列」を代入する必要があります。
+The previous example used a regular column, so each record could have at most one link. Obviously, the specification is insufficient because a site usually has more than one links. To solve this problem, the following example uses a vector column.
 .sp
 Execution example:
 .sp
 .nf
 .ft C
 > column_create \-\-table Site \-\-name links \-\-flags COLUMN_VECTOR \-\-type Site
-[[0,1322616296.19238,0.007598942],true]
+[[0,1332498294.7353,0.00729537010192871],true]
 > load \-\-table Site
 > [{"_key":"http://example.org/","links":["http://example.net/","http://example.org/","http://example.com/"]}]
-[[0,1322616296.40092,0.201036234],1]
+[[0,1332498294.94353,0.200709581375122],1]
 > select \-\-table Site \-\-output_columns _key,title,links._key,links.title \-\-query title:@this
-[[0,1322616296.80305,0.000899975],[[[1],[["_key","ShortText"],["title","ShortText"],["links._key","ShortText"],["links.title","ShortText"]],["http://example.org/","This is test record 1!",["http://example.net/","http://example.org/","http://example.com/"],["test record 2.","This is test record 1!","test test record three."]]]]]
+[[0,1332498295.34514,0.00077366828918457],[[[1],[["_key","ShortText"],["title","ShortText"],["links._key","ShortText"],["links.title","ShortText"]],["http://example.org/","This is test record 1!",["http://example.net/","http://example.org/","http://example.com/"],["test record 2.","This is test record 1!","test test record three."]]]]]
 .ft P
 .fi
 .sp
-このように、複数の参照関係が保存できました。また、output_columnsによって、複数の参照先のカラム値も表示させることができました。
+The only difference at the first step is the \fIflags\fP parameter that specifies to create a vector column. The \fItype\fP parameter of the \fB/commands/column_create\fP command is the same as in the previous example. Then, the \fB/commands/load\fP command registers three links from "\fI\%http://example.org/\fP" to "\fI\%http://example.net/\fP", "\fI\%http://example.org/\fP" and "\fI\%http://example.com/\fP". After that, the links are confirmed by the \fB/commands/select\fP command. In this case, the primary keys and the titles are output as arrays because links._key and links.title are specified to the \fIoutput_columns\fP parameter.
 .SS さまざまな検索条件の指定
 .sp
 groongaは、JavaScriptに似た文法での条件絞込や、計算した値を用いたソートを行うことができます。また、位置情報(緯度・経度)を用いた絞込・ソートを行うことができます。
@@ -5741,6 +6004,33 @@ find any records.
 .B Default:
 \fBauto\fP
 .UNINDENT
+.TP
+.B \fBsimilar_search\fP
+It specifies whether optional similar search is used or not
+in correction.
+.sp
+Here are available values:
+.INDENT 7.0
+.INDENT 3.5
+.INDENT 0.0
+.TP
+.B \fByes\fP
+Similar search is always used.
+.TP
+.B \fBno\fP
+Similar search is never used.
+.TP
+.B \fBauto\fP
+Similar search is used only when other search can\(aqt
+find any records.
+.UNINDENT
+.UNINDENT
+.UNINDENT
+.INDENT 7.0
+.TP
+.B Default:
+\fBauto\fP
+.UNINDENT
 .UNINDENT
 .SS RETURN VALUE
 .SS JSON format
@@ -6260,123 +6550,132 @@ groongaのデータベースでは、テーブルの主キーや、カラムの
 \fBObject\fP
 .INDENT 0.0
 .INDENT 3.5
-任意のテーブルに属する全てのレコード [1]
+任意のテーブルに属する全てのレコードです。 [1]
 .UNINDENT
 .UNINDENT
 .sp
 \fBBool\fP
 .INDENT 0.0
 .INDENT 3.5
-bool型。trueとfalse。
+ブーリアン型やブール型などと呼ばれる型であり、真偽値を表します。取り得る値はtrueとfalseです。（デフォルト値: false）
+.sp
+\fB/commands/load\fP コマンドで値を格納するときは、false、0、空文字列のいずれかを指定するとfalseになり、それ以外を指定するとtrueになります。
 .UNINDENT
 .UNINDENT
 .sp
 \fBInt8\fP
 .INDENT 0.0
 .INDENT 3.5
-8bit符号付き整数。
+8bit符号付き整数であり、\-128以上127以下の整数を表します。（デフォルト値: 0）
 .UNINDENT
 .UNINDENT
 .sp
 \fBUInt8\fP
 .INDENT 0.0
 .INDENT 3.5
-8bit符号なし整数。
+8bit符号なし整数であり、0以上255以下の整数を表します。（デフォルト値: 0）
 .UNINDENT
 .UNINDENT
 .sp
 \fBInt16\fP
 .INDENT 0.0
 .INDENT 3.5
-16bit符号付き整数。
+16bit符号付き整数であり、\-32,768以上32,767以下の整数を表します。（デフォルト値: 0）
 .UNINDENT
 .UNINDENT
 .sp
 \fBUInt16\fP
 .INDENT 0.0
 .INDENT 3.5
-16bit符号なし整数。
+16bit符号なし整数であり、0以上65,535以下の整数を表します。（デフォルト値: 0）
 .UNINDENT
 .UNINDENT
 .sp
 \fBInt32\fP
 .INDENT 0.0
 .INDENT 3.5
-32bit符号付き整数。
+32bit符号付き整数であり、\-2,147,483,648以上2,147,483,647以下の整数を表します。（デフォルト値: 0）
 .UNINDENT
 .UNINDENT
 .sp
 \fBUInt32\fP
 .INDENT 0.0
 .INDENT 3.5
-32bit符号なし整数。
+32bit符号なし整数であり、0以上4,294,967,295以下の整数を表します。（デフォルト値: 0）
 .UNINDENT
 .UNINDENT
 .sp
 \fBInt64\fP
 .INDENT 0.0
 .INDENT 3.5
-64bit符号付き整数。
+64bit符号付き整数であり、\-9,223,372,036,854,775,808以上9,223,372,036,854,775,807以下の整数を表します。（デフォルト値: 0）
 .UNINDENT
 .UNINDENT
 .sp
 \fBUInt64\fP
 .INDENT 0.0
 .INDENT 3.5
-64bit符号なし整数。
+64bit符号なし整数であり、0以上18,446,744,073,709,551,615以下の整数を表します。（デフォルト値: 0）
 .UNINDENT
 .UNINDENT
 .sp
 \fBFloat\fP
 .INDENT 0.0
 .INDENT 3.5
-ieee754形式の64bit浮動小数点数。
+IEEE 754形式の倍精度浮動小数点数であり、実数を表します。（デフォルト値: 0.0）
+.sp
+IEEE 754形式の詳細については、 \fI\%IEEE 754 - Wikipedia\fP や \fI\%IEEE 754: Standard for Binary Floating-Point\fP を参照してください。
 .UNINDENT
 .UNINDENT
 .sp
 \fBTime\fP
 .INDENT 0.0
 .INDENT 3.5
-1970年1月1日0時0分0秒からの経過マイクロ秒数を64bit符号付き整数で表現した値。
+日時を表す型であり、1970年1月1日0時0分0秒からの経過時間を、マイクロ秒単位で64bit符号付き整数により表現します。（デフォルト値: 0）
+.sp
+\fB/commands/load\fP コマンドで値を格納するときは、1970年1月1日0時0分0秒からの経過秒数を指定します。秒単位より詳細な日時を指定するには、小数を使います。
 .UNINDENT
 .UNINDENT
 .sp
 \fBShortText\fP
 .INDENT 0.0
 .INDENT 3.5
-4Kbyte以下の文字列。
+4,095バイト以下の文字列を表します。（デフォルト値: ""）
 .UNINDENT
 .UNINDENT
 .sp
 \fBText\fP
 .INDENT 0.0
 .INDENT 3.5
-64Kbyte以下の文字列。
+65,535バイト以下の文字列を表します。（デフォルト値: ""）
 .UNINDENT
 .UNINDENT
 .sp
 \fBLongText\fP
 .INDENT 0.0
 .INDENT 3.5
-2Gbyte以下の文字列。
+2,147,483,647バイト以下の文字列を表します。（デフォルト値: ""）
 .UNINDENT
 .UNINDENT
 .sp
 \fBTokyoGeoPoint\fP
 .INDENT 0.0
 .INDENT 3.5
-日本測地系緯度経度座標。緯度と経度はミリ秒単位での整数。
-"経度のミリ秒x緯度のミリ秒"という文字列表現を持つ。
-度分秒形式であれば、x度y分z秒は(((x * 60) + y) * 60 + z) * 1000という計算式で変換した値を代入します。
+旧日本測地系による経緯度であり、経度と緯度をミリ秒単位で表現した整数の組により表現します。（デフォルト値: 0x0）
+.sp
+度分秒形式でx度y分z秒となる経度・緯度は、(((x * 60) + y) * 60 + z) * 1000という計算式でミリ秒単位へと変換されます。
+\fB/commands/load\fP コマンドで値を格納するときは、"ミリ秒単位の経度xミリ秒単位の緯度" もしくは "経度の小数表記x緯度の小数表記" という文字列表現を使って指定します。経度と緯度の区切りとしては、\(aqx\(aq のほかに \(aq,\(aq を使うことができます。
+.sp
+測地系の詳細については、 \fI\%測地系 - Wikipedia\fP を参照してください。
 .UNINDENT
 .UNINDENT
 .sp
 \fBWGS84GeoPoint\fP
 .INDENT 0.0
 .INDENT 3.5
-世界測地系緯度経度座標。緯度と経度はミリ秒単位での整数。
-"経度のミリ秒x緯度のミリ秒"という文字列表現を持つ。
-度分秒形式であれば、x度y分z秒は(((x * 60) + y) * 60 + z) * 1000という計算式で変換した値を代入します。
+世界測地系（World Geodetic System, WGS 84）による経緯度であり、経度と緯度をミリ秒単位で表現した整数の組により表現します。（デフォルト値: 0x0）
+.sp
+度分秒形式からミリ秒形式への変換方法や \fB/commands/load\fP コマンドにおける指定方法はTokyoGeoPointと同じです。
 .UNINDENT
 .UNINDENT
 .SS 型に関する制限事項