Skip to content
Snippets Groups Projects
Commit 4b0362a4 authored by GitLab Runner 1149's avatar GitLab Runner 1149
Browse files

Automated Save by CI Run

parent f0fc993c
No related branches found
No related tags found
No related merge requests found
......@@ -1447,7 +1447,7 @@ components:
description: IP-Adresse
type: string
value_with_prefixlen:
description: ''
description: IP-Adresswert in CIDR-Notation
type: string
type: object
dns.record:
......@@ -4084,7 +4084,7 @@ info:
\ nicht Bestandteil dieser Dokumentation, sondern \xFCber selbstdokumentierende\
\ Indexabfragen der WebAPI erreichbar."
title: SCC NETDB-API
version: 4.2.11
version: 4.2.0
openapi: 3.0.3
paths:
/cntl/column/create:
......@@ -147,7 +147,7 @@
"default": null,
"pattern": "^\\[\\-?[0-9]*:\\-?[0-9]*\\]$",
"minItems": 1,
"description": "Positional range of the result sets being returned by the referenced statement as array (list of single positions, 0-based) or range literal as string (like '[<lower_bound>:<upper_bound>]' according to the array slice notation) or null (use all result sets). Negative values specify the position calculated backwards beginning at the end of the result set.",
"description": "Positional range of the evaluated result sets being returned by the referenced statement as array (a list of zero based single positions) or range literal as string (like '[<lower_bound>:<upper_bound>]' according to the array slice notation) or null (evaluate all result sets). Negative values specify the position calculated backwards beginning at the end of the result set.",
"uniqueItems": true
},
"params": {
......@@ -165,7 +165,7 @@
],
"title": "JOIN condition for result sets",
"default": "pos",
"description": "Which attributes are being used in the join condition for comparison between the current result set and the result set of the referenced statement. With 'pos' (position based join), the result sets are joined on equal position. With 'val' (value based join) they are joined on equal values of the attribute tuple, defined by the UP constraint type of the respective object types. The attribute tuple for the generic object type must be arbitrarily defined by 'ref_params_join_on_val_attrs_tuple'. If neither a UP constraint exists (for regular OT) nor 'ref_params_join_on_val_attrs_tuple' is specified or is null or empty or contains nonexisting attributes, the value based join will return no data and hence cannot be used. The position based join is always guaranteed to be usable. If the value based join is specified, 'join_offset_by_idx_list' and 'join_offset_by_constant' may not be specified."
"description": "Which attributes are being used in the join condition for comparison between the current result set and the result set of the referenced statement. With 'pos' (position based join), the result sets are joined on equal position. With 'val' (value based join) they are joined on equal values of the attribute tuple, defined by the UP constraint type of the respective object types (OT). The attribute tuple for the generic OT or for regular OT having no UP constraint must be arbitrarily defined by 'ref_params_join_on_val_attrs_tuple'. The attribute tuple for all remaining OT can be defined by 'ref_params_join_on_val_attrs_tuple' if desired. If neither a UP constraint exists (for regular OT) nor 'ref_params_join_on_val_attrs_tuple' is specified or is null or empty or contains nonexisting attributes, the value based join will return no data and hence cannot be used. The position based join is always guaranteed to be usable. If the value based join is specified, 'join_offset_by_idx_list' and 'join_offset_by_constant' may not be specified."
},
"join_type": {
"enum": [
......
4.2.11
\ No newline at end of file
4.2.0
\ No newline at end of file
4.2.11
\ No newline at end of file
4.2.0
\ No newline at end of file
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment