---
title: SHOW CONSTRAINTS
url: https://nexyron.tech/docs/cypher/clauses/schema-and-admin/show-constraints
description: Use SHOW CONSTRAINTS when the query must list current constraints and the planner needs to see that operation as part of the Cypher row pipeline. Keep the clause explicit because
---

# SHOW CONSTRAINTS

## Generic Description

List current constraints.

Simple example:

```cypher
SHOW CONSTRAINTS
```

## Consumer-Level Explanation

Use `SHOW CONSTRAINTS` when the query must list current constraints and the planner needs to see that operation as part of the Cypher row pipeline. Keep the clause explicit because it controls row grain, variable scope, and what later clauses are allowed to reference.

## More Detailed Explanation

SHOW CONSTRAINTS is part of schema introspection. It is useful for verifying whether the database is enforcing the rules you think it is enforcing.

What this clause is really for:

-   it defines one concrete stage in the Cypher row pipeline, so variables available before and after `SHOW CONSTRAINTS` must be clear
-   it should make graph structure, temporal filters, document payload shaping, or procedure output explicit instead of relying on client-side interpretation
-   planner tooling depends on this clause boundary to know row grain, variable scope, and whether later expressions are reads, writes, schema operations, or projections

## Advanced Example

This example keeps `SHOW CONSTRAINTS` inside a complete query pipeline so the clause boundary, visible variables, and returned row shape are clear to planner tooling.

```cypher
SHOW INDEXES
```

## Real Use Cases

-   schema audits
-   migration verification
-   tooling and admin UIs

## Real Limitations And Tradeoffs

-   should still be validated against current implementation and tests
-   inventory does not validate data itself
-   naming quality affects readability