Its feature-rich, albeit focused on Postgres. And it's ability to compare database schemas makes updating and applying diffs much easier.
Found a simple tool for database modeling: dbdiagram.io
21–30 of 76 posts
Re: Found a simple tool for database modeling: dbdiagram.io
#22Other 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)
Re: Found a simple tool for database modeling: dbdiagram.io
#23Re: Found a simple tool for database modeling: dbdiagram.io
#24Re: Found a simple tool for database modeling: dbdiagram.io
#25Re: Found a simple tool for database modeling: dbdiagram.io
#26When you have a complex data model and need to constantly engage the business regarding it, having an easy way to transform, compare and visualize representations of the schema can mean the difference between ~3 clicks and a multi-day journey into the rabbit hole of shiny technology.
I would still reach for SQLite in any scenario where I am embedding the DB in software that I am distributing. But, if I need to stand up a database that multiple systems and users are all going to talk to, I am always going to advocate for spending a little bit of money.
Re: Found a simple tool for database modeling: dbdiagram.io
#27Mermaid is also great https://docs.mermaidchart.com/blog/posts/7-er-diagram-exampl...
I found out about mermaid recently and have been using it to make diagrams. How do you use it for data modeling though?
Re: Found a simple tool for database modeling: dbdiagram.io
#28Mermaid is also great https://docs.mermaidchart.com/blog/posts/7-er-diagram-exampl...
I found out about mermaid recently and have been using it to make diagrams. How do you use it for data modeling though?
---
title: Order example
---
erDiagram
CUSTOMER ||--o{ ORDER : placesRe: Found a simple tool for database modeling: dbdiagram.io
#29In most projects I've seen people just do some generic models (not even proper ED diagrams) and write some SQL migrations to be applied with something like dbmate or Flyway and call it a day, though working on DB schemas feels like one of the areas where model driven development actually makes a lot of sense and feels natural, if the tooling is there! Otherwise you end up with the actual schema and the models you make diverging slightly over time, either due to people forgetting to add stuff, or you yourself missing something. That's also why I enjoy the likes of DbVisualizer for getting a nice overview about what's actually in the schema: https://www.dbvis.com/