Re: Why is database integrity so impopular ?

From: David BL <davidbl_at_iinet.net.au>
Date: Thu, 16 Oct 2008 05:32:56 -0700 (PDT)
Message-ID: <eb9e70c4-997b-4a81-95fa-62be64ebff16_at_b38g2000prf.googlegroups.com>


On Oct 15, 10:08 pm, "Walter Mitty" <wami..._at_verizon.net> wrote:
> "DBMS_Plumber" <paul_geoffrey_br..._at_yahoo.com> wrote in message

> > In engineering, shit happens. Design with failure in mind.
>
> > I'm not going to argue for two weeks with 'Max' in accounting about
> > about whether he has a legitimate reason to not know the close date of
> > some transaction. Waste. Of. Time. I'm not going to expect
> > perfection; especially not out of programmers.
> > It seems prudent management practice as well as sound engineering to
> > say simply that "If you don't know - that's OK - just go with the
> > default."
>
> Outstanding reply. I'd go even further. I'd say that in data management,
> impossible cases arise routinely. Planning your systems so that they do
> something reasonably intelligent when the impossible happens is just plain
> good engineering.

I'd say impossible cases never arise by definition :) Received on Thu Oct 16 2008 - 14:32:56 CEST

Original text of this message