You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For all currently maintained branches and postgres / age versions, the behavior of the request
SELECT *
FROM cypher('test_graph', $$
MATCH (v)
WITH label(v) as vlabel
RETURN vlabel
$$) AS t(a agtype);
is to return an label only, if label has rows.
If the label is created using SELECT create_vlabel('<graph_name>', '<vertice_name>')
vertex will be present, subsequent calls will produce message
however, until an row is created for this vertex check for existence using query above will produce no rows, as if vertex did not exist. How is it affecting my program.
I need to be able to issue call to create and subsequently, whether rows present or not, create an index or set of indexes on the vertex, if vertex already exists.
Request:
Please chose best variant and create either
1 two function label_exists and label_type, with input parameter label_name
2 two fuctions vertex_exists and edge_exists
Personally I would prefer variant 2.
It is entirely possible I am missing existing feature that produces similar result. In case team Age could point out, I would be grateful. Otherwise, please help in creating the above approach.
To my mind it should be fairly trivial, as function label_exists already present, it just need to be exposed to SQL interface.
The text was updated successfully, but these errors were encountered:
MironAtHome
changed the title
One more request for exist type function, this time for vertice(s) and edge(s), previous was for graph.
One more request for exist type function, this time for vertex and edge, previous was for graph.
Jul 18, 2024
For all currently maintained branches and postgres / age versions, the behavior of the request
is to return an label only, if label has rows.
If the label is created using
SELECT create_vlabel('<graph_name>', '<vertice_name>')
vertex will be present, subsequent calls will produce message
however, until an row is created for this vertex check for existence using query above will produce no rows, as if vertex did not exist. How is it affecting my program.
I need to be able to issue call to create and subsequently, whether rows present or not, create an index or set of indexes on the vertex, if vertex already exists.
Request:
Please chose best variant and create either
1 two function label_exists and label_type, with input parameter label_name
2 two fuctions vertex_exists and edge_exists
Personally I would prefer variant 2.
It is entirely possible I am missing existing feature that produces similar result. In case team Age could point out, I would be grateful. Otherwise, please help in creating the above approach.
To my mind it should be fairly trivial, as function
label_exists
already present, it just need to be exposed to SQL interface.The text was updated successfully, but these errors were encountered: