did you consider letting the input be just sql ddl rather than yet another layer of ddl?
We will have "import" functionality available soon. You should be able to convert database specific DDLs into diagram language.
51–60 of 87 posts
did you consider letting the input be just sql ddl rather than yet another layer of ddl?
We will have "import" functionality available soon. You should be able to convert database specific DDLs into diagram language.
Cool tool. My favorite tool for text to model / model to SQL is: https://app.quickdatabasediagrams.com/
We've been using https://dbdiagram.io/ , which also has an open-source markup language: https://github.com/holistics/dbml
When I see things like this, now my immediate question is always: what's the underlying model? Is this like a generally open and free thing, with maybe a little bit of monetization to keep the lights on? Then that's great. But, if this is looking to be a big moneymaker? eh, nah.
Absolutely right! Everyone launching a beta version of their product says its free. You invest time learning and migrating things over and by the time they catch up on features, pricing page shows up. I have been using https://www.erdlab.io for 6 months now and so far it looks like they are true to their word. The developers on ERDLab have fulltime jobs and treat it as a side project but still push out updates and ha…
I have been using this tool just for myself for the last few months. The project is intentionally built for longevity (striving to keep the project for decades, if there are serious users). The costs to run are negligible, and I haven't thought much about monetizing. At this point, evaluating if there is enough interest in the tool
it works! but dies a little with many tables :-)
code: https://paste.rs/1ZHp7.py3
screenshot: https://i.imgur.com/4D2hEWc.png
We've been using https://dbdiagram.io/ , which also has an open-source markup language: https://github.com/holistics/dbml
ive been a keeping a list of other diagramming tools too https://github.com/swyxio/spark-joy/blob/master/README.md#di...
1. Why not just use SQL? 2. You should really work on error handling. I went to /app and tried changing the name of the CustomerID column, and nothing happened. I tried changing something else and it didn’t work either. It should tell me that the other table is mentioning a non-existent column and the input is invalid.
1. Every database has its own flavor of SQL syntax. So we need to settle on a minimal syntax that can export to any database. (BigQuery, Snowflake, MySQL etc..) 2. I tested it out. When i attempt to change CustomerID it does show a error toast in the bottom saying FK reference is invalid. Not sure, why its not showing up for you. Which browser are you using ?