From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
---|---|
To: | "me(at)alternize(dot)com" <me(at)alternize(dot)com> |
Cc: | operationsengineer1(at)yahoo(dot)com, pgsqlnovice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: SQL Statement Help Needed |
Date: | 2005-12-06 18:55:49 |
Message-ID: | c2d9e70e0512061055m3b9a939aqf783b715148f3ad4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On 12/5/05, me(at)alternize(dot)com <me(at)alternize(dot)com> wrote:
> From: <operationsengineer1(at)yahoo(dot)com>
> > the reason for doing this is that you eliminate
> > database dead space (people that don't have faxes
> > won't store a null in the db (i think it is null) and
> > the db won't have to manage the null values).
>
> correct me if i'm wrong, but i don't think having a completely normalized
> datastructure makes always sense. if one would need to query an employee and
> having all phone numbers & stuff in one single view, you'll end up having a
> huge amount of joins. this is bound to "cost" performance while the "win"
> (diskspace) is relatively small.
>
> - thomas
>
there are cases, but you still want to justify yourself the use of
denormalized data...
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-06 20:17:43 | Re: CSV file - Using COPY Command - Double-Quotes |
Previous Message | operationsengineer1 | 2005-12-06 18:29:57 | Re: SQL Statement Help Needed |