nexyron.graph.drop

Generic Description

Delete a named projection.

Simple example:

CALL nexyron.graph.drop({name: 'people_knows'})

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.drop when delete a named projection 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.drop 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

Use it to reclaim conceptual and operational space once an analytical snapshot is no longer needed

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.drop and returns a bounded result shape that downstream planner tooling can compose without guessing column names or row grain.

CALL nexyron.graph.drop({name: 'people_knows'}) YIELD name, node_count, edge_count
RETURN name, node_count, edge_count

Real Use Cases

Real Limitations And Tradeoffs