rroonga 5.1.1-x86-mingw32 → 6.0.0-x86-mingw32

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/lock_acquire.txt

@@ -0,0 +1,102 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: lock_acquire
+
+``lock_acquire``
+================
+
+Summary
+-------
+
+.. versionadded:: 5.1.2
+
+``lock_acquire`` command acquires the lock of the target object. The
+target object is one of database, table and column.
+
+.. note::
+
+   This is a dangerous command. You must release locks by
+   :doc:`lock_release` that you acquire when these locks are no longer
+   needed. If you forget to release these locks, your database may be
+   broken.
+
+Syntax
+------
+
+This command takes only one optional parameter::
+
+  lock_clear [target_name=null]
+
+If ``target_name`` parameters is omitted, database is used for the
+target object.
+
+Usage
+-----
+
+Here is an example to acquire the lock of the database:
+
+.. groonga-command
+.. include:: ../../example/reference/commands/lock_acquire/database.log
+.. lock_acquire
+
+If the database is locked, you can't create a new table and
+column. Release the lock of the database to show another examples.
+
+.. groonga-command
+.. include:: ../../example/reference/commands/lock_acquire/database_release.log
+.. lock_release
+
+Here is an example to acquire the lock of ``Entries`` table:
+
+.. groonga-command
+.. include:: ../../example/reference/commands/lock_acquire/table.log
+.. table_create Entries TABLE_NO_KEY
+.. lock_acquire Entries
+
+Here is an example to acquire the lock of ``Sites.title`` column:
+
+.. groonga-command
+.. include:: ../../example/reference/commands/lock_acquire/column.log
+.. table_create Sites TABLE_HASH_KEY ShortText
+.. column_create Sites title COLUMN_SCALAR ShortText
+.. lock_acquire Sites.title
+
+Parameters
+----------
+
+This section describes all parameters.
+
+``target_name``
+"""""""""""""""
+
+Specifies the name of table or column.
+
+If you don't specify it, database is used for the target object.
+
+The default is none. It means that the target object is database.
+
+Return value
+------------
+
+``lock_acquire`` command returns whether lock is acquired or not::
+
+ [HEADER, SUCCEEDED_OR_NOT]
+
+``HEADER``
+""""""""""
+
+See :doc:`/reference/command/output_format` about ``HEADER``.
+
+``SUCCEEDED_OR_NOT``
+""""""""""""""""""""
+
+If command succeeded, it returns true, otherwise it returns false on error.
+
+See also
+--------
+
+  * :doc:`lock_release`
+  * :doc:`lock_clear`

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/lock_clear.txt

@@ -42,22 +42,22 @@ Here is an example to clear all locks in the database:
 .. include:: ../../example/reference/commands/lock_clear/database.log
 .. lock_clear
 
-Here is an example to clear locks of ``Entry`` table and ``Entry``
+Here is an example to clear locks of ``Entries`` table and ``Entries``
 table columns:
 
 .. groonga-command
 .. include:: ../../example/reference/commands/lock_clear/table.log
-.. table_create Entry TABLE_NO_KEY
-.. column_create Entry body COLUMN_SCALAR Text
-.. lock_clear Entry
+.. table_create Entries TABLE_NO_KEY
+.. column_create Entries body COLUMN_SCALAR Text
+.. lock_clear Entries
 
-Here is an example to clear the lock of ``Site.title`` column:
+Here is an example to clear the lock of ``Sites.title`` column:
 
 .. groonga-command
 .. include:: ../../example/reference/commands/lock_clear/column.log
-.. table_create Site TABLE_HASH_KEY ShortText
-.. column_create Site title COLUMN_SCALAR ShortText
-.. lock_clear Site.title
+.. table_create Sites TABLE_HASH_KEY ShortText
+.. column_create Sites title COLUMN_SCALAR ShortText
+.. lock_clear Sites.title
 
 Parameters
 ----------
@@ -76,7 +76,8 @@ The default is none. It means that the target object is database.
 Return value
 ------------
 
-``lock_clear`` command returns whether lock is acquired or not::
+``lock_clear`` command returns whether lock is cleared successfully or
+not::
 
  [HEADER, SUCCEEDED_OR_NOT]
 

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/lock_release.txt

@@ -0,0 +1,98 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: lock_release
+
+``lock_release``
+================
+
+Summary
+-------
+
+.. versionadded:: 5.1.2
+
+``lock_release`` command releases the lock of the target object. The
+target object is one of database, table and column.
+
+.. note::
+
+   This is a dangerous command. You must only release locks that you
+   acquire by :doc:`lock_acquire`. If you release locks without
+   :doc:`lock_acquire`, your database may be broken.
+
+Syntax
+------
+
+This command takes only one optional parameter::
+
+  lock_clear [target_name=null]
+
+If ``target_name`` parameters is omitted, database is used for the
+target object.
+
+Usage
+-----
+
+Here is an example to release the lock of the database:
+
+.. groonga-command
+.. include:: ../../example/reference/commands/lock_release/database.log
+.. lock_acquire
+.. lock_release
+
+Here is an example to release the lock of ``Entries`` table:
+
+.. groonga-command
+.. include:: ../../example/reference/commands/lock_release/table.log
+.. table_create Entries TABLE_NO_KEY
+.. lock_acquire Entries
+.. lock_release Entries
+
+Here is an example to release the lock of ``Sites.title`` column:
+
+.. groonga-command
+.. include:: ../../example/reference/commands/lock_release/column.log
+.. table_create Sites TABLE_HASH_KEY ShortText
+.. column_create Sites title COLUMN_SCALAR ShortText
+.. lock_acquire Sites.title
+.. lock_release Sites.title
+
+Parameters
+----------
+
+This section describes all parameters.
+
+``target_name``
+"""""""""""""""
+
+Specifies the name of table or column.
+
+If you don't specify it, database is used for the target object.
+
+The default is none. It means that the target object is database.
+
+Return value
+------------
+
+``lock_release`` command returns whether lock is released successfully
+or not::
+
+ [HEADER, SUCCEEDED_OR_NOT]
+
+``HEADER``
+""""""""""
+
+See :doc:`/reference/command/output_format` about ``HEADER``.
+
+``SUCCEEDED_OR_NOT``
+""""""""""""""""""""
+
+If command succeeded, it returns true, otherwise it returns false on error.
+
+See also
+--------
+
+  * :doc:`lock_acquire`
+  * :doc:`lock_clear`

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/object_exist.txt

@@ -40,10 +40,10 @@ You can check whether the name is already used in database:
 .. table_create Users TABLE_HASH_KEY ShortText
 .. object_exist Users
 
-The ``object_exist Users`` returns ``false`` before we create
+The ``object_exist Users`` returns ``false`` before you create
 ``Users`` table.
 
-The ``object_exist Users`` returns ``true`` after we create ``Users``
+The ``object_exist Users`` returns ``true`` after you create ``Users``
 table.
 
 Parameters
@@ -75,6 +75,11 @@ If you want to check existence of a column, use
 ``Logs`` is table name and ``timestamp`` is column name in
 ``Logs.timestamp``.
 
+Optional parameters
+^^^^^^^^^^^^^^^^^^^
+
+There is no optional parameters.
+
 Return value
 ------------
 

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/commands/object_inspect.txt

@@ -0,0 +1,385 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+.. groonga-command
+.. database: commands_object_inspect
+
+``object_inspect``
+==================
+
+Summary
+-------
+
+.. versionadded:: 6.0.0
+
+``object_inspect`` inspects an object. You can confirm details of an
+object.
+
+For example:
+
+  * If the object is a table, you can confirm the number of records in
+    the table.
+
+  * If the object is a column, you can confirm the type of value of
+    the column.
+
+Syntax
+------
+
+This command takes only one optional parameter::
+
+  object_inspect [name=null]
+
+Usage
+-----
+
+You can inspect an object in the database specified by ``name``:
+
+.. groonga-command
+.. include:: ../../example/reference/commands/object_inspect/usage-name.log
+.. table_create Users TABLE_HASH_KEY ShortText
+.. load --table Users
+.. [
+.. {"_key": "Alice"}
+.. ]
+.. object_inspect Users
+
+The ``object_inspect Users`` returns the following information:
+
+  * The name of the table: ``"name": Users``
+
+  * The total used key size: ``"key": {"total_size": 5}``
+    (``"Alice"`` is 5 byte data)
+
+  * The maximum total key size: ``"key": {"max_total_size": 4294967295}``
+
+  * and so on.
+
+You can inspect the database by not specifying ``name``:
+
+.. groonga-command
+.. include:: ../../example/reference/commands/object_inspect/usage-database.log
+.. object_inspect
+
+The ``object_inspect`` returns the following information:
+
+  * The table type for object name management:
+    ``"key": {"type": {"name": "table:dat_key"}}``
+
+  * and so on.
+
+Parameters
+----------
+
+This section describes all parameters.
+
+Required parameters
+^^^^^^^^^^^^^^^^^^^
+
+There is no required parameters.
+
+Optional parameters
+^^^^^^^^^^^^^^^^^^^
+
+There is only one optional parameter.
+
+.. _object-inspect-name:
+
+``name``
+""""""""
+
+Specifies the object name to be inspected.
+
+If ``name`` isn't specified, the database is inspected.
+
+Return value
+------------
+
+The command returns an object (nested key and value pairs) that
+includes details of the object (such as table) as body::
+
+  [HEADER, object]
+
+See :doc:`/reference/command/output_format` for ``HEADER``.
+
+The format of the details is depends on object type. For example,
+table has key information but function doesn't have key information.
+
+.. _object-inspect-return-value-database:
+
+Database
+^^^^^^^^
+
+Database inspection returns the following information::
+
+  {
+    "type": {
+      "id": DATABASE_TYPE_ID,
+      "name": DATABASE_TYPE_NAME
+    },
+    "name_table": DATABASE_NAME_TABLE
+  }
+
+.. _object-inspect-return-value-database-type-id:
+
+``DATABASE_TYPE_ID``
+""""""""""""""""""""
+
+``DATABASE_TYPE_ID`` is always ``55``.
+
+.. _object-inspect-return-value-database-type-name:
+
+``DATABASE_TYPE_NAME``
+""""""""""""""""""""""
+
+``DATABASE_TYPE_NAME`` is always ``"db"``.
+
+.. _object-inspect-return-value-database-name-table:
+
+``DATABASE_NAME_TABLE``
+"""""""""""""""""""""""
+
+``DATABASE_NAME_TABLE`` is a table for managing object names in the
+database. The table is :ref:`table-pat-key` or
+:ref:`table-dat-key`. Normally, it's :ref:`table-dat-key`.
+
+See :ref:`object-inspect-return-value-table` for format details.
+
+.. _object-inspect-return-value-table:
+
+Table
+^^^^^
+
+Table inspection returns the following information::
+
+  {
+    "name": TABLE_NAME,
+    "type": {
+      "id": TABLE_TYPE_ID,
+      "name": TABLE_TYPE_NAME
+    },
+    "key": {
+      "type": TABLE_KEY_TYPE,
+      "total_size": TABLE_KEY_TOTAL_SIZE
+      "max_total_size": TABLE_KEY_MAX_TOTAL_SIZE
+    },
+    "value": {
+      "type": TABLE_VALUE_TYPE,
+    },
+    "n_records": TABLE_N_RECORDS
+  }
+
+There are some exceptions:
+
+  * :ref:`table-no-key` doesn't return key information because it
+    doesn't have key.
+
+  * :ref:`table-dat-key` doesn't return value information because it
+    doesn't have value.
+
+.. _object-inspect-return-value-table-name:
+
+``TABLE_NAME``
+""""""""""""""
+
+The name of the inspected table.
+
+.. _object-inspect-return-value-table-type-id:
+
+``TABLE_TYPE_ID``
+"""""""""""""""""
+
+The type ID of the inspected table.
+
+Here is a list of type IDs:
+
+.. list-table::
+   :header-rows: 1
+
+   * - Table type
+     - ID
+   * - :ref:`table-hash-key`
+     - ``48``
+   * - :ref:`table-pat-key`
+     - ``49``
+   * - :ref:`table-dat-key`
+     - ``50``
+   * - :ref:`table-no-key`
+     - ``51``
+
+.. _object-inspect-return-value-table-type-name:
+
+``TABLE_TYPE_NAME``
+"""""""""""""""""""
+
+The type name of the inspected table.
+
+Here is a list of type names:
+
+.. list-table::
+   :header-rows: 1
+
+   * - Table type
+     - Name
+   * - :ref:`table-hash-key`
+     - ``"table:hash_key"``
+   * - :ref:`table-pat-key`
+     - ``"table:pat_key"``
+   * - :ref:`table-dat-key`
+     - ``"table:dat_key"``
+   * - :ref:`table-no-key`
+     - ``"table:no_key"``
+
+.. _object-inspect-return-value-table-key-type:
+
+``TABLE_KEY_TYPE``
+""""""""""""""""""
+
+The type of key of the inspected table.
+
+See :ref:`object-inspect-return-value-type` for format details.
+
+.. _object-inspect-return-value-table-total-key-size:
+
+``TABLE_KEY_TOTAL_SIZE``
+""""""""""""""""""""""""
+
+The total key size of the inspected table in bytes.
+
+.. _object-inspect-return-value-table-max-total-key-size:
+
+``TABLE_KEY_MAX_TOTAL_SIZE``
+""""""""""""""""""""""""""""
+
+The maximum total key size of the inspected table in bytes.
+
+.. _object-inspect-return-value-table-value-type:
+
+``TABLE_VALUE_TYPE``
+""""""""""""""""""""
+
+The type of value of the inspected table.
+
+See :ref:`object-inspect-return-value-type` for format details.
+
+.. _object-inspect-return-value-table-n-records:
+
+``TABLE_N_RECORDS``
+"""""""""""""""""""
+
+The number of records of the inspected table.
+
+It's a 64bit unsigned integer value.
+
+.. _object-inspect-return-value-type:
+
+Type
+""""
+
+Type inspection returns the following information::
+
+  {
+    "id": TYPE_ID,
+    "name": TYPE_NAME,
+    "type": {
+      "id": TYPE_ID_OF_TYPE,
+      "name": TYPE_NAME_OF_TYPE
+    },
+    "size": TYPE_SIZE
+  }
+
+.. _object-inspect-return-value-type-id:
+
+``TYPE_ID``
+"""""""""""
+
+The ID of the inspected type.
+
+Here is an ID list of builtin types:
+
+.. list-table::
+   :header-rows: 1
+
+   * - Type
+     - ID
+   * - :ref:`builtin-type-bool`
+     - ``3``
+   * - :ref:`builtin-type-int8`
+     - ``4``
+   * - :ref:`builtin-type-uint8`
+     - ``5``
+   * - :ref:`builtin-type-int16`
+     - ``6``
+   * - :ref:`builtin-type-uint16`
+     - ``7``
+   * - :ref:`builtin-type-int32`
+     - ``8``
+   * - :ref:`builtin-type-uint32`
+     - ``9``
+   * - :ref:`builtin-type-int64`
+     - ``10``
+   * - :ref:`builtin-type-uint64`
+     - ``11``
+   * - :ref:`builtin-type-float`
+     - ``12``
+   * - :ref:`builtin-type-time`
+     - ``13``
+   * - :ref:`builtin-type-short-text`
+     - ``14``
+   * - :ref:`builtin-type-text`
+     - ``15``
+   * - :ref:`builtin-type-long-text`
+     - ``16``
+   * - :ref:`builtin-type-tokyo-geo-point`
+     - ``17``
+   * - :ref:`builtin-type-wgs84-geo-point`
+     - ``18``
+
+.. _object-inspect-return-value-type-name:
+
+``TYPE_NAME``
+"""""""""""""
+
+The name of the inspected type.
+
+Here is a name list of builtin types:
+
+  * :ref:`builtin-type-bool`
+  * :ref:`builtin-type-int8`
+  * :ref:`builtin-type-uint8`
+  * :ref:`builtin-type-int16`
+  * :ref:`builtin-type-uint16`
+  * :ref:`builtin-type-int32`
+  * :ref:`builtin-type-uint32`
+  * :ref:`builtin-type-int64`
+  * :ref:`builtin-type-uint64`
+  * :ref:`builtin-type-float`
+  * :ref:`builtin-type-time`
+  * :ref:`builtin-type-short-text`
+  * :ref:`builtin-type-text`
+  * :ref:`builtin-type-long-text`
+  * :ref:`builtin-type-tokyo-geo-point`
+  * :ref:`builtin-type-wgs84-geo-point`
+
+.. _object-inspect-return-value-type-id-of-type:
+
+``TYPE_ID_OF_TYPE``
+"""""""""""""""""""
+
+``TYPE_ID_OF_TYPE`` is always ``32``.
+
+.. _object-inspect-return-value-type-name-of-type:
+
+``TYPE_NAME_OF_TYPE``
+"""""""""""""""""""""
+
+``TYPE_NAME_OF_TYPE`` is always ``type``.
+
+.. _object-inspect-return-value-type-size:
+
+``TYPE_SIZE``
+"""""""""""""
+
+``TYPE_SIZE`` is the size of the inspected type in bytes. If the
+inspected type is variable size type, the size means the maximum size.