API 4.0: api_func_nd_p_port_is_contained_by_conn_id_gfk_list: operator does not exist: bigint = bigint[]

{
	"exception": {
		"error": {
			"code": 1,
			"description": "[cntl] Ungültige Eingabesyntax für entsprechenden Datentyp",
			"details": null
		},
		"error_type": {
			"code": -20900,
			"name": "format_error",
			"description": "Datentyp-Formatierungsfehler"
		},
		"constraint": {
			"name": null,
			"description": null
		},
		"stacked_diag_params": {
			"sqlstate": "42883",
			"message": "operator does not exist: bigint = bigint[]",
			"detail": "",
			"hint": "No operator matches the given name and argument types. You might need to add explicit type casts.",
			"context": "PL/pgSQL function eh.set_err(eh.stacked_diag_params_rec_type,name,name,eh.userparams_kv_rec_type[],eh.typecode_rec_type) line 22 at RAISE\\nSQL statement \"SELECT eh.set_err(sd_rec, fpkg, fname, up_kv_rec_list, et_rec)\"\\nPL/pgSQL function nd_wapi_4_0.ta_stmt_handler(jsonb,wapi_4_0.exec_ta_stmt_rec_type) line 528 at PERFORM\\nSQL statement \"select\\n                    eh_ret_stmt_pos, eh_ret_stmt_idx,\\n                    (attrs.dict #> array[int_dwh_tab_arg_name, dwh_gpk_col_name])::bigint,\\n                    attrs.dict - attrs.fattrs,\\n                    nextval('obj_dict_pos_seq')\\n                  from nd_wapi_4_0.ta_stmt_handler(in_ta_osr_jsonb => stmt_osr_jsonb, in_stmt_rec => rp_tah_stmt_rec) as attrs(dict, fattrs)\"\\nPL/pgSQL function wapi_4_0.exec_ta_handler(bigint,jsonb,boolean,boolean,boolean,boolean,text,text) line 1103 at RETURN QUERY\\nSQL statement \"select tah.out_stmt_pos, tah.out_stmt_idx, tah.out_obj_dict from wapi_4_0.exec_ta_handler(\\n    in_ta_id => ta_id,\\n    in_ta_osr_jsonb => ta_osr_jsonb,\\n    in_keep_tmp_ta => in_keep_tmp_ta,\\n    in_report_stmt_pos => in_report_stmt_pos,\\n    in_is_dry_mode => in_is_dry_mode,\\n    in_ignore_maint_state => in_ignore_maint_state,\\n    in_su_login_name => in_su_login_name,\\n    in_language_tag => in_language_tag\\n  ) AS tah\"\\nPL/pgSQL function wapi_4_0.ta_handler(text,text,text,boolean,boolean,boolean,boolean,text,text) line 33 at RETURN QUERY",
			"dml_src_table": null,
			"schema": "",
			"table": "",
			"column": "",
			"datatype": "",
			"constraint": ""
		},
		"others": {},
		"traceback": [
			{
				"function": "wapi_4_0.exec_ta_handler",
				"param": {
					"wapi.transaction_stmt.pos": [
						{
							"state": null,
							"value": 6
						}
					],
					"wapi.transaction_stmt.idx": [
						{
							"state": null,
							"value": "resolved"
						}
					]
				}
			}
		],
		"hint": null
	}
}

Request:

[
	{
		"idx": "bcd_list",
		"name": "nd.bcd.list",
		"old": {
			"name": "scc-nw-bg-pinkie-1"
		}
	},
	{
		"idx": "vlan_list",
		"inner_join_ref": {
			"bcd_list": "default"
		},
		"name": "nd.vlan.list"
	},
	{
		"idx": "l_port_list",
		"inner_join_ref": {
			"vlan_list": "default"
		},
		"name": "nd.l_port.list",
		"old": {
			"dev_fqdn": "scs2020g0101.tmn.scc.kit.edu."
		}
	},
	{
		"idx": "l2p_port_list",
		"inner_join_ref": {
			"l_port_list": "default"
		},
		"name": "nd.l2p_port.list"
	},
	{
		"idx": "p_port_list",
		"inner_join_ref": {
			"l2p_port_list": "default"
		},
		"name": "nd.p_port.list",
		"old": {
			"name": "1:8"
		}
	},
	{
		"idx": "tmp",
		"inner_join_ref": {
			"p_port_list": "self"
		},
		"name": "nd.p_port.list"
	},
	{
		"anti_join_ref": {
			"tmp": "self"
		},
		"idx": "resolved",
		"inner_join_ref": {
			"p_port_list": "api_func_nd_p_port_is_contained_by_conn_id_gfk_list"
		},
		"name": "nd.p_port.list",
		"old": {
			"is_edge_node": true
		}
	}
]

added API label

assigned to @rainer.steinmueller

changed the description

4.0 unterstuetzt das dynsql fuer diesen constraint nicht. das geht erst mit 4.1. muss erstmal sehen, inwieweit es abwaerts anpassbar ist.

changed milestone to %API 4.1 Release

changed title from api_func_nd_p_port_is_contained_by_conn_id_gfk_list: operator does not exist: bigint = bigint[] to API 4.0: api_func_nd_p_port_is_contained_by_conn_id_gfk_list: operator does not exist: bigint = bigint[]

filtern im datadict (ueber die pro version definierten constraint-attribute) wird extrem aufwendig, weil (im beispiel) das attribut gpk (f. api_func_nd_p_port_is_contained_by_conn_id_gfk_list) in 4.0 definiert ist, aber das referenzierte attribut connection_id_gfk_list (f. api_unq_nd_p_port_conn_id_gpk_list) nicht.

das einzige, was geht, ist eine check-fkt., die ggf. eine exception wirft, dass der constraint in der aktuellen version nicht gueltig ist.

ist gemacht.

closed