Problem
UNIQUE constraints and indexes are important parts of a schema's semantics but are not visualized. A column with a unique constraint behaves differently from a plain nullable column, and this distinction matters when reading an ERD.
Proposed
- Mark columns that participate in a
UniqueConstraint with a small indicator (e.g. a U badge or underline) in both HTML and SVG renderers
- Optionally list multi-column unique constraints as a footer row in the table card
- Index visibility could be opt-in via
show_indexes=True to avoid cluttering diagrams for schemas with many indexes
The data is available via table.constraints and table.indexes in SQLAlchemy metadata.
Problem
UNIQUE constraints and indexes are important parts of a schema's semantics but are not visualized. A column with a unique constraint behaves differently from a plain nullable column, and this distinction matters when reading an ERD.
Proposed
UniqueConstraintwith a small indicator (e.g. aUbadge or underline) in both HTML and SVG renderersshow_indexes=Trueto avoid cluttering diagrams for schemas with many indexesThe data is available via
table.constraintsandtable.indexesin SQLAlchemy metadata.