Show HN: Dbdot – Golang tool to help generate Postgres schema diagrams
1–10 of 13 posts
Re: Show HN: Dbdot – Golang tool to help generate Postgres schema diagrams
#2Re: Show HN: Dbdot – Golang tool to help generate Postgres schema diagrams
#3Ideally there'd be an officially supported tool that allowed you to define your relationships at a high level and it would create a well normalised and indexed schema for you automatically.
Re: Show HN: Dbdot – Golang tool to help generate Postgres schema diagrams
#4At least bottom to top would pack the independent ones to the top and those that represent many-to-many relationships at the bottom.
From my work with Oracle Datamodeler know that even at a dozen tables manual layout beats an algorithm any time. And the oracle algithms are more sophisticated/less general than dot.
Re: Show HN: Dbdot – Golang tool to help generate Postgres schema diagrams
#5Good schema design tools are the missing piece for making PostgreSQL the complete package. Ideally there'd be an officially supported tool that allowed you to define your relationships at a high level and it would create a well normalised and indexed schema for you automatically.
Re: Show HN: Dbdot – Golang tool to help generate Postgres schema diagrams
#6The diagrams in that way are problematic. When you model them as digraphs and use this layout and order them from too to bottom you get all the tables at the top that represent n:m relationships and at the bottom (at different levels) your main/independent entities. At least bottom to top would pack the independent ones to the top and those that represent many-to-many relationships at the bottom. From my work with Or…
Re: Show HN: Dbdot – Golang tool to help generate Postgres schema diagrams
#7Re: Show HN: Dbdot – Golang tool to help generate Postgres schema diagrams
#8For high-level/quick-and-dirty designing I'm a fan of https://dbdiagram.io/
Only as a next step you translate that to the actual relations.
Re: Show HN: Dbdot – Golang tool to help generate Postgres schema diagrams
#9The diagrams in that way are problematic. When you model them as digraphs and use this layout and order them from too to bottom you get all the tables at the top that represent n:m relationships and at the bottom (at different levels) your main/independent entities. At least bottom to top would pack the independent ones to the top and those that represent many-to-many relationships at the bottom. From my work with Or…