> >> > Read the literature on how to design databases. What you do > >> > is storing "true propositions". That is, each attribute defines a > >> > certain "true proposition". For example: > >> > > >> > Employee "Martijn" has Employee# 14. > >> > > >> > You should be able to derive these sentences from every row. > >> > Putting a NULL or N/A in there fails to meet this requirement. > >> > > >> Perhaps my theory is a bit rusty but I have never heard of this "true > >> propositions" business before. Do you have a citation where I can read > > about > >> this? > > > > I would certainly recommend this one: > > http://www.amazon.com/exec/obidos/ASIN/0321197844/databasede095-20/103-0880452-0854264?creative=327641&camp=14573&adid=0VQ1KDVJ56MV7389RPEQ&link_code=as1 > > > Hmm, I had hoped for a citation to a free online document that I could read. > I don't fancy the thought of spending $100+ US on a book just to argue the > fine points of database design.... > > Then again, I didn't ask for a link to a free source of this information so > I can't fault you for your link, it (presumably) answers the question.
You will find the true-thingy also in here: http://www.dbdebunk.com/page/page/2928212.htm Martijn Tonies Database Workbench - development tool for MySQL, and more! Upscene Productions http://www.upscene.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
