Arex.Edge (arex v0.1.0)

Graph edge helpers with tenant and scope awareness.

Edges are created and queried with the same tenant and scope boundary rules as records and vertices.

Use this module when your relationship data is naturally represented as ArcadeDB edges and you want Arex to validate vertex visibility, stamp active boundaries, and normalize RID-oriented operations.

Arex.Edge complements Arex.Vertex rather than replacing it. Use the two together when you want explicit graph workflows with the same boundary model that Arex applies to document helpers.

Summary

Functions

between(from_rid, to_rid, edge_type \\ nil, opts \\ [])

Finds edges from one vertex RID to another, optionally restricted by edge type.

create(edge_type, from_rid, to_rid, attrs \\ %{}, opts \\ [])

Creates an edge between two existing vertices.

delete(rid, opts \\ [])

Deletes an edge by RID after confirming it is visible within the active boundary.

fetch(rid, opts \\ [])

Fetches an edge by RID using the same boundary rules as record fetches.

in_rid(edge_record)

Extracts the incoming RID from an edge record.

out_rid(edge_record)

Extracts the outgoing RID from an edge record.

Functions

between(from_rid, to_rid, edge_type \\ nil, opts \\ [])

Finds edges from one vertex RID to another, optionally restricted by edge type.

Returned rows are filtered to the active tenant and scope boundary.

create(edge_type, from_rid, to_rid, attrs \\ %{}, opts \\ [])

Creates an edge between two existing vertices.

Both endpoint RIDs must be valid and visible within the active boundary before the edge is created.

delete(rid, opts \\ [])

Deletes an edge by RID after confirming it is visible within the active boundary.

fetch(rid, opts \\ [])

Fetches an edge by RID using the same boundary rules as record fetches.

in_rid(edge_record)

Extracts the incoming RID from an edge record.

out_rid(edge_record)

Extracts the outgoing RID from an edge record.