OP here. If you've ever wrestled with a complex SQL schema, I built this project because I’ve always found that traditional 2D ER diagrams turn into unreadable "spaghetti" once a database grows beyond a certain size.
I wanted to test if adding the Z-axis (via three.js) could solve the crowding problem. My hypothesis is that by utilizing 3D depth, we can separate distinct table clusters and illustrate relationships without the visual chaos of crossing lines.
I’m specifically looking for feedback on a few things:
1. Utility vs. Gimmick: Does the 3D aspect genuinely help you explore the schema better than a 2D view, or does it feel more like a novelty?
2. Navigation: How do the camera controls feel? Is it intuitive to inspect specific table details?
3. Enhancements: This is a first pass—if you see a path for this to become a practical daily driver tool, I’d love to hear your thoughts.
shane-jacobeen•2mo ago
I wanted to test if adding the Z-axis (via three.js) could solve the crowding problem. My hypothesis is that by utilizing 3D depth, we can separate distinct table clusters and illustrate relationships without the visual chaos of crossing lines.
I’m specifically looking for feedback on a few things:
1. Utility vs. Gimmick: Does the 3D aspect genuinely help you explore the schema better than a 2D view, or does it feel more like a novelty? 2. Navigation: How do the camera controls feel? Is it intuitive to inspect specific table details? 3. Enhancements: This is a first pass—if you see a path for this to become a practical daily driver tool, I’d love to hear your thoughts.
Thanks for checking it out!