Other than the visual differences in the output diagram, I think the other main difference is the way the table & columns are created.
dbdiagram is freeform text-based and parses that to generate the diagram, while in DrawSQL there's an editor supported by keyboard-shortcuts to do the creation.
Overall they achieve similar outcomes. Personally I think it's a well-built tool too!
Great suggestion - I agree, having an easy way to view the diagrams in full screen would be so useful and solve that. For now you can actually click on the "DrawSQL" logo within that opens it in full screen in a new tab.
If you imported the diagram from a SQL DDL script, then it does generate relationships based on the foreign keys. I can then add the other missing ones.
In the future there will be smarter ways to infer them, e.g. searching for {table_name}_id etc. In fact I did use a crude script that did just that when curating the diagrams for the gallery. Just need to build a nice frontend for it.
Thanks, good to know of the alternate constraints in other companies. Pricing aside, indeed it would be a different challenge tech-wise to have this as an offline tool.
My motivation for building this stemmed from the use-case of smaller-medium dev teams. We were using offline tools (e.g. MySQL Workbench) as part of our dev process and trying to keep it updated as documentation. Which was quite a nightmare to keep in sync between different devs. In this case having a central server was the silver bullet.
Curious - do you all currently use other tools (eg: workbench) for this?
Interesting, though I think that will make more sense in the future when new features to better compartmentalize sections of the diagram is introduced. I imagine it will be a mess of lines right now haha
Thanks, a big part of this idea actually came from lecturers that have been using DrawSQL for teaching in uni classes :). I agree will definitely reach out to a few more to see if this tool will be valuable.
On making it fullscreen, that's such an useful/obvious thing to include in hindsight. Thanks for the suggestion! For now you can actually click on the "DrawSQL" logo within that opens it in full screen in a new tab
Hey all, maker of DrawSQL here. To dog-food the app over the past year, I've been mapping out the database schemas of open-source packages and apps... lots of them in fact!
Then it clicked, these collected diagrams could be useful for other developers to use as references as well. And maybe bring some SEO juice to the DrawSQL over the long-term. Hence the idea to curate this gallery - A central place to browse & discover DB schemas.
First time posting in HN, let me know what you think, or if you have a schema to suggest that should be added. Thanks!