> I'll give you a simple example. Consider, movies and directors. If you started with the fact that each movie has exactly one director, you'd design exactly one table, with a director column.
With respect, if you have that little domain knowledge, you shouldn't be designing--er, coding--anything other than a throwaway exploratory scrap.
And in preference to doing that, you should be getting out and talking to the people who plan to use your database, and learning how they think, and what about.
Systems analysis is another '80s development "fad" that is way underrated.
With respect, if you have that little domain knowledge, you shouldn't be designing--er, coding--anything other than a throwaway exploratory scrap.
And in preference to doing that, you should be getting out and talking to the people who plan to use your database, and learning how they think, and what about.
Systems analysis is another '80s development "fad" that is way underrated.