Re: Enforcing Referential Integrity: Pros vs. Cons?
Date: Tue, 16 Nov 2004 12:20:50 -0600
Message-ID: <cndge8$a4e$1_at_news.netins.net>
"Marshall Spight" <mspight_at_dnai.com> wrote in message
news:b1rmd.39567$V41.7776_at_attbi_s52...
> "Gene Wirchenko" <genew_at_mail.ocis.net> wrote in message
news:7os1p0l9pliemtr8hniui8h128jr2q3okq_at_4ax.com...
> >
> > It is a way to get speed. It is at the expense of accuracy, but
> > some do not see that.
>
> Or sometimes they see it and they don't care. Sigh.
Accuracy has many faces. When a system is rigid, the users of that system figure out how to work around the system rather than request or make changes. We have all seen systems where the end user or even the application developer decides they will store this code in that location because it isn't currently used for anything else. When the metadata does not accurately name the data, the system is not accurate.
The trade-off isn't really one of speed for accuracy -- it has to do with the ongoing support for an accurate system and the agility (I know some don't like the word, but it is a good word) of the trustees of the system to make accurate changes to the system in a timely fashion.
--dawn Received on Tue Nov 16 2004 - 19:20:50 CET