On Fri, Jun 18, 2010 at 2:41 PM, Paul McNett <[email protected]> wrote: > > I believe in the proper design but usually I still start with a non-normalized > design. Like everything, it can be refactored once it is needed. > > IOW, I try to do the simplest implementation that satisfies the needs. Much > easier to > get stuff out the door, *and* to maintain in the future. >
I think 'normalization' gets a bad rep. It doesn't help that advocates think that calling things "fourth normal form" in Baukus-Nour format makes it easier to understand ;) Many people get the principle that "things should be in only one place" but then go nuts with it and store all phone numbers in a single table, whether they are customer service numbers, order fax numbers or emergency pager numbers. That's not a normalized design. People also fall into the trap that they don't consider whether their system is modelling a snapshot of the current business or a historical audit trail of its past, or both. Gee, I could lecture all day on this. Oh, wait, I have! -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
