Keep in mind that 'bad normalization' can equal
'good optimization'. I seldom see fully-normalized
databases because the overhead of getting and
opening tables, creating the view, etc. can be
prohibitive vs the maintenance of denormalized
data. Otherwise, I would agree. These aren't
legacy databases. They are practical ones where
performance considerations dominate maintenance.
len
From: Joe English [mailto:]
What are the real-world use cases of minOccurs and maxOccurs?
In my experience, occurrence constraints specifying anything
other than zero, one, or many are almost always an indication
of a bad design decision somewhere in the system.
(Or maybe that *is* the use case? To be able to accurately
describe badly normalized legacy RDBMSs and other such things?)
