OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   RE: [xml-dev] To Normalize or Not to Normalize

[ Lists Home | Date Index | Thread Index ]

Insight.

It is a common experience.  With the current chasm 
crossings to web-based tech, possibly very common.

As Frank says, research first, of course.  Now what 
questions are important?

My first clue is that denormalization is either intentional 
(performance, for example) or laziness (multiple developers, 
not enough discipline or communication), historical (obtained 
the code from another company and built on it), or accidental 
(didn't know two fields were the same thing).

Names seem easier but can be harder.

Of course, finding out where the customer intends to spend 
money or resources now, next and after next is important.

len

From: Robert Koberg [mailto:rob@koberg.com]

Can there be any other answer than "It Depends" ?

What's the budget? What's the time frame? How important is the app?

Given the all too common and absurd answers to the above questions, my 
strategy would be to bail out, start my own company and do what I want :)

seriously, what are you expecting here?




 

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS