"Daniel Morgan" <damorgan_at_x.washington.edu> wrote in message
news:1069865589.637816_at_yasure...
> Mike Sherrill wrote:
>
> > On Tue, 25 Nov 2003 08:35:23 -0500, "mcstock"
> > <mcstockspamplug_at_spamdamenquery.com> wrote:
> >
> >
> >>if you're referring to declarative constraints, that's a given
> >
> >
> > I'm pretty sure that most of the people posting to this thread don't
> > regard it as a given.
> >
> > Looks like it's time to clarify who means what when they're talking
> > about "business logic" and "integrity constraints". To me, it looks
> > like some people regard them as identical, and some people regard them
> > as different.
> >
>
> By any definition you will ever learn while earning a computer science
> degree they are different.
>
> The business logic is that every invoice must have an invoice number.
> The integrity constraint is a primary key.
>
> The business logic is that all persons must have a gender
> The integrity constraints are a NOT NULL and a check constraint
> constraining entries to 'F' or 'M').
Interestingly the business logic may well specify a set of allowable values
for Gender well beyond 2. Possibly especially in california.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
Received on Wed Nov 26 2003 - 14:36:28 CST
