[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: To Normalize or Not to Normalize
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@k...] 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?
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|