Re: Agility and Data Design (was: Dreaming About Redesigning SQL)

"Marshall Spight" <mspight_at_dnai.com> wrote in message news:<Mv%lb.5734$9E1.26853_at_attbi_s52>...
>
> Well, it sounds like what you're describing falls into the category of
> what I was describing as smaller homogeneous systems, where I
> said it "may work well enough." If everything is written in the same
> language, it's a good deal easier to write your integrity enforcement
> code procedurally. (I still think that's a worse technique than
> declarative integrity enforcement, but you may offset the cost by
> gains in other areas.)
>
Yes, maybe. What would your upper limits be for a "smaller homogeneous system"? Maybe it would be best to use number of users, annual turnover - that sort of thing - to measure by, as (and I'm really not trying to provoke by saying this) the number of "transactions", "records", "tables", "total database size", number of IT staff, total IT expenditure and required hardware will all be smaller on an equivalent Pick system.

Mike. Received on Fri Oct 24 2003 - 07:04:35 CEST