Commit

4a497e7

When I design a schema, the whole model lives in my head. If someone renames a field while I am mid-design, that is not a merge conflict. It is a disaster. So Schemity, the desktop database design software I build, has no real-time co-editing, on purpose. On my teams, the person in charge of the design holds the pen. The diagram goes up on a screen share, everyone argues about it, and only one person touches it. The diagram is a plain JSON file, and its workspace folder sits in the project's repo, next to the code. Whoever disagrees after the meeting says so on the pull request. One person edits. Everyone still gets a say. How the diagram lives in Git with your code: https://schemity.com/doc/version-control-git/
schemity.comVersion Control in Git - Schemity DocsVersion control your database diagram in Git with Schemity: import a workspace into your repo and commit the JSON. Review a schema change by opening its migration in the change preview.

commit 4a497e7