DB design document

Phillip Shelton shelton@usq.edu.au
Mon, 18 Dec 2000 10:02:06 +1000


> -----Original Message-----
> This can certainly be a problem, but if the person who has the role of
> database designer normalizes (preferably to at least 3BNF*)
> the database
> when designing it, the times you would want to change its basic design
> should be extremely few, since each table (relation) of the database
> should be set up to correspond to one entity or concept in the real
> world and since the real world should not be changing all
> that much, the
> need to change existing items in the database should not
> change all that
> much either. (It might be necessary to add new tables to correspond to
> new stuff in the real world that GnuCash is to handle, but that would
> not require "refactoring".)

This only works if the DB designer know that they know all that is requied
and how it is relates to everything else.

I think that David M is still trying to make sure that he understands what
it is that gnycash needs to store.

Phill