Re: DB clasical structure violation

From: Lee Fesperman <firstsql_at_ix.netcom.com>
Date: Sun, 23 Jun 2002 12:43:19 -0700
Message-ID: <3D1624D7.1E0D_at_ix.netcom.com>


Mariano Abdala wrote:
>
> Of course the idea is to keep the integrity. What we'd be gaining is
> redundancy, in order to improve in some cases performance(at least that's
> what i'm trying to prove).

But, redundancy directly impacts integrity. Redundancy means you have the same 'fact' in two different places. If the recording of the fact doesn't match in each place, then you have an integrity problem.

To avoid that, you must add constraints to ensure that multiple recordings of the fact do match. This will affect performance.

I ask again --- are you taking this into account?

> Hey! Thanx for the Web site, i'll check it out.

That's a good idea.

-- 
Lee Fesperman, FirstSQL, Inc. (http://www.firstsql.com)
==============================================================
* The Ultimate DBMS is here!
* FirstSQL/J Object/Relational DBMS  (http://www.firstsql.com)
Received on Sun Jun 23 2002 - 21:43:19 CEST

Original text of this message