Re: Arbitrary Constraints
Date: Wed, 27 Oct 2004 09:25:41 -0400
Message-ID: <yJCdnVwaZpF9POLcRVn-pg_at_comcast.com>
"Tony Andrews" <andrewst_at_onetel.com> wrote in message news:1098882637.945531.272870_at_z14g2000cwz.googlegroups.com...
> The important consideration that is so often overlooked by people with
> a "developer" mindset and not a "database" mindset is that applications
> come and go, come and go, but the data is there "forever". Right now,
> everyone is re-building their old apps using Java; in 5 years time it
> may be C#.NET or some as yet unknown super-language. Also, even while
> the current UI exists, there is often a push for new alternatives:
> web-based applications, mobile phone-based applications maybe; a batch
> process that receives XML by email and populates the database;
> whatever. The more robustly constraints are enforced by the DBMS, the
> easier and less dangerous it is to allow these UI upgrades and
> alternatives.
You are right. And thanks for fleshing out the reasons for redundant rule enforcement, the ones I snipped.