RubyGems - rroonga - Versions diffs - 7.0.2-x64-mingw32 → 7.1.1-x64-mingw32 - Mend

rroonga 7.0.2-x64-mingw32 → 7.1.1-x64-mingw32

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1237) hide show

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/command/return_code.txt DELETED Viewed

@@ -1,117 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-Return code
-===========
-Summary
--------
-Return code is used to show whether a processing is succeeded or
-not. If the processing is not succeeded, return code shows error type.
-Return code is used in C API and query API. You can check return code
-via ``grn_ctx_t::rc`` in C API. You can check return code by looking
-the header element in query API. See :doc:`output_format` about the
-header element in query API.
-List
-----
-Here is a list of return codes. ``GRN_SUCCESS`` (= 0) means that the
-processing is succeeded. Return codes that have negative value show
-error type. ``GRN_END_OF_DATA`` is a special return code. It is used
-only C API. It is not showen in query API.
-* 0: ``GRN_SUCCESS``
-* 1: ``GRN_END_OF_DATA``
-* -1: ``GRN_UNKNOWN_ERROR``
-* -2: ``GRN_OPERATION_NOT_PERMITTED``
-* -3: ``GRN_NO_SUCH_FILE_OR_DIRECTORY``
-* -4: ``GRN_NO_SUCH_PROCESS``
-* -5: ``GRN_INTERRUPTED_FUNCTION_CALL``
-* -6: ``GRN_INPUT_OUTPUT_ERROR``
-* -7: ``GRN_NO_SUCH_DEVICE_OR_ADDRESS``
-* -8: ``GRN_ARG_LIST_TOO_LONG``
-* -9: ``GRN_EXEC_FORMAT_ERROR``
-* -10: ``GRN_BAD_FILE_DESCRIPTOR``
-* -11: ``GRN_NO_CHILD_PROCESSES``
-* -12: ``GRN_RESOURCE_TEMPORARILY_UNAVAILABLE``
-* -13: ``GRN_NOT_ENOUGH_SPACE``
-* -14: ``GRN_PERMISSION_DENIED``
-* -15: ``GRN_BAD_ADDRESS``
-* -16: ``GRN_RESOURCE_BUSY``
-* -17: ``GRN_FILE_EXISTS``
-* -18: ``GRN_IMPROPER_LINK``
-* -19: ``GRN_NO_SUCH_DEVICE``
-* -20: ``GRN_NOT_A_DIRECTORY``
-* -21: ``GRN_IS_A_DIRECTORY``
-* -22: ``GRN_INVALID_ARGUMENT``
-* -23: ``GRN_TOO_MANY_OPEN_FILES_IN_SYSTEM``
-* -24: ``GRN_TOO_MANY_OPEN_FILES``
-* -25: ``GRN_INAPPROPRIATE_I_O_CONTROL_OPERATION``
-* -26: ``GRN_FILE_TOO_LARGE``
-* -27: ``GRN_NO_SPACE_LEFT_ON_DEVICE``
-* -28: ``GRN_INVALID_SEEK``
-* -29: ``GRN_READ_ONLY_FILE_SYSTEM``
-* -30: ``GRN_TOO_MANY_LINKS``
-* -31: ``GRN_BROKEN_PIPE``
-* -32: ``GRN_DOMAIN_ERROR``
-* -33: ``GRN_RESULT_TOO_LARGE``
-* -34: ``GRN_RESOURCE_DEADLOCK_AVOIDED``
-* -35: ``GRN_NO_MEMORY_AVAILABLE``
-* -36: ``GRN_FILENAME_TOO_LONG``
-* -37: ``GRN_NO_LOCKS_AVAILABLE``
-* -38: ``GRN_FUNCTION_NOT_IMPLEMENTED``
-* -39: ``GRN_DIRECTORY_NOT_EMPTY``
-* -40: ``GRN_ILLEGAL_BYTE_SEQUENCE``
-* -41: ``GRN_SOCKET_NOT_INITIALIZED``
-* -42: ``GRN_OPERATION_WOULD_BLOCK``
-* -43: ``GRN_ADDRESS_IS_NOT_AVAILABLE``
-* -44: ``GRN_NETWORK_IS_DOWN``
-* -45: ``GRN_NO_BUFFER``
-* -46: ``GRN_SOCKET_IS_ALREADY_CONNECTED``
-* -47: ``GRN_SOCKET_IS_NOT_CONNECTED``
-* -48: ``GRN_SOCKET_IS_ALREADY_SHUTDOWNED``
-* -49: ``GRN_OPERATION_TIMEOUT``
-* -50: ``GRN_CONNECTION_REFUSED``
-* -51: ``GRN_RANGE_ERROR``
-* -52: ``GRN_TOKENIZER_ERROR``
-* -53: ``GRN_FILE_CORRUPT``
-* -54: ``GRN_INVALID_FORMAT``
-* -55: ``GRN_OBJECT_CORRUPT``
-* -56: ``GRN_TOO_MANY_SYMBOLIC_LINKS``
-* -57: ``GRN_NOT_SOCKET``
-* -58: ``GRN_OPERATION_NOT_SUPPORTED``
-* -59: ``GRN_ADDRESS_IS_IN_USE``
-* -60: ``GRN_ZLIB_ERROR``
-* -61: ``GRN_LZO_ERROR``
-* -62: ``GRN_STACK_OVER_FLOW``
-* -63: ``GRN_SYNTAX_ERROR``
-* -64: ``GRN_RETRY_MAX``
-* -65: ``GRN_INCOMPATIBLE_FILE_FORMAT``
-* -66: ``GRN_UPDATE_NOT_ALLOWED``
-* -67: ``GRN_TOO_SMALL_OFFSET``
-* -68: ``GRN_TOO_LARGE_OFFSET``
-* -69: ``GRN_TOO_SMALL_LIMIT``
-* -70: ``GRN_CAS_ERROR``
-* -71: ``GRN_UNSUPPORTED_COMMAND_VERSION``
-* -72: ``GRN_NORMALIZER_ERROR``
-* -73: ``GRN_TOKEN_FILTER_ERROR``
-* -74: ``GRN_COMMAND_ERROR``
-* -75: ``GRN_PLUGIN_ERROR``
-* -76: ``GRN_SCORER_ERROR``
-* -77: ``GRN_CANCEL``
-* -78: ``GRN_WINDOW_FUNCTION_ERROR``
-See also
---------
-* :doc:`output_format` shows where return code is appeared in query
-  API response.
-* :doc:`/spec/gqtp`: GQTP protocol also uses return code as status but
-  it uses 2byte unsigned integer. So return codes that have negative
-  value are statuses that have positive value in GQTP protocol. You
-  can convert status value in GQTP protocol to return code by
-  handling it as 2byte signed integer.

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/cache_limit.txt DELETED Viewed

@@ -1,87 +0,0 @@
-.. -*- rst -*-
-.. Groonga Project
-.. highlightlang:: none
-.. groonga-command
-.. database: commands_cache_limit
-``cache_limit``
-===============
-Summary
--------
-``cache_limit`` gets or sets the max number of query cache
-entries. Query cache is used only by :doc:`select` command.
-If the max number of query cache entries is 100, the recent 100
-``select`` commands are only cached. The cache expire algorithm is LRU
-(least recently used).
-Syntax
-------
-This command takes only one optional parameter::
-  cache_limit [max=null]
-Usage
------
-You can get the current max number of cache entries by executing
-``cache_limit`` without parameter.
-.. groonga-command
-.. include:: ../../example/reference/commands/cache_limit/get.log
-.. cache_limit
-You can set the max number of cache entries by executing ``cache_limit``
-with ``max`` parameter.
-Here is an example that sets ``10`` as the max number of cache
-entries.
-.. groonga-command
-.. include:: ../../example/reference/commands/cache_limit/set.log
-.. cache_limit 10
-.. cache_limit
-If ``max`` parameter is used, the return value is the max number of
-cache entries before ``max`` parameter is set.
-Parameters
-----------
-This section describes all parameters.
-``max``
-"""""""
-Specifies the max number of query cache entries as a number.
-If ``max`` parameter isn't specified, the current max number of query
-cache entries isn't changed. ``cache_limit`` just returns the current
-max number of query cache entries.
-Return value
-------------
-``cache_limit`` returns the current max number of query cache entries::
-  [HEADER, N_ENTRIES]
-``HEADER``
-  See :doc:`/reference/command/output_format` about ``HEADER``.
-``N_ENTRIES``
-  ``N_ENTRIES`` is the current max number of query cache entries. It
-  is a number.
-See also
---------
-* :doc:`select`

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/check.txt DELETED Viewed

@@ -1,161 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-``check``
-=========
-Summary
--------
-check - オブジェクトの状態表示
-Groonga組込コマンドの一つであるcheckについて説明します。組込コマンドは、groonga実行ファイルの引数、標準入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
-checkコマンドは、groongaプロセス内の指定したオブジェクトの状態を表示します。主にデータベースが壊れた場合など異常時の問題解決のために使用することを想定しています。デバッグ用のため、返値のフォーマットが安定しているということは保証されません。（フォーマットが変更される可能性が高い）
-Syntax
-------
-::
- check obj
-Usage
------
-テーブルTermsのインデックスカラムnameの状態を表示します。::
- check Terms.name
- [{"flags":"00008202",
-   "max sid":1,
-   "number of garbage segments":0,
-   "number of array segments":1,
-   "max id of array segment":1,
-   "number of buffer segments":110,
-   "max id of buffer segment":111,
-   "max id of physical segment in use":111,
-   "number of unmanaged segments":4294967185,
-   "total chunk size":7470239,
-   "max id of chunk segments in use":127,
-   "number of garbage chunk":[0,0,0,0,0,0,0,0,2,2,0,0,0,0,0]},
-  {"buffer id":0,
-   "chunk size":94392,
-   "buffer term":["596","59777","6",...],
-   "buffer free":152944,
-   "size in buffer":7361,
-   "nterms":237,
-   "nterms with chunk":216,
-   "buffer id":1,
-   "chunk size":71236,
-   "buffer term":[["に述",18149,18149,2,25,6,6],
-                  ["に追",4505,4505,76,485,136,174],
-                  ["に退",26568,26568,2,9,2,2],
-                  ...],
-   "buffer free":120000,
-   "size in buffer":11155,
-   "nterms":121,
-   "nterms with chunk":116},
-   {"buffer id":1,
-    ...},
-   ...]
-Parameters
-----------
-``obj``
-  状態を表示するオブジェクトの名前を指定します。
-Return value
-------------
-チェックするオブジェクトにより返される値が変わります。
-インデックスカラムの場合::
-  下記のような配列が出力されます。
-    [インデックスの状態, バッファの状態1, バッファの状態2, ...]
-``インデックスの状態`` には下記の項目がハッシュ形式で出力されます。
-  ``flags``
-    指定されているフラグ値です。16進数で表現されています。
-  ``max sid``
-    セグメントのうち最も大きなIDです。
-  ``number of garbage segments``
-    ゴミセグメントの数です。
-  ``number of array segments``
-    配列セグメントの数です。
-  ``max id of array segment``
-    配列セグメントのうち最も大きなIDです。
-  ``number of buffer segments``
-    バッファセグメントの数です。
-  ``max id of buffer segment``
-    バッファセグメントのうち最も大きなIDです。
-  ``max id of physical segment in use``
-    使用中の論理セグメントのうち最も大きなIDです。
-  ``number of unmanaged segments``
-    管理されていないセグメントの数です。
-  ``total chunk size``
-    チャンクサイズの合計です。
-  ``max id of chunk segments in use``
-    使用中のチャンクセグメントのうち最も大きなIDです。
-  ``number of garbage chunk``
-    各チャンク毎のゴミの数です。
-``バッファの状態`` には下記の項目がハッシュ形式で出力されます。
-  ``buffer id``
-    バッファIDです。
-  ``chunk size``
-    チャンクのサイズです。
-  ``buffer term``
-    バッファ内にある語の一覧です。各語の状態は以下のような配列となっています。
-      [語, バッファに登録されている語のID, 用語集に登録されている語のID, バッファ内でのサイズ, チャンク内でのサイズ]
-  ``buffer free``
-    バッファの空き容量です。
-  ``size in buffer``
-    バッファの使用量です。
-  ``nterms``
-    バッファ内にある語の数です。
-  ``nterms with chunk``
-    バッファ内にある語のうち、チャンクを使っている語の数です。

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/clearlock.txt DELETED Viewed

@@ -1,60 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-``clearlock``
-=============
-Summary
--------
-.. deprecated:: 4.0.9
-   Use :doc:`lock_clear` instead.
-clearlock - オブジェクトにセットされたロックを解除する
-Groonga組込コマンドの一つであるclearlockについて説明します。組込コマンドは、groonga実行ファイルの引数、標準>入力、またはソケット経由でgroongaサーバにリクエストを送信することによって実行します。
-clearlockは、対象となるオブジェクト(データベース,テーブル,インデックス等)を指定し、オブジェクトにかけられた>ロックを再帰的に解除します。
-Syntax
-------
-::
- clearlock objname
-Usage
------
-開いているデータベースのロックをすべて解除する::
- clearlock
- [true]
-テーブル名 Entry のカラム body のロックを解除する::
- clearlock Entry.body
- [true]
-Parameters
-----------
-``objname``
-  対象となるオブジェクト名を指定します。空の場合、開いているdbオブジェクトが対象となります。
-Return value
-------------
-::
- [成功かどうかのフラグ]
-``成功かどうかのフラグ``
-  エラーが生じなかった場合にはtrue、エラーが生じた場合にはfalseを返す。
-See also
---------
-:doc:`load`

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/column_copy.txt DELETED Viewed

@@ -1,381 +0,0 @@
-.. -*- rst -*-
-.. highlightlang:: none
-.. groonga-command
-.. database: commands_copy
-``column_copy``
-===============
-Summary
--------
-.. versionadded:: 5.0.7
-``column_copy`` copies all column values to other column.
-You can implement the following features with this command:
-  * Changing column configuration
-  * Changing table configuration
-You can change column configuration by the following steps:
-  1. Create a new column with new configuration
-  2. Copy all values from the current column to the new column
-  3. Remove the current column
-  4. Rename the new column to the current column
-You can change table configuration by the following steps:
-  1. Create a new table with new configuration
-  2. Create all same columns to the new table
-  3. Copy all column values from the current table to the new table
-  4. Remove the current table
-  5. Rename the new table to the current table
-Concrete examples are showed later.
-You can't copy column values from a ``TABLE_NO_KEY`` table to another
-table. And you can't copy column values to a ``TABLE_NO_KEY`` table
-from another table. Because Groonga can't map records without record
-key.
-You can copy column values from a ``TABLE_NO_KEY`` table to the same
-``TABLE_NO_KEY`` table.
-You can copy column values from a ``TABLE_HASH_KEY`` /
-``TABLE_PAT_KEY`` / ``TABLE_DAT_KEY`` table to the same or another
-``TABLE_HASH_KEY`` / ``TABLE_PAT_KEY`` / ``TABLE_DAT_KEY`` table.
-Syntax
-------
-This command takes four parameters.
-All parameters are required::
-  column_copy from_table
-              from_name
-              to_table
-              to_name
-Usage
------
-Here are use cases of this command:
-  * Changing column configuration
-  * Changing table configuration
-How to change column configuration
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-You can change column value type. For example, you can change
-``UInt32`` column value to ``ShortText`` column value.
-You can change column type. For example, you can change
-``COLUMN_SCALAR`` column to ``COLUMN_VECTOR`` column.
-You can move a column to other table. For example, you can move
-``high_score`` column to ``Users`` table from ``Players`` table.
-Here are basic steps to change column configuration:
-  1. Create a new column with new configuration
-  2. Copy all values from the current column to the new column
-  3. Remove the current column
-  4. Rename the new column to the current column
-Here is an example to change column value type to ``Int32`` from
-``ShortText``.
-Here are schema and data:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/change_column_value_type_setup.log
-.. table_create Logs TABLE_HASH_KEY ShortText
-.. column_create Logs serial COLUMN_SCALAR Int32
-.. load --table Logs
-.. [
-.. {"_key": "log1", "serial": 1}
-.. ]
-The following commands change ``Logs.serial`` column value type to
-``ShortText`` from ``Int32``:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/change_column_value_type.log
-.. column_create Logs new_serial COLUMN_SCALAR ShortText
-.. column_copy Logs serial Logs new_serial
-.. column_remove Logs serial
-.. column_rename Logs new_serial serial
-.. select Logs
-You can find ``Logs.serial`` stores ``ShortText`` value from the
-response of ``select``.
-Here is an example to change column type to ``COLUMN_VECTOR`` from
-``COLUMN_SCALAR``.
-Here are schema and data:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/change_column_type_setup.log
-.. table_create Entries TABLE_HASH_KEY ShortText
-.. column_create Entries tag COLUMN_SCALAR ShortText
-.. load --table Entries
-.. [
-.. {"_key": "entry1", "tag": "Groonga"}
-.. ]
-The following commands change ``Entries.tag`` column to
-``COLUMN_VECTOR`` from ``COLUMN_SCALAR``:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/change_column_type.log
-.. column_create Entries new_tag COLUMN_VECTOR ShortText
-.. column_copy Entries tag Entries new_tag
-.. column_remove Entries tag
-.. column_rename Entries new_tag tag
-.. select Entries
-You can find ``Entries.tag`` stores ``COLUMN_VECTOR`` value from the
-response of ``select``.
-Here is an example to move ``high_score`` column to ``Users`` table
-from ``Players`` table.
-Here are schema and data:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/move_column_setup.log
-.. table_create Players TABLE_HASH_KEY ShortText
-.. column_create Players high_score COLUMN_SCALAR Int32
-.. load --table Players
-.. [
-.. {"_key": "player1", "high_score": 100}
-.. ]
-The following commands move ``high_score`` column to ``Users`` table
-from ``Players`` table:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/move_column.log
-.. table_create Users TABLE_HASH_KEY ShortText
-.. column_create Users high_score COLUMN_SCALAR Int32
-.. column_copy Players high_score Users high_score
-.. column_remove Players high_score
-.. select Users
-You can find ``Users.high_score`` is moved from ``Players.high_score``
-from the response of ``select``.
-How to change table configuration
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-You can change table key type. For example, you can change
-key type to ``ShortText`` from ``Int32``.
-You can change table type. For example, you can change
-``TABLE_HASH_KEY`` table to ``TABLE_PAT_KEY`` table.
-You can also change other options such as default tokenizer and
-normalizer. For example, you can change default tokenizer to
-``TokenBigramSplitSymbolAlphaDigit`` from ``TokenBigrm``.
-.. note::
-   You can't change ``TABLE_NO_KEY`` table. Because ``TABLE_NO_KEY``
-   doesn't have record key. Groonga can't identify copy destination
-   record without record key.
-Here are basic steps to change table configuration:
-  1. Create a new table with new configuration
-  2. Create all same columns to the new table
-  3. Copy all column values from the current table to the new table
-  4. Remove the current table
-  5. Rename the new table to the current table
-Here is an example to change table key type to ``ShortText`` from
-``Int32``.
-Here are schema and data:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/change_table_key_type_setup.log
-.. table_create IDs TABLE_HASH_KEY Int32
-.. column_create IDs label COLUMN_SCALAR ShortText
-.. column_create IDs used COLUMN_SCALAR Bool
-.. load --table IDs
-.. [
-.. {"_key": 100, "label": "ID 100", used: true}
-.. ]
-The following commands change ``IDs`` table key type to ``ShortText``
-from ``Int32``:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/change_table_key_type.log
-.. table_create NewIDs TABLE_HASH_KEY Int32
-.. column_create NewIDs label COLUMN_SCALAR ShortText
-.. column_create NewIDs used COLUMN_SCALAR Bool
-.. column_copy IDs label NewIDs label
-.. column_copy IDs used  NewIDs used
-.. table_remove IDs
-.. table_rename NewIDs IDs
-.. select IDs
-You can find ``IDs`` stores ``ShortText`` key from the response of
-``select``.
-Here is an example to change table type to ``TABLE_PAT_KEY`` from
-``TABLE_HASH_KEY``.
-Here are schema and data:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/change_table_type_setup.log
-.. table_create Names TABLE_HASH_KEY ShortText
-.. column_create Names used COLUMN_SCALAR Bool
-.. load --table Entries
-.. [
-.. {"_key": "alice", "used": false}
-.. ]
-The following commands change ``Names`` table to ``TABLE_PAT_KEY``
-from ``TABLE_HASH_KEY``:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/change_table_type.log
-.. table_create NewNames TABLE_PAT_KEY ShortText
-.. column_create NewNames used COLUMN_SCALAR Bool
-.. column_copy Names used NewNames used
-.. table_remove Names
-.. table_rename NewNames Names
-.. select Names --filter '_key @^ "ali"'
-You can find ``Names`` is a ``TABLE_PAT_KEY`` because ``select`` can
-use :ref:`script-syntax-prefix-search-operator`. You can't use
-:ref:`script-syntax-prefix-search-operator` with ``TABLE_HASH_KEY``.
-Parameters
-----------
-This section describes parameters.
-Required parameters
-^^^^^^^^^^^^^^^^^^^
-All parameters are required.
-.. _column-copy-from-table:
-``from_table``
-""""""""""""""
-Specifies the table name of source column.
-You can specify any table including ``TABLE_NO_KEY`` table.
-If you specify ``TABLE_NO_KEY`` table, :ref:`column-copy-to-table`
-must be the same table.
-Here is an example to use ``from_table``.
-Here are schema and data:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/from_table_setup.log
-.. table_create FromTable TABLE_HASH_KEY ShortText
-.. column_create FromTable from_column COLUMN_SCALAR ShortText
-.. column_create FromTable to_column   COLUMN_SCALAR ShortText
-.. load --table FromTable
-.. [
-.. {"_key": "key1", "from_column": "value1"}
-.. ]
-.. select FromTable --output_columns _key,from_column,to_column
-You can copy all values to ``to_column`` from ``from_column``:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/from_table.log
-.. column_copy FromTable from_column FromTable to_column
-.. select FromTable --output_columns _key,from_column,to_column
-.. _column-copy-from-name:
-``from_name``
-"""""""""""""
-Specifies the column name to be copied values.
-See :ref:`column-copy-from-table` for example.
-.. _column-copy-to-table:
-``to_table``
-""""""""""""
-Specifies the table name of destination column.
-You can specify the same table name as :ref:`column-copy-from-table`
-when you want to copy column values in the same table.
-You can't specify ``TABLE_NO_KEY`` table to ``to_table`` because
-Groonga can't identify destination records without record key.
-There is one exception. If you specify the same name as ``from_table``
-to ``to_table``, you can use ``TABLE_NO_KEY`` table as
-``to_table``. Because Groonga can identify destination records when
-source table and destination table is the same table.
-Here is an example to use ``to_table``.
-Here are schema and data:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/to_table_setup.log
-.. table_create Table TABLE_HASH_KEY ShortText
-.. column_create Table column COLUMN_SCALAR ShortText
-.. table_create ToTable TABLE_HASH_KEY ShortText
-.. column_create ToTable to_column COLUMN_SCALAR ShortText
-.. load --table Table
-.. [
-.. {"_key": "key1", "column": "value1"}
-.. ]
-You can copy all values to ``ToTable.to_column`` from
-``Table.column``:
-.. groonga-command
-.. include:: ../../example/reference/commands/column_copy/to_table.log
-.. column_copy Table column ToTable to_column
-.. select ToTable --output_columns _key,to_column
-.. _column-copy-to-name:
-``to_name``
-"""""""""""
-Specifies the destination column name.
-See :ref:`column-copy-to-table` for example.
-Optional parameters
-^^^^^^^^^^^^^^^^^^^
-There is no optional parameter.
-Return value
-------------
-The command returns ``true`` as body on success such as::
-  [HEADER, true]
-If the command fails, error details are in ``HEADER``.
-See :doc:`/reference/command/output_format` for ``HEADER``.