Zen

Translation

Rows can optionally be filtered using the same view filters that are available for the views. Multiple filters may be applied if they follow the same format. The `field` and `filter` variables indicate how and where to apply the filter, respectively.

#### With `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__Name__equal=test`, only rows where the value of `Name` equals 'test' will be returned. This method is backwards compatible and will check against `field_id` if it fails on the name.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__field_1__equal=test`, only rows where the value of `field_1` equals 'test' will be returned.

Please note that if the filters parameter is provided, this parameter will be ignored.
apiDocsTableListRows.filter
English
Rows can optionally be filtered using the same view filters that are available for the views. Multiple filters may be applied if they follow the same format. The `field` and `filter` variables indicate how and where to apply the filter, respectively.

#### With `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__Name__equal=test`, only rows where the value of `Name` equals 'test' will be returned. This method is backwards compatible and will check against `field_id` if it fails on the name.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__field_1__equal=test`, only rows where the value of `field_1` equals 'test' will be returned.

Please note that if the filters parameter is provided, this parameter will be ignored.
177/8350 · 835

Sign in to save the translation.

Key English Japanese Actions
apiDocsTableListRows.size
Defines how many rows should be returned per page.
返却される１ページ毎の行数を指定。
apiDocsTableListRows.userFieldNames
When any value is provided for the `user_field_names` GET param then field names returned by this endpoint will be the actual names of the fields.

If the `user_field_names` GET param is not provided, then all returned field names will be `field_` followed by the id of the field. For example `field_1` refers to the field with an id of `1`.

Additionally when `user_field_names` is set then the behaviour of the other GET parameters `order_by`, `include` and `exclude` changes. They instead expect comma separated lists of the actual field names instead.
`user_field_names` GET パラメタにどのような値でもセットすると、エンドポイントから返却されるフィールド名は実際のフィールド名になります。

`user_field_names` GET パラメタが指定されないと、返却されるフィールド名は`field_`で始まり、フィールドのid を付した名前になります。例えば、`field_1` は id が `1`のフィールドになります。

`user_field_names` GET パラメタが指定されると、`order_by` 、`include`、`exclude` GETパラメタの振る舞いも変わり、実際のフィールド名で指定する必要があります。
apiDocsTableListRows.search
If provided only rows with data that matches the search query are going to be returned.
指定されると条件に合致した行のみが返却されます。
apiDocsTableListRows.orderBy
Optionally the rows can be ordered by fields separated by comma. By default or if prepended with a '+' a field is ordered in ascending (A-Z) order, but by prepending the field with a '-' it can be ordered descending (Z-A).

#### With `user_field_names`:

`order_by` should be a comma separated list of the field names to order by. For example if you provide the following GET parameter `order_by=My Field,-My Field 2` the rows will ordered by the field called `My Field` in ascending order. If some fields have the same value, that subset will be ordered by the field called `My Field 2` in descending order.

Ensure fields with names starting with a `+` or `-` are explicitly prepended with another `+` or `-`. E.g `+-Name`.

The name of fields containing commas must be surrounded by quotes: `"Name ,"`. If the field names contain quotes, then they must be escaped using the `\` character. Eg: `Name \"`.

#### Without `user_field_names`:

`order_by` should be a comma separated list of `field_` followed by the id of the field to order by. For example if you provide the following GET parameter `order_by=field_1,-field_2` the rows will ordered by `field_1` in ascending order. If some fields have the same value, that subset will be ordered by `field_2` in descending order.
オプションとして、返却される行の並び替えはカンマ区切りで指定出来ます。'+' を頭に付けると昇順（A-Zの順、既定値）、'-' を頭に付けると降順で並びます。

#### `user_field_names`を指定した場合

`order_by`パラメタはカンマ区切りのフィールド名のリストで指定します。例えば次のようなGETパラメタは、`My Field` の昇順でならび、同じ値の場合は `My Field 2`の降順でならんで返却されます。

`+`や`-`で始まるフィールド名の場合は、必ず昇順・降順を明示するために、頭に`+` / `-` を指定して下さい。例）`+-Name`。

フィールド名がコンマを含む場合は、ダブルクォーテーションで囲む必要があります： 例）`"Name,"`　また、ダブルクォーテーションを含む場合は、`\`記号でエスケープする必要があります。例）`\"Name\"`。

#### `user_field_names`を指定しない場合

`order_by`はコンマ区切りの、`field_`と数字で表される識別子のリストを使います。例えば、次のようなGETパラメタを考えます：`order_by=field_1,-field_2`。この場合、field_1 の昇順で並び、かつ、field_1 が同じ値の行は、field_2 の降順で並びます。
apiDocsTableListRows.filters
Rows can optionally be filtered using the same view filters that are available for the views. This parameter accepts a JSON serialized string containing the filter tree to apply to this view. The filter tree is a nested structure containing the filters that need to be applied.

#### With `user_field_names`:

An example of a valid filter tree is the following: `{"filter_type": "AND", "filters": [{"field": "Name", "type": "equal", "value": "test"}]}`.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `{"filter_type": "AND", "filters": [{"field": 1, "type": "equal", "value": "test"}]}`

Please note that if this parameter is provided, all other `filter__{field}__{filter}` will be ignored, as well as the filter_type parameter.
 
apiDocsTableListRows.filter
Rows can optionally be filtered using the same view filters that are available for the views. Multiple filters may be applied if they follow the same format. The `field` and `filter` variables indicate how and where to apply the filter, respectively.

#### With `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__Name__equal=test`, only rows where the value of `Name` equals 'test' will be returned. This method is backwards compatible and will check against `field_id` if it fails on the name.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__field_1__equal=test`, only rows where the value of `field_1` equals 'test' will be returned.

Please note that if the filters parameter is provided, this parameter will be ignored.
行はビュー・フィルターと同じフィルターで絞り込むことが出来ます。複数のフィルターも書式が同じであれば指定出来ます。フィールドと絞り込み方法を指定し、値で絞り込む行を指定します。

例えば、次のようなGETパラメタを指定します：`filter__field_1__equal=test`。すると、field_1 が「test」と等しい行のみが返却されます。
apiDocsTableListRows.filterLink
A list of all filters can be found here.
全てのフィルターの一覧です。
apiDocsTableListRows.filterType
- `AND`: Indicates that the rows must match all the provided filters.
- `OR`: Indicates that the rows only have to match one of the filters.

This works only if two or more filters are provided.
- `AND`：全ての条件に合致するものを検索します。
- `OR`：いずれかの条件に合致するものを検索します。

２つ以上のフィルターが指定された場合のみ有効です。
apiDocsTableListRows.include
All the fields are included in the response by default. You can select a subset of fields to include by providing the include query parameter.

#### With `user_field_names`:

`include` should be a comma separated list of field names to be included in results. For example if you provide the following GET param: `include=My Field,-My Field 2` then only those fields will be included (unless they are explicitly excluded).

The name of fields containing commas must be surrounded by quotes: `"Name ,"`. If the field names contain quotes, then they must be escaped using the `\` character. Eg: `Name \"`.

#### Without `user_field_names`:

`include` should be a comma separated list of `field_` followed by the id of the field to include in the results. For example: If you provide the following GET parameter `include=field_1,field_2` then the fields with id `1` and id `2` then only those fields will be included (unless they are explicitly excluded).
デフォルトでは全てのフィールドがレスポンスに返却されます。「include」クエリ・パラメタを利用して返却するフィールドを指定することが出来ます。

#### `user_field_names`を指定した場合

`include`は返却したいフィールドを、コンマ区切りの一覧で指定します。例えば次のようなGETパラメタは：`include=My Field,-MyField2`この２つのフィールドのみ返却されます（`exclude`で指定されていない限り）。

フィールド名がコンマを含む場合は、ダブルクォーテーションで囲む必要があります： 例）`"Name,"`　また、ダブルクォーテーションを含む場合は、`\`記号でエスケープする必要があります。例）`\"Name\"`。

#### `user_field_names`を指定しない場合

`include`はコンマ区切りの、`field_`と数字で表される識別子のリストを使います。例えば、次のようなGETパラメタを考えます：`include=field_1,-field_2`。この場合、id が`1`と`2`のフィールドのみが返却されます（`exclude`で指定されていない限り）。
apiDocsTableListRows.exclude
All the fields are included in the response by default. You can select a subset of fields to exclude by providing the exclude query parameter.

#### With `user_field_names`:

`exclude` should be a comma separated list of field names to be excluded from the results. For example if you provide the following GET param: `exclude=My Field,-My Field 2` then those fields will be excluded.

The name of fields containing commas must be surrounded by quotes: `"Name ,"`. If the field names contain quotes, then they must be escaped using the `\` character. Eg: `Name \"`.

#### Without `user_field_names`:

`exclude` should be a comma separated list of `field_` followed by the id of the field to exclude from the results. For example: If you provide the following GET parameter `exclude=field_1,field_2` then the fields with id `1` and id `2` will be excluded.
デフォルトでは全てのフィールドがレスポンスに返却されます。「exclude」クエリ・パラメタを利用して返却しないフィールドを指定することが出来ます。

#### `user_field_names`を指定した場合

`exclude`は返却しないフィールドを、コンマ区切りの一覧で指定します。例えば次のようなGETパラメタは：`exclude=My Field,-MyField2`この２つのフィールドは返却されません。

フィールド名がコンマを含む場合は、ダブルクォーテーションで囲む必要があります： 例）`"Name,"`　また、ダブルクォーテーションを含む場合は、`\`記号でエスケープする必要があります。例）`\"Name\"`。

#### `user_field_names`を指定しない場合

`exclude`はコンマ区切りの、`field_`と数字で表される識別子のリストを使います。例えば、次のようなGETパラメタを考えます：`exclude=field_1,-field_2`。この場合、id が`1`と`2`のフィールドは返却されません。
apiDocsTableListRows.viewId
By default non of the filters and sorts outside of the ones defined in the query parameters are applied. You can add the filters and sorts of a view by providing its `id` in the `view_id` GET parameter. For example if you provide the following GET parameter `view_id=1` then the filters and sorts defined in the view with id `1` will be applied. You can find the `view_id` in the context menu of any given view. It is the number in brackets behind the view name.

#### With `filter__{field}__{filter}`

Both the filter provided in the query parameter and the filters defined in the view will be applied.

#### With `order_by`

If `order_by` is provided then the sort defined in the view will be ignored.
デフォルトではクエリ・パラメタに指定されたフィルターと並び替え以外は適用されません。ビューのフィルターや並び替えを id で指定して加えることが出来ます。例えば、GETパラメタに `view_id=1` を加えると、id 「１」のビューに設定されているフィルターと並び替えが適用されます。`view_id` はビューのコンテキスト・メニューに表示されます。ビュー名の横に括弧付きいで表示されている数値が id になります。

#### `filter__{field}___{filter}` を指定する場合

クエリ・パラメタのフィルターとビューに定義されているフィルターの両方が適用されます。

#### `order_by` を指定する場合

クエリ・パラメタに並び替えを指定されると、ビューに定義されている序列は無視されます。
Key English Japanese Actions
apiDocsTableListFields.resultFieldProperties
Result field properties
結果フィールドの属性
apiDocsTableListFields.tableId
Related table id.
関連テーブルID。
apiDocsTableListFields.type
Type defined for this field.
フィールドの型。
apiDocsTableListRows.description
To list rows in the *{name}* table a `GET` request has to be made to the *{name}* endpoint. The response is paginated and by default the first page is returned. The correct page can be fetched by providing the `page` and `size` query parameters.
行の一覧を *{name}* テーブルより取得するには、`GET`リクエストを *{name}* エンドポイントへ投げます。 The response is paginated and by default the first page is returned. The correct page can be fetched by providing the `page` and `size` query parameters.
apiDocsTableListRows.exclude
All the fields are included in the response by default. You can select a subset of fields to exclude by providing the exclude query parameter.

#### With `user_field_names`:

`exclude` should be a comma separated list of field names to be excluded from the results. For example if you provide the following GET param: `exclude=My Field,-My Field 2` then those fields will be excluded.

The name of fields containing commas must be surrounded by quotes: `"Name ,"`. If the field names contain quotes, then they must be escaped using the `\` character. Eg: `Name \"`.

#### Without `user_field_names`:

`exclude` should be a comma separated list of `field_` followed by the id of the field to exclude from the results. For example: If you provide the following GET parameter `exclude=field_1,field_2` then the fields with id `1` and id `2` will be excluded.
デフォルトでは全てのフィールドがレスポンスに返却されます。「exclude」クエリ・パラメタを利用して返却しないフィールドを指定することが出来ます。

#### `user_field_names`を指定した場合

`exclude`は返却しないフィールドを、コンマ区切りの一覧で指定します。例えば次のようなGETパラメタは：`exclude=My Field,-MyField2`この２つのフィールドは返却されません。

フィールド名がコンマを含む場合は、ダブルクォーテーションで囲む必要があります： 例）`"Name,"`　また、ダブルクォーテーションを含む場合は、`\`記号でエスケープする必要があります。例）`\"Name\"`。

#### `user_field_names`を指定しない場合

`exclude`はコンマ区切りの、`field_`と数字で表される識別子のリストを使います。例えば、次のようなGETパラメタを考えます：`exclude=field_1,-field_2`。この場合、id が`1`と`2`のフィールドは返却されません。
apiDocsTableListRows.filter
Rows can optionally be filtered using the same view filters that are available for the views. Multiple filters may be applied if they follow the same format. The `field` and `filter` variables indicate how and where to apply the filter, respectively.

#### With `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__Name__equal=test`, only rows where the value of `Name` equals 'test' will be returned. This method is backwards compatible and will check against `field_id` if it fails on the name.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__field_1__equal=test`, only rows where the value of `field_1` equals 'test' will be returned.

Please note that if the filters parameter is provided, this parameter will be ignored.
行はビュー・フィルターと同じフィルターで絞り込むことが出来ます。複数のフィルターも書式が同じであれば指定出来ます。フィールドと絞り込み方法を指定し、値で絞り込む行を指定します。

例えば、次のようなGETパラメタを指定します：`filter__field_1__equal=test`。すると、field_1 が「test」と等しい行のみが返却されます。
apiDocsTableListRows.filterLink
A list of all filters can be found here.
全てのフィルターの一覧です。
apiDocsTableListRows.filters
Rows can optionally be filtered using the same view filters that are available for the views. This parameter accepts a JSON serialized string containing the filter tree to apply to this view. The filter tree is a nested structure containing the filters that need to be applied.

#### With `user_field_names`:

An example of a valid filter tree is the following: `{"filter_type": "AND", "filters": [{"field": "Name", "type": "equal", "value": "test"}]}`.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `{"filter_type": "AND", "filters": [{"field": 1, "type": "equal", "value": "test"}]}`

Please note that if this parameter is provided, all other `filter__{field}__{filter}` will be ignored, as well as the filter_type parameter.
 
apiDocsTableListRows.filtersBuilder
Open filters parameter builder
 
apiDocsTableListRows.filterType
- `AND`: Indicates that the rows must match all the provided filters.
- `OR`: Indicates that the rows only have to match one of the filters.

This works only if two or more filters are provided.
- `AND`：全ての条件に合致するものを検索します。
- `OR`：いずれかの条件に合致するものを検索します。

２つ以上のフィルターが指定された場合のみ有効です。

Loading…

User avatar None

String updated in the repository

  1. Baserow
  2. web-frontend-database
  3. Japanese
Rows can optionally be filtered using the same view filters that are available for the views. Multiple filters may be applied if they follow the same format. The `field` and `filter` variables indicate how and where to apply the filter, respectively.

#### With `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__Name__equal=test`, only rows where the value of `Name` equals 'test' will be returned. This method is backwards compatible and will check against `field_id` if it fails on the name.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__field_1__equal=test`, only rows where the value of `field_1` equals 'test' will be returned.

Please note that if the filters parameter is provided, this parameter will be ignored.
行はビュー・フィルターと同じフィルターで絞り込むことが出来ます。複数のフィルターも書式が同じであれば指定出来ます。フィールドと絞り込み方法を指定し、値で絞り込む行を指定します。

例えば、次のようなGETパラメタを指定します：`filter__field_1__equal=test`。すると、field_1 が「test」と等しい行のみが返却されます。
8 months ago
User avatar None

Source string changed

  1. Baserow
  2. web-frontend-database
  3. Japanese
Rows can optionally be filtered using the same view filters that are available for the views. Multiple filters may be applied if they follow the same format. The `field` and `filter` variables indicate how and where to apply the filter, respectively.

#### With `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__Name__equal=test`, only rows where the value of `Name` equals 'test' will be returned. This method is backwards compatible and will check against `field_id` if it fails on the name.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__field_1__equal=test`, only rows where the value of `field_1` equals 'test' will be returned.

Please note that if the filters parameter is provided, this parameter will be ignored.
8 months ago
User avatar None

String updated in the repository

  1. Baserow
  2. web-frontend-database
  3. Japanese
Rows can optionally be filtered using the same view filters that are available for the views. Multiple filters may be applied if they follow the same format. The `field` and `filter` variables indicate how and where to apply the filter, respectively.

#### With `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__Name__equal=test`, only rows where the value of `Name` equals 'test' will be returned. This method is backwards compatible and will check against `field_id` if it fails on the name.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__field_1__equal=test`, only rows where the value of `field_1` equals 'test' will be returned.
行はビュー・フィルターと同じフィルターで絞り込むことが出来ます。複数のフィルターも書式が同じであれば指定出来ます。フィールドと絞り込み方法を指定し、値で絞り込む行を指定します。

例えば、次のようなGETパラメタを指定します：`filter__field_1__equal=test`。すると、field_1 が「test」と等しい行のみが返却されます。
9 months ago
User avatar None

Source string changed

  1. Baserow
  2. web-frontend-database
  3. Japanese
The rRows can optionally be filtered byusing the same view filters that are available for the views. Multiple filters canmay be providapplied if they follow the same format. The `field` and `filter` variables indicate how to filter and the value indicates where toand where to apply the filter, respectively.

#### With `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__Name__equal=test`, only rows where the value of `Name` equals 'test' will be returned. This method is backwards compatible and will check against `field_id` if it failter on.

s on the name.

#### Without `user_field_names`:

For example, if you optionally provide the following GET parameter: `filter__field_1__equal=test` then, only rows where the value of `field_1 is` equal to test are going tos 'test' will be returned.
9 months ago
User avatar masahirominami

Translation replaced

  1. Baserow
  2. web-frontend-database
  3. Japanese
The rows can optionally be filtered by the same view filters available for the views. Multiple filters can be provided if they follow the same format. The `field` and `filter` variable indicate how to filter and the value indicates where to filter on.

For example if you provide the following GET parameter `filter__field_1__equal=test` then only rows where the value of field_1 is equal to test are going to be returned.
行はビュー・フィルターと同じフィルターで絞り込むことが出来ます。複数のフィルターも書式が同じであれば指定出来ます。フィールドと絞り込み方法を指定し、値で絞り込む行を指定します。

例えば、次のようなGETパラメタを指定します：`filter__field_1__equal=test`。すると、field_1 が「test」と等しい行のみが返却されます。
a year ago
User avatar masahirominami

Translation replaced

  1. Baserow
  2. web-frontend-database
  3. Japanese
The rows can optionally be filtered by the same view filters available for the views. Multiple filters can be provided if they follow the same format. The `field` and `filter` variable indicate how to filter and the value indicates where to filter on.

For example if you provide the following GET parameter `filter__field_1__equal=test` then only rows where the value of field_1 is equal to test are going to be returned.
行はビュー・フィルターと同じフィルターで絞り込むことが出来ます。複数のフィルターも書式が同じであれば指定出来ます。フィールドと絞り込み方法を指定し、値で絞り込む行を指定します。

例えば、次のようなGETパラメタを指定します：`filter__field_1__equal=test`。すると、field_1 が「test」と等しい行のみが返却されます。
a year ago
User avatar masahirominami

Translation changed

  1. Baserow
  2. web-frontend-database
  3. Japanese
The rows can optionally be filtered by the same view filters available for the views. Multiple filters can be provided if they follow the same format. The `field` and `filter` variable indicate how to filter and the value indicates where to filter on.

For example if you provide the following GET parameter `filter__field_1__equal=test` then only rows where the value of field_1 is equal to test are going to be returned.
行はビュー・フィルターと同じフィルターで絞り込むことが出来ます。複数のフィルターも書式が同じであれば指定出来ます。フィールドと絞り込み方法を指定し、値で絞り込む行を指定します。

例えば、次のようなGETパラメタを指定します：`filter__field_1__equal=test`。すると、field_1 が「test」と等しい行のみが返却されます。
a year ago
User avatar masahirominami

Translation added

  1. Baserow
  2. web-frontend-database
  3. Japanese
The rows can optionally be filtered by the same view filters available for the views. Multiple filters can be provided if they follow the same format. The `field` and `filter` variable indicate how to filter and the value indicates where to filter on.

For example if you provide the following GET parameter `filter__field_1__equal=test` then only rows where the value of field_1 is equal to test are going to be returned.
行はビュー・フィルタと同じフィルタで絞り込むことが出来ます。複数のフィルタも書式が同じであれば指定出来ます。フィールドと絞り込み方法を指定し、値で絞り込む行を指定します。

例えば、次のようなGETパラメタを指定します：`filter__field_1__equal=test`。すると、field_1 が「test」と等しい行のみが返却されます。
a year ago
User avatar None

String updated in the repository

  1. Baserow
  2. web-frontend-database
  3. Japanese
The rows can optionally be filtered by the same view filters available for the views. Multiple filters can be provided if they follow the same format. The `field` and `filter` variable indicate how to filter and the value indicates where to filter on.

For example if you provide the following GET parameter `filter__field_1__equal=test` then only rows where the value of field_1 is equal to test are going to be returned.
 
a year ago
Browse all string changes

Things to check

Trailing space

Source and translation do not both end with a space

Fix string

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Mismatching line breaks

Number of new lines in translation does not match source

Reset

Glossary

English Japanese
No related strings found in the glossary.

String information

Key
apiDocsTableListRows.filter
String age
a year ago
Last updated
8 months ago
Source string age
2 years ago
Translation file
web-frontend/modules/database/locales/ja.json, string 96