Database 'relationship designer'
Posted on 2014-07-26
I think we missed the boat in designing our database, and our needs have morphed into something different. My guess is that this happens allot between those with the business need and the developers, and has thus prompted this question.
Let's say we want to do our project in MySQL but don't want to dive right into designing the tables until we have the relationships, requirements, and so forth drawn out first.
What is the best way to do this for step one of creating a database for any purpose.