nexyron.graph.list
Generic Description
List named graph projections.
Simple example:
CALL nexyron.graph.list()
Catalog and projection procedures manage projected graphs, aggregate views, procedure metadata, and abstraction graph projections used by analytical workflows.
Consumer-Level Explanation
Use nexyron.graph.list when list named graph projections is the graph-analysis or operational question you actually need to answer. Keep the call explicit because its YIELD columns, row grain, and required runtime state determine how the rest of the Cypher pipeline can safely compose it. Use these procedures when the query needs to inspect or maintain derived structures explicitly instead of assuming they already exist.
Conceptual Explanation
nexyron.graph.list should be read as one named procedure contract in the broader Nexyron Cypher surface. The procedure call is not only a syntax hook: it defines what runtime state, projection, registry entry, or graph algorithm is being asked to operate, and it determines which output columns downstream YIELD, WITH, and RETURN stages can safely use.
More Detailed Explanation
This is for visibility into the currently materialized analytical snapshots
In practical queries, start by deciding the row grain you want after the call: one row per node, one row per path, one row per registry object, one row per artifact, or one row per summary. Then keep that grain explicit with YIELD and named projections. That is the difference between a useful planner-facing example and a vague call that downstream tooling cannot safely compose. For contract-driven procedures, the executable examples on these pages intentionally inspect procedure metadata unless the required named artifacts are created in the same example.
Advanced Example
This example yields named columns from nexyron.graph.list and returns a bounded result shape that downstream planner tooling can compose without guessing column names or row grain.
CALL nexyron.graph.list() YIELD name, node_count, edge_count, density
RETURN name, node_count, edge_count, density
ORDER BY name
Real Use Cases
- operator introspection
- projection inventory UIs
- cleanup and lifecycle management
- inventory projected graphs, aggregate views, and procedure metadata before running dependent analytics
- make derived structure maintenance explicit in migrations and operational checks
Real Limitations And Tradeoffs
- inventory pages are only useful if projection naming is disciplined
- catalog procedures describe or maintain registered structures; they do not validate that the underlying model is analytically appropriate
- dropping or refreshing derived structures can affect dependent workflows and should be treated as an operational action