I would absolutely love a free tool that compiled SQL into UML suitable for diagrams and visual exploration.
BTW, one that did the same for Terraform would make my life so much easier…
Found a simple tool for database modeling: dbdiagram.io
51–60 of 76 posts
Re: Found a simple tool for database modeling: dbdiagram.io
#52It's really convenient for being able to quickly whip up diagrams to share for discussion. Like when you have a small group of folks that need to iterate on a DB design, it's super simple to change things.
I've used this a bunch early in projects where the team needs to agree on DB structure:
1. whip something up as a discussion piece 2. usually a quick meeting to iterate on it, spot problems, correct. 3. you're close enough to build the DB bits, ship it. :)
Re: Found a simple tool for database modeling: dbdiagram.io
#53I would absolutely love a free tool that compiled SQL into UML suitable for diagrams and visual exploration. BTW, one that did the same for Terraform would make my life so much easier…
I was also very interested in finding a TF auto-diagramming tool at some point. After researching some examples however, I became convinced that it's not something I actually wanted or could make proper use of.
The issue I had with them is that they were just plain confusing and "noisy". After reflecting on it a bit, this made sense. Diagrams are only ever easy to follow if they have a clear purpose, but with minimal to no human semantic context, these auto generated diagrams could never be that way. They were just aimless scattershots of boxes with pretty icons on them.
Maybe it was just me not being used to them enough, and I could have grown to appreciate them and utilize them well if I bothered for long enough. But if I think about what I'd want from a diagram, it would be things like how data flows through an infrastructure, which Terraform cannot hope to have an exact idea about. And this only gets worse when you upload custom code, such as by using lambdas, containers, ec2 instances, what have you.
Re: Found a simple tool for database modeling: dbdiagram.io
#54The FLOSS tool https://drawdb.vercel.app/editor has been here on HN several times. IMHO also does a somewhat better job.
Doesn't seem to work on mobile at all. Tables that I add are not shown in the diagram. The diagram area is not visible unless I scroll sideways.I cannot scroll sideways, unless I request desktop site and scroll there. But I still don't see any entities in the diagram. When I use the buttons to add tables in the diagram, they also do not show up in the grid, but only on the left in the textual list of tables. Seems li…
I wouldn't think mobile is a primary workspace for doing any sort of diagramming, let alone ERD where its assumed the user has a PC.
Re: Found a simple tool for database modeling: dbdiagram.io
#55I maintain an almost exhaustive list of text to diagram tools [1]. dbdiagram.io requires login to export. Other dedicated text to database diagram tools are 1. Database Diagram Tool https://databasediagram.com/app 2. QuickDBD https://app.quickdatabasediagrams.com/#/ 3. ERD Lab https://app.erdlab.io/designer/guest (Requires Login to Export) [1]: https://xosh.org/text-to-diagram/
Is there a tool that can connect to a db and generate its own diagram?
Re: Found a simple tool for database modeling: dbdiagram.io
#56I maintain an almost exhaustive list of text to diagram tools [1]. dbdiagram.io requires login to export. Other dedicated text to database diagram tools are 1. Database Diagram Tool https://databasediagram.com/app 2. QuickDBD https://app.quickdatabasediagrams.com/#/ 3. ERD Lab https://app.erdlab.io/designer/guest (Requires Login to Export) [1]: https://xosh.org/text-to-diagram/
Is there a tool that can connect to a db and generate its own diagram?
DBeaver will generate an ER diagram from a connected DB
Re: Found a simple tool for database modeling: dbdiagram.io
#57Earlier quoted context omitted.
Is there a tool that can connect to a db and generate its own diagram?
DBeaver will generate an ER diagram from a connected DB
I find the auto-generated layout to be pretty poor. Requires a lot of jostling to get something more compact and immediately usable.
Re: Found a simple tool for database modeling: dbdiagram.io
#58What's wrong with dbeaver?
Honestly, i love dbeaver but the fact it doesn't respect GTK nicely and the UI hasn't gotten much love makes me want to switch to something else. I know most people don't really get bothered by it, so I'd say it's not that big of a deal. It is for me though
What else is on the table that is similarly nice? The only other contender of which I am aware is DataGrip.
I likely only use 1% of the DBeaver features, so I do not necessarily need something as powerful, yet most of the database IDEs feel pretty anemic in their offerings.
Re: Found a simple tool for database modeling: dbdiagram.io
#59I maintain an almost exhaustive list of text to diagram tools [1]. dbdiagram.io requires login to export. Other dedicated text to database diagram tools are 1. Database Diagram Tool https://databasediagram.com/app 2. QuickDBD https://app.quickdatabasediagrams.com/#/ 3. ERD Lab https://app.erdlab.io/designer/guest (Requires Login to Export) [1]: https://xosh.org/text-to-diagram/
Is there a tool that can connect to a db and generate its own diagram?
Proprietary and a bit pricy but Luna Modeller is good.
Re: Found a simple tool for database modeling: dbdiagram.io
#60I have an issue with calling any of the diagrams created by all the tools mentioned "ER Diagrams". Entities are not the same thing as tables, and Sr diagrams are not relational database table diagrams. A (semi) visual representation of a database schema of any size that'd require a visual representation is almost necessarily a mess, and doesn't really help discussion or design. It is at best a faster indexing into the DDL for the tables.
What I'd love to have (but never saw an affordable tool) is the ability to work at different levels of abstraction: physical (which is what all tools here actually do), logical (hiding field details, normalization and de normalization, giving better business entity names, etc) and conceptual (to show how big picture concepts relate, domain boundaries, department dependencies/relationships).
Just the physical representation does, for my purposes, little more than code highlighting.