Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!news.glorb.com!border1.nntp.ash.giganews.com!nntp.giganews.com!newspeer.monmouth.com!solaris.cc.vt.edu!news.vt.edu!news.netins.net!not-for-mail
From: "Dawn M. Wolthuis" <dwolt@tincat-group.com>
Newsgroups: comp.databases.theory
Subject: Re: Multiple specification of constraints
Date: Wed, 3 Mar 2004 16:03:14 -0600
Organization: netINS InterNetNews site
Lines: 55
Message-ID: <c25kn5$dij$1@news.netins.net>
References: <c1iq4p$6dp$1@news.netins.net> <9wd%b.121916$jk2.526707@attbi_s53> <c1ku71$jqu$1@news.netins.net> <D3n1c.20847$rG4.14508@newssvr31.news.prodigy.com> <c0e3f26e.0403031339.5d77d873@posting.google.com>
NNTP-Posting-Host: 199.120.93.7
X-Trace: news.netins.net 1078351398 13907 199.120.93.7 (3 Mar 2004 22:03:18 GMT)
X-Complaints-To: usenet@netins.net
NNTP-Posting-Date: Wed, 3 Mar 2004 22:03:18 +0000 (UTC)
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Xref: newssvr20.news.prodigy.com comp.databases.theory:24385

"Tony" <andrewst@onetel.net.uk> wrote in message
news:c0e3f26e.0403031339.5d77d873@posting.google.com...
> "Eric Kaun" <ekaun@yahoo.com> wrote in message
news:<D3n1c.20847$rG4.14508@newssvr31.news.prodigy.com>...
> > "Dawn M. Wolthuis" <dwolt@tincat-group.com> wrote in message
> > news:c1ku71$jqu$1@news.netins.net...
> > > "Marshall Spight" <mspight@dnai.com> wrote in message
> > > news:9wd%b.121916$jk2.526707@attbi_s53...
> > > > I think the optimal solution here is to have the constraints
specified
> > > > declaratively and centrally, but to be able to *additionally*
execute
> > > > them remotely, i.e., on the client. That last part, on the client,
is
> >  actually
> > > > the least essential place for validation to occur; it's the only one
> >  that
> > > > can be omitted. It's always essential to have it enforced centrally,
on
> >  the
> > > > server, because clients are typically not running on trusted
computing
> > > > bases.
> > > >
> > > I agree they should be specified "centrally" but don't necessarily
agree
> > > with what you mean by that.  If you mean that they should be specified
in
> >  a
> > > way that is tightly coupled with database storage services, I
disagree.
> >
> > Why is the storage even an issue? Surely we've abstracted above storage
by
> > now? A relational DBMS says what your data means - would you say that
the
> > Pick dictionary is "data storage"? The dicionary seems to be the
"meaning"
> > of your data, at least in a limited way. With relational languages like
D4,
> > you can say much, much more.
> >
> > If people just think of a database as a way to write to disk, then I
guess
> > the conversation is fairly stymied already. Hmph.
>
> Well, when they refer to the DBMS as "CRUD services", I think we can
> see what kind of goggles they are wearing!

If you are referring to me at the "they" I'll clarify -- the DBMS is made up
of at least data integrity services and CRUD services.  I would never
intentionally leave out the non-CRUD services of a DBMS (although I might
for a "database") so my apologies if that was not clear.  smiles  --dawn


