Re: Declarative constraints in practical terms

From: David Cressey <>
Date: Sat, 25 Feb 2006 13:44:34 GMT
Message-ID: <6bZLf.607$SJ2.606_at_trndny01>

"dawn" <> wrote in message
> David Cressey wrote:
> > "Frank Hamersley" <> wrote in message
> > news:4XBLf.15219$
> <snip>
> > If your primary role is prescribing process (in other words,
> > an imperative constraints may make more sense than declarative ones.
> > can't really speak to this. I programmed for twenty years before I got
> > databases, and I still know how to program. But I no longer look at
> > world through a programmer's eyes.
> >
> > In spite of Dawn's protestations to the contrary, I believe she still
> > look at the information through the eyes of a programmer, and not the
> > of a manager, or certainly not those of a data manager.
> I'll buy the first and last phrases of that observation. I've doled
> out the designation of "DBA" before to someone on my team, but have
> never been a DBA and likely lack many of the skills and personality
> traits required.

My question is not whether you are a DBA or not. My question is whether you are a database designer or not.

> When I disagree with someone here, it makes sense that it is likely my
> process side showing since this ng leans heavily on the data side. I
> think that on any given project I would likely be viewed by the rest of
> the team as being more data-centric than process-centric. Maybe I'm
> just well-balanced. Nah, unlikely...

Well... maybe not so unlikely. I've been on both sides of that fence, myself, in different contexts.
All I can react to is what I read. If that isn't the complete picture, then that isn't the complete picture.

In this n.g. your writing reflects an extremely process-centric position. Received on Sat Feb 25 2006 - 14:44:34 CET

Original text of this message