Re: Multiple specification of constraints

"Dawn M. Wolthuis" <dwolt_at_tincat-group.com> wrote in message news:c258v3$v9c$1_at_news.netins.net...
> It does seem that DBA's spend a lot of time trying to figure out how to
> prevent programmers from doing this or that.

That's a bad situation, agreed. Most of the problems I've run into are security-related, not "data definition" related.

> One or more software
> applications written with the teamwork of all participants addressing how
to
> get the most integrity in the stored data seems like a less flawed
strategy
> than having DBAs figure out how to block programmers who figure out how to
> get around the walls built by the DBA.

Definitely true.

> Even though you cannot ensure that the data coming into a system is sound,
> if you take 100 software development teams and have them write
applications
> to meet the same data requirements (no UI specified), there will be some
> variance in the quality of the data captured that is due to the way the
> applications were written, right? So, you cannot prevent garbage coming
in,
> but you can encourage quality input.

Agreed again. I just want to be sure that multiple programmers don't have the opportunity to corrupt data which is required to meet constraints the business demands, just because they don't understand them.

• Eric