No, I agree! Just saying that it's always better to fix the underlying problem (i.e. the db design) than coding around it.
The metaphor "Fix broken windows" refer to the idea, that if you leave even small bits of bad code in your code base, it spreads to other code. Better to bite the bullet and fix the DB design *apparently this comes from a study, that showed, if a broken window in housing block is left unrepaired, that occupants start to disrespect the property and that broken window leads to further problems* WG > -----Original Message----- > From: Dina Hess [mailto:[EMAIL PROTECTED]] > Sent: 17 January 2003 18:06 > To: CF-Talk > Subject: Re: WOT: Access SQL Question - Round 2 > > > I'm not too sure what you're getting at...maybe I wasn't clear. > > My point was that a list of values should not be stored in a DB > field. This is a basic criterion of a normalized database. It > tends to become increasingly difficult to work with such databases. > > > > Too bad you have to go thru all of this...a normalized database > > schema would've prevented this problem...which you probably > > haven't seen the last of... :) > > > > ~Dina > > Ouch! Database - Refactoring 101 > http://www.agiledata.org/essays/databaseRefactoring.html > > Always fix broken windows... > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
