Re: "We don't do triggers"

damorgan_at_x.washington.edu says...

> >>1. NO DATA LOADS EVER. Key it through the app ALWAYS. even 10 million rows.
> >>2. NO INTERFACES TO OTHER SYSTEMS, EVER. make other systems talk to the app.
> >>They both follow logically from this 'design' rule.

> > Makes sense.
 

> Provided you don't do anything with a database you couldn't do with 3x5
> cards.
> Anyone that "needs" Oracle would break such nonsense.
 

Oh dear. I appear to be having a problem with another person whose offerings on these newsgroup I normally respect.

Are you having an issue with my use of "Makes sense" because you think that

1. I think that organising a db that doesn't make use of SP's, Triggers &c. is a good thing?

or

b) I agree with Mr. Litchfield that if one doesn't have Triggers, SP's &.c, then one has to be very very careful about how one modifies data externally to any application that uses this db?

I agree with Mr. Litchfield, and that's why I wrote (that what he had written) "Makes sense".

I am aware that some people use databases as little more than glorified spreadsheets (I had to work in such an environment!), however, acknowledging that one *_should_* treat a db differently in such poor circumstances than when one is working in a decent well-designed environment is not an issue for which I would have thought that I would have merited such severe critique.

Paul...

-- 

plinehan  x__AT__x  yahoo  x__DOT__x  com

C++ Builder 5 SP1, Interbase 6.0.1.6 IBX 5.04 W2K Pro

Please do not top-post.