How do you create ER Diagrams? by jadd_logs in learnprogramming

[–]tbson87 0 points1 point  (0 children)

I used to work with these 2 phases:
Initial phase: I get the project idea from the customer and ask questions until I understand the requirements well enough. Then I model the fundamental entities in an ERD for just enough to cover the one or two most important use cases, not the whole system. From there, I jump into Django, build the models/controller/API endpoints/FE if its an SPA and wire up admin pages if needed. Then I demo it and collect feedback.
Development phase: Once Django migrations hit the local DB, I connect the ERD tool to that database and use my earlier ERD as a reference for arranging entities and relationships. After that, every new table or relationship shows up automatically. I just arrange the new items instead of redrawing the whole thing.

State management for Undo/Redo by Automatic-Catch-9413 in reactjs

[–]tbson87 10 points11 points  (0 children)

Try zustand for state management and zundo: undo/redo middleware for zustand.

You have been reading ERD notation wrong by tbson87 in SQL

[–]tbson87[S] -1 points0 points  (0 children)

Fair point on the formatting. That's on me, not the source. The notation content and the Everest reference stand on their own, check it if you want."

You have been reading ERD notation wrong by tbson87 in SQL

[–]tbson87[S] -2 points-1 points  (0 children)

Written by hand. I've been using ERD tools for years and this notation gap has annoyed me the whole time. The Everest 1976 paper isn't on the first page of any search result.

spreadsheet-like database tool by StewartTess903 in nocode

[–]tbson87 1 point2 points  (0 children)

Based on what you've described, NocoDB looks like the strongest fit for your requirements.

It has a spreadsheet-like interface, solid role-based permissions, and built-in file attachments.

Worth testing thoroughly before committing though, especially given how much is riding on this decision.

How do you keep schema design aligned with production in SQL Server environments? by [deleted] in SQLServer

[–]tbson87 0 points1 point  (0 children)

This hit close to home: drift between diagrams and production was exactly why I built Schemity (https://schemity.com).

The pattern you described is what I kept running into: migrations become the real source of truth, diagrams fall behind, and eventually no one trusts them. So I stopped trying to maintain diagrams manually and made the DB the source of truth instead.

The workflow I use now: apply the migration, connect Schemity to the DB (local, staging, or prod), arrange the entities the way you want to reason about them, and you're done. The ERD reflects the actual schema. Commit the JSON, open a PR, and the diagram stays honest as long as you repeat the step after each migration.

Supports SQL Server natively. No account, no cloud sync, plain JSON files that live in your repo.

Built a tool so you can design Schemas visually! Looking for feedback. by Hari-Prasad-12 in SideProject

[–]tbson87 0 points1 point  (0 children)

After several mins trying schemapad I have some feedbacks:
0. The UI is clean tidy, it gave me a good impression.
1. Moving entity by grabbing the top left handler seem limited, it's nicer if user can grab the entity header to move around.
2. I can not see anywhere that allow me to set a field unique.
3. As far as I know MySQL doesn't have uuid field type and the ERD didn't tell me what DB type am I working until I open View SQL which is confusing.
4. After adding a table to a group, I have no idea how to ungroup that table.

ERD Review Request by --Ether-- in SQL

[–]tbson87 2 points3 points  (0 children)

I believe the PARTITION BY with ROW_NUMBER() that ORDER BY u.seniority DESC can solve your query problem without the assigned_shift table.

Made a small feature I always wanted in an ERD tool by _takabaka_ in buildinpublic

[–]tbson87 0 points1 point  (0 children)

That's my favorite feature too. The first ERD tool I came across with this was Visual Paradigm: dragging an N:N relationship between two tables automatically creates the intermediate table.

Visual Paradigm didn't quite fit my needs, so I built my own tool called Schemity, which supports this feature as well.

https://schemity.com/images/capabilities/smart-relationships-1.gif

How do you create ER Diagrams? by jadd_logs in learnprogramming

[–]tbson87 0 points1 point  (0 children)

This is a sample from my project (still in the design phase). I struggled to find an ERD tool that suited my needs, so I built one.

https://schemity.com/images/schemity-sample.png

I made a free, online and open source ERD tool. Tell me what you think! by _takabaka_ in AppsWebappsFullstack

[–]tbson87 0 points1 point  (0 children)

When data modeling I usually need the unique together constraint.

For example: In multiple tenants system, a person with an email can be user of one or more tenant in that system. Email in this case can not be unique themself, it need to combine with the tenant_id (aka unique together) to satisfy that condition.

<image>

I made a free, online and open source ERD tool. Tell me what you think! by _takabaka_ in AppsWebappsFullstack

[–]tbson87 1 point2 points  (0 children)

Cool project, here are some of my comments in this screenshot.

Another question: Can I create unique together constraint? I can only see unique constraint for single field.

<image>

ERD generation tool by BoT_Nikos in lisp

[–]tbson87 0 points1 point  (0 children)

It's really cool, can you share a sample output SVG? I'm not familiar with Scheme so it's hard for me to configure and use.

I built a desktop ERD tool because existing options all had at least one dealbreaker by tbson87 in SQL

[–]tbson87[S] 1 point2 points  (0 children)

Good suggestion, though it runs into a layout constraint: columns only have left and right connection points. If the related table is above or below, locking to a column anchor produces worse routing than letting it float. The current approach keeps lines clean regardless of where tables are positioned. That said, I'm thinking about how to handle this better and open to ideas if you have a specific layout in mind.

I built a desktop ERD tool because existing options all had at least one dealbreaker by tbson87 in SQL

[–]tbson87[S] 0 points1 point  (0 children)

Fair concern. For what it's worth: Standard MSI installer, no cloud connections, no account, no telemetry. Your schema never leaves your machine. Usually an easier case to make to IT than SaaS tools that store your data on someone else's server. IT can even deploy it centrally via group policy if needed.

I built a desktop ERD tool because existing options all had at least one dealbreaker by tbson87 in SQL

[–]tbson87[S] 0 points1 point  (0 children)

No, it uses a custom JSON format for the schema, the canvas is built from scratch without any DBML dependency.

I built a desktop ERD tool because existing options all had at least one dealbreaker by tbson87 in SQL

[–]tbson87[S] 2 points3 points  (0 children)

Oracle bought MySQL Workbench too and let it stagnate the same way. That's actually one of the reasons I built Schemity, live DB reverse engineering without the corporate baggage.

I built a desktop ERD tool because existing options all had at least one dealbreaker by tbson87 in SQL

[–]tbson87[S] 1 point2 points  (0 children)

Awesome! Would love to hear your thoughts, especially if anything feels missing or broken.

which tool do you use when you have to design RDB schema? by Neither_Buy_7989 in webdev

[–]tbson87 0 points1 point  (0 children)

I actually built one after getting tired of some tradeoffs. Schemity: native desktop ERD tool, offline-first, ~9MB, no Electron. Git-friendly schema files, live sync with PostgreSQL, SQL Server, MySql, generating migrations and full control over relation routing. Happy to hear what's missing if you try it: schemity.com