Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Nice, but there is no LICENSE file in the github: https://github.com/royalbhati/sqltoerdiagram
    by petilon
  • I'm using https://github.com/ondras/wwwsqldesigner and I think that's worth taking it in account for comparison.
    by mingodad
  • btw did you know that ER diagrams are supported by Mermaid diagrams: https://mdview.io/mermaid?example=working-er It's not that pretty as in your app, but it does the work
    by Igor_Wiwi
  • Reminds me of: https://explain.dalibo.com/

    For visualizing query plans. One of the most useful tools for optimizing sql queries I’ve ever used.

    Just make sure to download the fully offline v2 version at the bottom if you want to use it with anything sensitive.

    by throwatdem12311
  • Could we have the option of straight lines and 90 degree angles? I’ve never really liked the bendy ones. Looks cool, good job!
    by corkybeta
  • It's a small too nothing great I just figured others might find it useful too. I kept finding myself needing to visualize database schemas, but most tools had the same problems: paywalls, mandatory signups, or sending your SQL to someone else's server.

    No backend, no accounts, no data leaving your machine.

    A few implementation details that were fun:

    * Built on <canvas> instead of DOM/SVG. Tables are rasterized into cached bitmaps with viewport culling, which keeps things smooth even with hundreds of tables on screen.

    * The SQL parser tracks source spans for every token. That lets edits stay surgical so a rename a table and only the relevant identifier (and its references) change while comments and formatting remain untouched.

    * The URL contains the entire schema. Sharing simply serializes the schema into the URL itself, so there's no backend, no stored state, and no account required.

    * I also experimented with a Rust/WASM version because why not? but the parser was ~37% slower because the JS↔WASM boundary cost outweighed the compute savings but The O(n^2) overlap-resolution pass was about 2.2x faster though * In the end I stuck with plain JavaScript. No framework ~32KB gzipped

    by robhati
  • The tool looks very cool! But IMO you can't get an ER diagram from SQL since entities are fundamentally different from tables. They are certainly very similar, but SQL alone doesn't give you enough information to create an ER diagram.

    That's not to say that the tool is useless or that diagrams of this sort are unhelpful. I'll admit I'm being pedantic and others will probably disagree.

    by michaelmior
  • 100/10 for mobile usability. Panning, Zooming, selecting and moving was so seamless I thought I was tripping out.
    by written-beyond

Explore Birbla archives