Skip to main content
The Schema tab shows the shape of the selected graph rather than the result of your query. It is derived from the graph itself with read-only queries, so opening it never modifies data and never re-runs the query in the editor. Schema view with a label selected

​
What it draws

  • Nodes are node labels. Nodes without any label appear as a single No Label entry.
  • Links are relationship placements — one link per distinct (source label, relationship type, target label) triple found in the graph. Two labels connected by the same type in both directions therefore show two links.
Because a link is a placement and not a relationship type, the counter under the canvas reads Connections, not “relationships”.

​
Controls

The Schema tab reuses the graph canvas, so panning, zooming, layouts, and the Labels/Relationships filters behave the same way as on the Graph canvas. The controls next to the tab strip are:
  • Zoom in / Zoom out
  • Fit graph to screen
  • Labels: n — how many labels were discovered
  • Connections: n — how many placements were drawn
Editing controls are hidden: the Schema tab is always read-only, so there is no Add node, Add edge, or Delete. There is no refresh button. The schema is rediscovered whenever you open the tab, and results are cached per tab so switching back is instant.

​
Inspecting a label or relationship type

Select a node or a link to open the details panel, titled Label Schema or Relationship Schema. It lists every property key discovered for that label or relationship type in four columns: Schema view with a relationship placement selected

​
How the schema is discovered

  • Relationship placements and the label list are read exactly, aggregated on the server.
  • Property keys are sampled: up to 10 elements per label and per relationship type are inspected. This keeps discovery fast on large graphs, but a key that only appears on rarely used elements may not be listed.
  • Constraints and index information come from the graph’s own constraint and index metadata, so they are exact.

​
Per-tab state

Schema state belongs to the graph tab it was opened in: layout, viewport, hidden labels, and the selected element are remembered separately from the Graph tab’s own state, and are restored when you come back.

​
Frequently Asked Questions

No. The schema is discovered with separate read-only queries. Your query, its results, and the Graph/Table/Metadata tabs are untouched.
Each link is a placement — a distinct source label, relationship type, and target label combination. One relationship type can produce several placements, so the count is of drawn links.
Property keys are sampled from up to 10 elements per label or relationship type. A key carried only by elements outside that sample is not reported.
They reflect the graph’s constraints. Unique means no two elements of that label or type can hold the same value for the property. Mandatory means every element of that label or type must carry the property.
Switch away from the Schema tab and back. The schema is rediscovered each time the tab is opened.