diagram2codeBlog
Writing on turning ER diagrams into SQL and ORM code — the architecture behind diagram2code, hands-on tutorials, and why the diagram should be your schema's source of truth.
One Schema Model, N parsers, M generators
A walk through the design decision that makes adding a diagram format or an output target a one-sided change — plus how a shared dialect config keeps four SQL backends thin.
Read article →Mermaid to SQL: Generate PostgreSQL DDL From an ER Diagram (and Keep It in Sync)
A copy-pasteable how-to for turning a Mermaid erDiagram into Postgres or MySQL DDL, an ORM model, and a PR check that catches schema drift.
Read article →Your ER Diagram Should Be the Source of Truth, Not a Stale Picture
Stop drawing your schema twice. Make the diagram canonical, generate the SQL, and let CI fail the PR when someone drops a column.
Read article →I Kept Typing the Same Schema Twice. So I Built diagram2code.
The origin story of a tool that turns one ER diagram into SQL, ORM models, GraphQL, and OpenAPI — and the small, stupid problem that started it.
Read article →