Schema diagrams
Know your tables before a change.
Follow declared relationships, inspect columns and keys, and check the database names your code actually uses before changing a query or migration.
order_idPKproduct_idPKquantityInt
idPKuser_idFK
idPKemailString
What it does
A picture of the database structure declared in your project.
For projects with supported backend schema declarations, Iris Code reads the tables, columns, keys, indexes and relationships described in the repository. Diagram and Tables offer two ways to inspect that structure.
Focus a table to inspect its declared relationships and code usage. The diagram reads declarations, not a running database: no database credentials are needed, and it does not verify what is deployed or query your data.
- Switch between Diagram and Tables to inspect the same schema.
- Focus a table to see its declared relationships and code usage.
- Export schema structure for discussion and review.
Why use it
Check the names and relationships before writing the query.
A query or migration depends on the structure that actually exists in the project's schema declarations.
- Use declared names
- Inspect the table and its columns instead of guessing from a model name or an old description. The source declarations remain the authority behind the diagram.
- Read relationships in context
- Follow declared relations and keys around a focused table. That gives you structure to inspect before changing how records connect.
- Explain a schema change
- Switch to Tables for field details or export the structure for review. People can discuss the same declared schema without sharing live database access.
How to use it
Bring a backend schema. Leave the database credentials out.
This workflow is optional. Skip it if your project has no supported database schema declarations.
Open the repository's schema
Run Open Schema, or choose Schema inside Code Map. Iris Code reads supported declarations from the project.
Command palette Iris Code: Open SchemaResultThe declared tables and relationships appear when supported schema sources are available.
Focus a table
Inspect its columns, keys and declared relations in Diagram. Switch to Tables when a structured list is easier to read.
ResultYou can check the exact field names and structure before editing a query or migration.
Inspect usage and share structure
Read focused-table usage and export the schema for discussion. Whole-schema structure, focused usage and exports are Free; aggregate usage and warnings can be read from an earned workspace result. A fresh project inspection uses applicable project access.
ResultYou have repository-derived structure to review, with the Free and Pro scopes explicit.
The capabilities, in detail.
- Schema diagramFree / Pro scopes
- Tables, columns, keys and declared relationships from Prisma, SQL migrations, Drizzle, Django, Rails, Diesel. Whole-schema structure, focused-table usage and exports are Free. Aggregate schema usage and warnings are available from earned project evidence; fresh project inspection uses applicable project access.
Choose your scope
What's included.
- Free
- Whole-schema structure, focused-table usage and exports are Free.
- Pro and Teams
- Aggregate schema usage and warnings are available from earned project evidence; fresh inspection uses project access.
Know the boundary
What it doesn't promise.
Reads schema declarations in your repository. No live database connection or credentials are needed. It does not query your data or verify the deployed database.
Start here.
Open Iris Code: Open Schema, or select Schema in Code Map. Switch between Diagram and Tables to inspect columns, relations and indexes.