Re: Normalization and DBMS
Date: Wed, 12 May 2004 00:22:45 -0300
Message-ID: <pan.2004.05.12.03.22.43.667655_at_dutra.fastmail.fm>
Em Tue, 11 May 2004 20:10:10 -0500, Dawn M. Wolthuis escreveu:
> it seems to have a direct correlation to the flexibility of a
Quite to the contrary. With nested tables, the only way to
> system to withstand years of requirements changes
On the other hand if you only have relations, the data will
always be there...
> For example, if people used to have an e-mail address and now they
> However, when working with SQL-DBMS's, it seems that developers use
This is a tools issue, not a DBMS one. If the tools request
codification changes, so be it. It is a low-level tool.
> have several, sometimes absolutely NOTHING has to change in the
> entire application other than to change the metadata for the field
> to describe it as permitting multiples.
CREATE TABLE
email
(
address,
person_code
)
> clever methods to keep from building new tables when cardinality
> changes
For many good-quality screen painters and the like nothing will be required.
You seem to be thinking about a 4GL. Aren't you one of the Pick guys?
-- Leandro Guimarães Faria Corsetti Dutra +55 (11) 5685 2219 Av Sgto Geraldo Santana, 1100 6/71 +55 (11) 5686 9607 04.674-000 São Paulo, SP BRASIL http://br.geocities.com./lgcdutra/Received on Wed May 12 2004 - 05:22:45 CEST
