[Groonga-commit] pgroonga/pgroonga.github.io at 18e2372 [master] Translate @>

Back to archive index

Kouhei Sutou null+****@clear*****
Sun Oct 25 15:28:23 JST 2015


Kouhei Sutou	2015-10-25 15:28:23 +0900 (Sun, 25 Oct 2015)

  New Revision: 18e2372db84a17b9522092408d9af281343431b3
  https://github.com/pgroonga/pgroonga.github.io/commit/18e2372db84a17b9522092408d9af281343431b3

  Message:
    Translate @>

  Modified files:
    _po/ja/reference/operators/jsonb-contain.po
    ja/reference/operators/jsonb-contain.md
    reference/operators/jsonb-contain.md

  Modified: _po/ja/reference/operators/jsonb-contain.po (+29 -18)
===================================================================
--- _po/ja/reference/operators/jsonb-contain.po    2015-10-24 17:59:18 +0900 (a8c9259)
+++ _po/ja/reference/operators/jsonb-contain.po    2015-10-25 15:28:23 +0900 (5ce02af)
@@ -1,7 +1,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: PACKAGE VERSION\n"
-"PO-Revision-Date: 2015-10-24 17:58+0900\n"
+"PO-Revision-Date: 2015-10-25 15:28+0900\n"
 "Language: ja\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -29,16 +29,20 @@ msgid "PGroonga supports fast index search by `@>` operator."
 msgstr "PGroongaは`@>`演算子の検索をインデックスを使って高速に実現できます。"
 
 msgid ""
-"[`@>` is a built-in PostgreSQL operator](http://www.postgresql.org/docs/curren"
-"t/static/functions-json.html#FUNCTIONS-JSONB-OP-TABLE). `@>` returns true when"
-" the right hand side `jsonb` is a subset of left hand side `jsonb`."
+"[`@>` operator is a built-in PostgreSQL operator](http://www.postgresql.org/do"
+"cs/{{ site.postgresql_short_version }}/static/functions-json.html#FUNCTIONS-JS"
+"ONB-OP-TABLE). `@>` operator returns true when the right hand side `jsonb` typ"
+"e value is a subset of left hand side `jsonb` type value."
 msgstr ""
+"[`@>`演算子はPostgreSQL組み込みの演算子](http://www.postgresql.jp/document/{{ site.postgre"
+"sql_short_version }}/html/functions-json.html#FUNCTIONS-JSONB-OP-TABLE)です。`@>`"
+"演算子は右辺の`jsonb`型の値が左辺の`jsonb`型の値のサブセットなら真を返します。"
 
 msgid "## Syntax"
 msgstr "## 構文"
 
 msgid "Here is the syntax of this operator:"
-msgstr ""
+msgstr "この演算子の構文は次の通りです。"
 
 msgid ""
 "```sql\n"
@@ -47,15 +51,15 @@ msgid ""
 msgstr ""
 
 msgid "`jsonb_column` is a column that its type is `jsonb`."
-msgstr ""
+msgstr "`jsonb_column`は`jsonb`型のカラムです。"
 
-msgid "`jsonb_query` is a `jsonb` value used as query."
-msgstr ""
+msgid "`jsonb_query` is a `jsonb` type value used as query."
+msgstr "`jsonb_query`はクエリーとして使う`jsonb`型の値です。"
 
 msgid ""
-"The operator returns `true` when `jsonb_query` is a sub set of `jsonb_column` "
-"value, `false` otherwise."
-msgstr ""
+"The operator returns `true` when `jsonb_query` is a subset of `jsonb_column` v"
+"alue, `false` otherwise."
+msgstr "この演算子は`jsonb_query`が`jsonb_column`の値のサブセットなら`true`を返し、そうでない場合は`false`を返します。"
 
 msgid "## Usage"
 msgstr "## 使い方"
@@ -115,7 +119,7 @@ msgid ""
 msgstr ""
 
 msgid "Here is an example for match case:"
-msgstr ""
+msgstr "マッチする例は次の通りです。"
 
 msgid ""
 "(It uses [`jsonb_pretty()` function](http://www.postgresql.org/docs/devel/stat"
@@ -154,21 +158,26 @@ msgid ""
 msgstr ""
 
 msgid "Here is an example for not match case."
-msgstr ""
+msgstr "マッチしない例は次の通りです。"
 
 msgid ""
-"If you use an array in the condition `jsonb` value, all elements must be inclu"
-"ded in the search target `jsonb` value. Position of element isn't cared. If th"
-"ere are one or more elements that are included in the condition `jsonb` value "
-"but aren't included in the search target `jsonb` value, record that have the s"
-"earch target `jsonb` value isn't matched."
+"If you use an array in the search condition `jsonb` type value, all elements m"
+"ust be included in the search target `jsonb` type value. Position of element i"
+"sn't cared. If there are one or more elements that are included in the search "
+"condition `jsonb` type value but aren't included in the search target `jsonb` "
+"type value, record that have the search target `jsonb` type value isn't matche"
+"d."
 msgstr ""
+"検索条件の`jsonb`型の値で配列を使った場合、検索対象の`jsonb`型の値にすべての要素が含まれていなければいけません。要素の順番は問いません。もし、"
+"検索条件の`jsonb`型の値の要素のうち、1つでも検索対象の`jsonb`型の値に含まれていない要素があればそのレコードはマッチしません。"
 
 msgid ""
 "In the following example, there are records that have only `\"mail\"` or `\"web\"`"
 " but there are no records that have both `\"mail\"` and `\"web\"`. So the followin"
 "g `SELECT` returns no record:"
 msgstr ""
+"以下の例では、`\"mail\"`または`\"web\"`を含むレコードはありますが、`\"mail\"`と`\"web\"`両方を含むレコードはありません。そのため、次の"
+"`SELECT`は1つもレコードを返しません。"
 
 msgid ""
 "```sql\n"
@@ -187,3 +196,5 @@ msgid ""
 "  * [`jsonb` support](../jsonb.html)\n"
 "  * [`@@` operator](jsonb-query.html)"
 msgstr ""
+"  * [`jsonb`サポート](../jsonb.html)\n"
+"  * [`@@`演算子](jsonb-query.html)"

  Modified: ja/reference/operators/jsonb-contain.md (+11 -11)
===================================================================
--- ja/reference/operators/jsonb-contain.md    2015-10-24 17:59:18 +0900 (2d8ed2f)
+++ ja/reference/operators/jsonb-contain.md    2015-10-25 15:28:23 +0900 (d6cdcf7)
@@ -9,21 +9,21 @@ layout: ja
 
 PGroongaは`@>`演算子の検索をインデックスを使って高速に実現できます。
 
-[`@>` is a built-in PostgreSQL operator](http://www.postgresql.org/docs/current/static/functions-json.html#FUNCTIONS-JSONB-OP-TABLE). `@>` returns true when the right hand side `jsonb` is a subset of left hand side `jsonb`.
+[`@>`演算子はPostgreSQL組み込みの演算子](http://www.postgresql.jp/document/{{ site.postgresql_short_version }}/html/functions-json.html#FUNCTIONS-JSONB-OP-TABLE)です。`@>`演算子は右辺の`jsonb`型の値が左辺の`jsonb`型の値のサブセットなら真を返します。
 
 ## 構文
 
-Here is the syntax of this operator:
+この演算子の構文は次の通りです。
 
 ```sql
 jsonb_column @> jsonb_query
 ```
 
-`jsonb_column` is a column that its type is `jsonb`.
+`jsonb_column`は`jsonb`型のカラムです。
 
-`jsonb_query` is a `jsonb` value used as query.
+`jsonb_query`はクエリーとして使う`jsonb`型の値です。
 
-The operator returns `true` when `jsonb_query` is a sub set of `jsonb_column` value, `false` otherwise.
+この演算子は`jsonb_query`が`jsonb_column`の値のサブセットなら`true`を返し、そうでない場合は`false`を返します。
 
 ## 使い方
 
@@ -72,7 +72,7 @@ INSERT INTO logs
 SET enable_seqscan = off;
 ```
 
-Here is an example for match case:
+マッチする例は次の通りです。
 
 (読みやすくするためにPostgreSQL 9.5以降で使える[`jsonb_pretty()`関数](http://www.postgresql.jp/document/current/html/functions-json.html#FUNCTIONS-JSON-PROCESSING-TABLE)を使っています。)
 
@@ -100,11 +100,11 @@ SELECT jsonb_pretty(record) FROM logs WHERE record @> '{"host": "www.example.com
 -- (2 rows)
 ```
 
-Here is an example for not match case.
+マッチしない例は次の通りです。
 
-If you use an array in the condition `jsonb` value, all elements must be included in the search target `jsonb` value. Position of element isn't cared. If there are one or more elements that are included in the condition `jsonb` value but aren't included in the search target `jsonb` value, record that have the search target `jsonb` value isn't matched.
+検索条件の`jsonb`型の値で配列を使った場合、検索対象の`jsonb`型の値にすべての要素が含まれていなければいけません。要素の順番は問いません。もし、検索条件の`jsonb`型の値の要素のうち、1つでも検索対象の`jsonb`型の値に含まれていない要素があればそのレコードはマッチしません。
 
-In the following example, there are records that have only `"mail"` or `"web"` but there are no records that have both `"mail"` and `"web"`. So the following `SELECT` returns no record:
+以下の例では、`"mail"`または`"web"`を含むレコードはありますが、`"mail"`と`"web"`両方を含むレコードはありません。そのため、次の`SELECT`は1つもレコードを返しません。
 
 ```sql
 SELECT jsonb_pretty(record) FROM logs WHERE record @> '{"tags": ["mail", "web"]}'::jsonb;
@@ -115,5 +115,5 @@ SELECT jsonb_pretty(record) FROM logs WHERE record @> '{"tags": ["mail", "web"]}
 
 ## 参考
 
-  * [`jsonb` support](../jsonb.html)
-  * [`@@` operator](jsonb-query.html)
+  * [`jsonb`サポート](../jsonb.html)
+  * [`@@`演算子](jsonb-query.html)

  Modified: reference/operators/jsonb-contain.md (+4 -4)
===================================================================
--- reference/operators/jsonb-contain.md    2015-10-24 17:59:18 +0900 (3664faa)
+++ reference/operators/jsonb-contain.md    2015-10-25 15:28:23 +0900 (34255a6)
@@ -9,7 +9,7 @@ layout: en
 
 PGroonga supports fast index search by `@>` operator.
 
-[`@>` is a built-in PostgreSQL operator](http://www.postgresql.org/docs/current/static/functions-json.html#FUNCTIONS-JSONB-OP-TABLE). `@>` returns true when the right hand side `jsonb` is a subset of left hand side `jsonb`.
+[`@>` operator is a built-in PostgreSQL operator](http://www.postgresql.org/docs/{{ site.postgresql_short_version }}/static/functions-json.html#FUNCTIONS-JSONB-OP-TABLE). `@>` operator returns true when the right hand side `jsonb` type value is a subset of left hand side `jsonb` type value.
 
 ## Syntax
 
@@ -21,9 +21,9 @@ jsonb_column @> jsonb_query
 
 `jsonb_column` is a column that its type is `jsonb`.
 
-`jsonb_query` is a `jsonb` value used as query.
+`jsonb_query` is a `jsonb` type value used as query.
 
-The operator returns `true` when `jsonb_query` is a sub set of `jsonb_column` value, `false` otherwise.
+The operator returns `true` when `jsonb_query` is a subset of `jsonb_column` value, `false` otherwise.
 
 ## Usage
 
@@ -102,7 +102,7 @@ SELECT jsonb_pretty(record) FROM logs WHERE record @> '{"host": "www.example.com
 
 Here is an example for not match case.
 
-If you use an array in the condition `jsonb` value, all elements must be included in the search target `jsonb` value. Position of element isn't cared. If there are one or more elements that are included in the condition `jsonb` value but aren't included in the search target `jsonb` value, record that have the search target `jsonb` value isn't matched.
+If you use an array in the search condition `jsonb` type value, all elements must be included in the search target `jsonb` type value. Position of element isn't cared. If there are one or more elements that are included in the search condition `jsonb` type value but aren't included in the search target `jsonb` type value, record that have the search target `jsonb` type value isn't matched.
 
 In the following example, there are records that have only `"mail"` or `"web"` but there are no records that have both `"mail"` and `"web"`. So the following `SELECT` returns no record:
 
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Back to archive index