The question I have is this, and don’t attack me for asking, but do people still produce database diagrams for use at work? I thought we had abstracted this by using Domain Driven design, ORMs, APIs, and the like.

Do individual teams still document their tables or do they document their entities? Do you still hand roll sql in a dao or do you use some higher abstractions?

Curious minds want to know because it’s been over a decade since I’ve done any database design documentation and have only done lean relationships and domain modeling documentation. Swaggering the rest.

I will say this, I love the look of this and I would love to just draw abstract shapes and things like I do on Miro. AWS architectures, etc etc.

How did you solve the AGPL hurdles for that pre-CLA third-party code? It's usually impractical to get a lot of contributors to retroactively sign a CLA. Did you have to rewrite some/all of those older code contributions, or is the full cloud product open source as well?

I tried a few other DB visualization tools but was turned off because it felt like I needed to learn another toolset, when I just wanted to import my schema and start working with it. ChartDB's approach was better for me, the single query import worked fine, and adding to the schema works how you'd expect.

Really hoping to see a feature for “diffs between the dev diagram and the live DB”. we’re collaborating on the diagram as a team, and it’d be great to track what changed between our current draft and the actual database.