pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: jkakar@expressus.com
Cc: sqllist <pgsql-sql@postgresql.org>
Subject: Re: Normalization is always good?
Date: Thu, 15 Mar 2001 12:13:26 -0800
Message-ID: <3AB12266.CC2C9FA3@agliodbs.com> (raw)
References: <20010314212627.H12986@mail.perdue.net>
	<web-25229@davinci.ethosmedia.com>
	<20010315114619.A18169@expressus.com>

Jamu,

> I have been working with SQL databases for about a year in a half and
> in that time I've come to the conclusion that it is not always
> preferable to normalize to a high level (like 3rd level).  In some
> cases, depending on the application, I've found that normalizing to a
> ridiculous degree has shot me in the foot in terms of the
> responsibility of my code to manage what happens in the database.

There I'd agree with you ... there is the question of *how rigorous* you
want your normalization to be.  I tend to hover around the simplest
normal form, most of the time.  And I do a few things (such as
polymorhic sub-tables) that would give Fabian Pascal fits :-)

However, there is (in my mind) no question as to whether a database
should be normalized, just how much effort is spent on normalization as
opposed to other considerations (UI, performance, development time).

> I've found referential integrity makes normalization a less expensive
> notion as it absolves you of the task of keeping data current in all
> your tables.  I've also found that working in an object oriented
> language makes normalization less expensive.

What do you use?  I've given up on OODB interfaces, myself, as I did not
find them helpful, but that's modtly because I was working in MS-land.

> What are the views of the people on this list re: Normalization
> Guidelines?  Anybody know of any good web sites that talk about this
> in depth?

Yup.  http://www.databasedebunking.com/  Dig through the archives.

-Josh Berkus

-- 
______AGLIO DATABASE SOLUTIONS___________________________
                                        Josh Berkus
   Complete information technology      josh@agliodbs.com
    and data management solutions       (415) 565-7293
   for law firms, small businesses       fax  621-2533
    and non-profit organizations.       San Francisco



view thread (4+ messages)  latest in thread

Message-ID: <3AB12266.CC2C9FA3@agliodbs.com>
Permalink:  ../3AB12266.CC2C9FA3@agliodbs.com/
Also on:    postgresql.org/message-id/3AB12266.CC2C9FA3@agliodbs.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: josh@agliodbs.com, jkakar@expressus.com
  Subject: Re: Normalization is always good?
  In-Reply-To: <3AB12266.CC2C9FA3@agliodbs.com>
  References: <20010314212627.H12986@mail.perdue.net> <web-25229@davinci.ethosmedia.com> <20010315114619.A18169@expressus.com> <3AB12266.CC2C9FA3@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox